Build of "telepathy-glib" fails

Andre Goree andre at drenet.net
Wed Dec 3 23:26:26 UTC 2014


On 12/03/2014 5:56 pm, Koop Mast wrote:
> On 3-12-2014 22:58, Lowell Gilbert wrote:
>> Andre Goree <andre at drenet.net> writes:
>> 
>>> On 12/03/2014 2:23 pm, Lowell Gilbert wrote:
>>>> Andre Goree <andre at 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 at 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 at 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.

Thanks, you two.  I'll get around to fiddling with this when I have the 
time.  Really don't want to break kde4 on this box atm (I've done this 
many times in the past, it's not fun trying to fix it).

-- 
Andre Goree
-=-=-=-=-=-
Email     - andre at drenet.net
Website   - http://www.drenet.net
PGP key   - http://www.drenet.net/pubkey.txt
-=-=-=-=-=-


More information about the freebsd-ports mailing list