On Mon, 9 Jun 2014 11:28:03 +0000, Alan Mackenzie wrote:

>     emerge -p --color y util-linux | less -F
> 
> , and get the following on my screen:
> 
>     [ebuild     U  ] sys-apps/util-linux-2.24.1-r2 [2.22.2]
> USE="bash-completion%* pam%* python%* -caps% -cytune% -fdformat%
> -tty-helpers%" PYTHON_SINGLE_TARGET="python2_7%* -python3_2%
> -python3_3% (-python3_4)" PYTHON_TARGETS="python2_7%* python3_3%*
> -python3_2% (-python3_4)"
>      * Error: The above package list contains packages which cannot be
>     [blocks B      ] <sys-apps/sysvinit-2.88-r7
> ("<sys-apps/sysvinit-2.88-r7" is blocking
> sys-apps/util-linux-2.24.1-r2) [blocks B      ]
> >=sys-apps/util-linux-2.23 (">=sys-apps/util-linux-2.23" is blocking
> >sys-apps/sysvinit-2.88-r4)
>      * installed at the same time on the same system.
> 
> .  The up to date versions of these two packages are sysvinit-2.88.r7
> and util-linux-2.24.1-r2.
> 
> Am I right in thinking that the first of these "blocks B" lines is
> saying that the latest util-linux is incompatible with the latest
> sysvinit - that util-linux needs _less_ than sysvinit-2.88.r7?  This
> feels like a bug.
> 
> What about the second "blocks B" line.  It seems to be saying that the
> _old_ version util-linux-2.23 is blocking the _new_ sysvinit.  Why is
> this comparison being done this way?

Because you are only upgrading util-linux, so portage is trying to
install it alongside the older sysvinit you have installed (the latest
stable version is 2.88-r7). If you emerge -u @system, portage should
resolve it correctly, it is your trying to update interdependent packages
piecemeal that results in the blocker.


-- 
Neil Bothwick

Did you hear about the blind prostitute? You have to hand it to her.

Attachment: signature.asc
Description: PGP signature

Reply via email to