Date: Wed, 03 Dec 2014 23:56:04 +0100 From: Koop Mast <kwm@rainbow-runner.nl> To: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org>, Andre Goree <andre@drenet.net> Cc: gnome@freebsd.org, kwm@freebsd.org, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Build of "telepathy-glib" fails Message-ID: <547F9504.5050907@rainbow-runner.nl> In-Reply-To: <44k328gzv0.fsf@lowell-desk.lan> References: <20141203085632.0ba07b59@scorpio> <b2e15161e692136206e77709ab9fe315@drenet.net> <44sigwh70h.fsf@lowell-desk.lan> <8809147fc4de7b88e4c71e2fb3368b5c@drenet.net> <44k328gzv0.fsf@lowell-desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3-12-2014 22:58, Lowell Gilbert wrote: > Andre Goree <andre@drenet.net> writes: > >> On 12/03/2014 2:23 pm, Lowell Gilbert wrote: >>> Andre Goree <andre@drenet.net> writes: >>> >>>> FWIW, I've also seen this. Like someone else mentioned, I think it >>>> has to do with the vala install, which I haven't been able to update >>>> either because according to /usr/ports/UPDATING I need to install >>>> gnome3 to update it, which I find to be ludicrous. >>> You are misunderstanding the instructions. >>> >>> If you aren't using Gnome, it's quite possible that nothing on your >>> system depends on vala, so the "users of vala" description wouldn't >>> apply to you. Assuming that it is in fact a leaf node, updating (or >>> removing) it is fine and doesn't even require any special instructions. >>> >>> telepathy-glib has a runtime dependency on vala, but you'll probably >>> still be fine doing a normal upgrade of both. >> Unfortunately: >> >> root@daemon2 ~ # pkg remove vala >> Checking integrity... done (0 conflicting) >> Deinstallation has been requested for the following 9 packages (of 0 >> packages in the universe): >> >> Installed packages to be REMOVED: >> vala-0.20.1_1 >> vala-vapigen-0.20.1_1 (depends on vala-0.20.1_1) >> telepathy-glib-0.20.2_1 (depends on vala-0.20.1_1) >> telepathy-farsight-0.0.19_2 (depends on vala-0.20.1_1) >> telepathy-qt4-0.9.3_1 (depends on vala-0.20.1_1) >> krfb-4.14.2 (depends on vala-0.20.1_1) >> kdenetwork-4.14.2 (depends on vala-0.20.1_1) >> kde-4.14.2 (depends on vala-0.20.1_1) >> krdc-4.14.2 (depends on vala-0.20.1_1) >> >> and even: >> >> root@daemon2 ~ # pkg remove vala-vapigen-0.20.1_1 >> Checking integrity... done (0 conflicting) >> Deinstallation has been requested for the following 8 packages (of 0 >> packages in the universe): >> >> Installed packages to be REMOVED: >> vala-vapigen-0.20.1_1 >> telepathy-glib-0.20.2_1 (depends on vala-vapigen-0.20.1_1) >> telepathy-farsight-0.0.19_2 (depends on vala-vapigen-0.20.1_1) >> telepathy-qt4-0.9.3_1 (depends on vala-vapigen-0.20.1_1) >> krfb-4.14.2 (depends on vala-vapigen-0.20.1_1) >> kdenetwork-4.14.2 (depends on vala-vapigen-0.20.1_1) >> kde-4.14.2 (depends on vala-vapigen-0.20.1_1) >> krdc-4.14.2 (depends on vala-vapigen-0.20.1_1) >> >> >> I do indeed use kde4 on this box. > You could check with whoever wrote that UPDATING entry. > > At the very worst, you'll have to do something along the lines of "pkg > delete vala-vapigen" followed by a "pkg add x11/kde" (or some equivalent > like building the port instead of the "pkg add"). In other words, follow > the instructions as listed but replace "gnome3" with "kde4". That would > be my recommendation. > > I suppose the UPDATING entry could be corrected to cover anything that > gets deinstalled by the "pkg delete" bits of the procedure, not just gnome. The update instructions mention that the user should make a list of installed ports, and install ports that where uninstalled after the update is done. This was done in this manor so that there would be no stale ports left on the system. Adding more would make the instruction rather complex. If only vala-vapigen is involved you can remove it with "pkg delete -f vala-vapigen" this will only remove this port.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?547F9504.5050907>