Date: Sun, 10 Mar 2013 09:55:28 +0400 From: Ruslan Makhmatkhanov <cvs-src@yandex.ru> To: Kevin Oberman <rkoberman@gmail.com> Cc: gnome@freebsd.org, kwm@freebsd.org, mandree@freebsd.org Subject: Re: ports/176750: accessibility/at-spi does not record a CONFLICTS for at-spi2-atk Message-ID: <513C2050.30507@yandex.ru> In-Reply-To: <CAN6yY1ube2OvzRVa_vS7gtKvcwwhCo_0ax1c_PLr_8y3XGJRvQ@mail.gmail.com> References: <201303091711.r29HBx2k097089@freefall.freebsd.org> <CAN6yY1ube2OvzRVa_vS7gtKvcwwhCo_0ax1c_PLr_8y3XGJRvQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Kevin Oberman wrote on 10.03.2013 05:44:
> On Sat, Mar 9, 2013 at 9:11 AM, <kwm@freebsd.org> wrote:
>
>> Synopsis: accessibility/at-spi does not record a CONFLICTS for at-spi2-atk
>>
>> State-Changed-From-To: open->closed
>> State-Changed-By: kwm
>> State-Changed-When: Sat Mar 9 17:11:41 UTC 2013
>> State-Changed-Why:
>> Fix by removing the conflict, thanks for reporting!
>>
>> The conflict was only removed in one direction. accessibility/at-spi2-atk
> still retains the conflict with accessibility/at-spi. If you delete both
> ports and install accessibility/at-spi, it works, but the next time you
> attempt to update accessibility/at-spi2-atk, it will fail.
Yes, it looks like this within portmaster session:
"""
===>>> accessibility/at-spi2-atk seems to depend on accessibility/at-spi
which looks like a dependency loop
===>>> Try pkg_updating accessibility/at-spi
===>>> Aborting update
"""
So not yet fixed.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?513C2050.30507>