Re: [gentoo-user] Multiple package instances within a single package slot

[Alan McKinnon <alan.mckinnon@gmail.com>]

On 06/03/2013 22:25, Valmor de Almeida wrote:
> On Wed, Mar 6, 2013 at 1:39 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> On 06/03/2013 01:21, Valmor de Almeida wrote:
>>> Hello,
>>>
>>> I would appreciate help with this multiple-packages-in-a-single slot
>>> problem. In the past I have unistalled packages and reinstalled on a
>>> case-by-case basis and dealt with the fall out manually. I wonder
>>> whether there is a more efficient way of doing it.
>>>
>>> Thanks,
>>>
>>> --
>>> Valmor
>>>
>>>
>>> -> USE="libkms cups apng minizip hwdb" emerge -vp --newuse --tree
>>> --update --deep system
>>
>>                   ^^^^^^
>>
>> Don't do that, rather run it on world; or you could do "emerge -pv
>> @system" Modern portage versions deal with these blockers automatically,
>> but they need the whole dependency graph to do it. There's no much point
>> in trying to deal with system and world independently anyway, system
>> isn't something magical, it's nothing more than a minimum collection of
>> packages that Gentoo can still run on, a mere list.
> 
> Thanks for the info. Did it on world and got
> 
> -------------------------
> -> USE="pulseaudio sqlite libkms cups apng minizip hwdb" emerge -vp
> --newuse --tree --update --deep world
> 
> These are the packages that would be merged, in reverse order:
> 
> [snip]
> 
> [blocks B      ]  <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
> sys-fs/udev-init-scripts-23)
> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
> 
> Total: 126 packages (91 upgrades, 12 new, 6 in new slots, 17
> reinstalls, 1 uninstall), Size of downloads: 989,597 kB
> Conflict: 7 blocks
> ------------------------
> 
> I have udev-171 at the moment and I have read and followed the
> instructions in the eselect news for the udev upgrade. I would
> appreciate any pointers on how to deal with this particular blocking.

First of all, don't put USE on the command line for emerge. It is not
stored and when you do the real emerge the results will be different if
you omit the USE. If you leave it in then portage doesn't know you did
it and complains bitterly with the next emerge claiming that flags
changed. Use make.conf like it is supposed to be used, don't try
second-guess portage.

Secondly, udev and sysvinit have higher versions marked stable. Portage
should just update them but apparently is not. I suspect you have masked
them in package.mask to avoid all the recefuss about udev, meaning you
have caused your own problem.

If you are happy moving to recent udev, then let portage do it.
If not, then you are on your own and have to figure out the masking
yourself. It will involve masking every new version of software that
shows up as a blocker like udev-init-scripts and util-linux. Eventually
you will run into an unsolveable conflict, maybe we are even already there


> nt 
> Thanks,
> 
> --
> Valmor
> 
>>
>> -ND to rebuild system doesn't get you anything extra and usually wants
>> to evaluate half of world as well (usually due to USE=X)
>>
>> You update system if you want to guarantee yourself a consistent
>> toolchain after a gcc or glibc update, or just prior to emerge -e world
>>
>>
>>
>>>
>>> [snip]
>>>
>>> [blocks B      ]  <sys-apps/sysvinit-2.88-r4
>>> ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)
>>> [blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking
>>> sys-fs/udev-init-scripts-23)
>>> [blocks B      ] <sys-fs/lvm2-2.02.97-r1 ("<sys-fs/lvm2-2.02.97-r1" is
>>> blocking sys-fs/udev-197-r8)
>>>
>>> !!! Multiple package instances within a single package slot have been pulled
>>> !!! into the dependency graph, resulting in a slot conflict:
>>>
>>> x11-base/xorg-server:0
>>>
>>>   (x11-base/xorg-server-1.12.4::gentoo, installed) pulled in by
>>>     <x11-base/xorg-server-1.12.99[-minimal] required by
>>> (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed)
>>>     (and 1 more with the same problem)
>>>
>>>   (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) pulled in by
>>>     (no parents that aren't satisfied by other packages in this slot)
>>>
>>> virtual/udev:0
>>>
>>>   (virtual/udev-171::gentoo, installed) pulled in by
>>>     <virtual/udev-196 required by (sys-fs/lvm2-2.02.88::gentoo, installed)
>>>
>>>   (virtual/udev-197-r1::gentoo, ebuild scheduled for merge) pulled in by
>>>     >=virtual/udev-197-r1 required by (sys-fs/udev-197-r8::gentoo,
>>> ebuild scheduled for merge)
>>>     =virtual/udev-197-r1 required by
>>> (sys-apps/util-linux-2.22.2::gentoo, ebuild scheduled for merge)
>>>     (and 11 more with the same problems)
>>>
>>> sys-fs/udev:0
>>>
>>>   (sys-fs/udev-171-r9::gentoo, installed) pulled in by
>>>     ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?]
>>> required by (virtual/udev-171::gentoo, installed)
>>>
>>>   (sys-fs/udev-197-r8::gentoo, ebuild scheduled for merge) pulled in by
>>>     >=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?]
>>> required by (virtual/udev-197-r1::gentoo, ebuild scheduled for merge)
>>>
>>> x11-drivers/xf86-video-virtualbox:0
>>>
>>>   (x11-drivers/xf86-video-virtualbox-4.1.24::gentoo, ebuild scheduled
>>> for merge) pulled in by
>>>     (no parents that aren't satisfied by other packages in this slot)
>>>
>>>   (x11-drivers/xf86-video-virtualbox-4.1.22::gentoo, installed) pulled in by
>>>     ~x11-drivers/xf86-video-virtualbox-4.1.22 required by
>>> (app-emulation/virtualbox-guest-additions-4.1.22::gentoo, installed)
>>>
>>
>>
>> --
>> Alan McKinnon
>> alan.mckinnon@gmail.com
>>
>>
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com