Re: [gentoo-user] eject and util-linux blocker

[Alan McKinnon]

On 17/03/2015 19:01, Dale wrote:
> Alan McKinnon wrote:
>> On 17/03/2015 03:43, Dale wrote:
>>
>> [...snip]
>>
>>> root@fireball / # emerge -uvaDN world -t
>>>
>>> These are the packages that would be merged, in reverse order:
>>>
>>> Calculating dependencies... done!
>>> [nomerge       ] lxde-base/lxde-meta-0.5.5-r4::gentoo
>>> [nomerge       ]  x11-misc/pcmanfm-1.2.3::gentoo  USE="-debug"
>>> [ebuild  N     ]   virtual/eject-0::gentoo  0 KiB
>>> [ebuild     UD ]    sys-apps/util-linux-2.24.1-r3::gentoo
>>> [2.26.1::gentoo] USE="bash-completion%* cramfs ncurses nls pam
>>> static-libs* suid udev unicode -caps -cytune% -fdformat -python
>>> (-selinux) -slang {-test} -tty-helpers (-systemd%)" ABI_X86="(64) (-32)
>>> (-x32)" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4"
>>> PYTHON_TARGETS="python2_7 python3_3 -python3_4" 0 KiB
>>> [ebuild  N     ]    sys-block/eject-2.1.5-r2::gentoo  USE="nls" 121 KiB
>>> [blocks B      ] sys-block/eject ("sys-block/eject" is blocking
>>> sys-apps/util-linux-2.24.1-r3)
>>>
>>> Total: 3 packages (1 downgrade, 2 new), Size of downloads: 121 KiB
>>> Conflict: 1 block (1 unsatisfied)
>>>
>>>  * Error: The above package list contains packages which cannot be
>>>  * installed at the same time on the same system.
>>>
>>>   (sys-block/eject-2.1.5-r2:0/0::gentoo, ebuild scheduled for merge)
>>> pulled in by
>>>     sys-block/eject required by (virtual/eject-0:0/0::gentoo, ebuild
>>> scheduled for merge)
>>>
>>>   (sys-apps/util-linux-2.24.1-r3:0/0::gentoo, ebuild scheduled for
>>> merge) pulled in by
>>>     >=sys-apps/util-linux-2.13 required by
>>> (www-plugins/nspluginwrapper-1.4.4-r3:0/0::gentoo, installed)
>>>     <sys-apps/util-linux-2.25[static-libs] required by
>>> (sys-fs/lvm2-2.02.109:0/0::gentoo, installed)
>>
>> Looks like this is the source of your problem. When dealing with
>> blocking downgrades I like to search for the "<" character to find what
>> other package is limiting the highest version. The above is the only one.
>>
>> The DEPEND for lvm2 looks like this:
>>
>> RDEPEND="${DEPEND_COMMON}
>> 	...
>>         >=sys-apps/util-linux-2.16
>> 	...
>> DEPEND="${DEPEND_COMMON}
>>         static? (
>>                 selinux? ( sys-libs/libselinux[static-libs] )
>>                 udev? ( >=virtual/libudev-208:=[static-libs] )
>>                 <sys-apps/util-linux-2.25[static-libs]
>>         )"
>>
>>
>> Do you have lvm2 built with USE=static?
>>
>>
>>
>> Second question is why will portage not upgrade lvm2 for you? What do
>> you get from this:
>>
>> emerge -pv lvm2
>>
>>
>
> This lead me down a path.  Here is the info you requested:
>
> root@fireball / # emerge -pv lvm2
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild     UD ] sys-apps/util-linux-2.24.1-r3::gentoo [2.26.1::gentoo]
> USE="bash-completion%* cramfs ncurses nls pam static-libs* suid udev
> unicode -caps -cytune% -fdformat -python (-selinux) -slang {-test}
> -tty-helpers (-systemd%)" ABI_X86="(64) (-32) (-x32)"
> PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4"
> PYTHON_TARGETS="python2_7 python3_3 -python3_4" 0 KiB
> [ebuild   R    ] sys-fs/lvm2-2.02.109::gentoo  USE="readline static thin
> udev (-clvm) (-cman) -device-mapper-only -lvm1 -lvm2create_initrd
> (-selinux) -static-libs -systemd" 0 KiB
>
> Total: 2 packages (1 downgrade, 1 reinstall), Size of downloads: 0 KiB
>
> The following USE changes are necessary to proceed:
>  (see "package.use" in the portage(5) man page for more details)
> # required by sys-fs/lvm2-2.02.109::gentoo[static]
> # required by @selected
> # required by @world (argument)
> =sys-apps/util-linux-2.24.1-r3 static-libs
> root@fireball / #
>
> It seems at some point, I did have a USE flag in package.use that was
> version specific.  I usually remove the version stuff and let it apply
> to all version.  Usually if you need a USE flag for one version, you
> will need it for the upgrade as well.  So, after removing the version
> info, I try again.  Similar message tho.  I then keyword lvm2, thinking
> it may need a newer version.  Then I get this crypted message.
>
> root@fireball / # emerge -uvaDN world -t
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies \
>
> !!! Problem resolving dependencies for sys-fs/lvm2 from @selected
> ... done!
>
> !!! The ebuild selected to satisfy "sys-fs/lvm2" has unmet requirements.
> - sys-fs/lvm2-2.02.110::gentoo USE="readline static thin udev -clvm
> -cman -device-mapper-only -lvm1 -lvm2create_initrd (-selinux)
> -static-libs -systemd" ABI_X86="64"
>
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     static? ( !udev )
>
>   The above constraints are a subset of the following complete expression:
>     device-mapper-only? ( !clvm !cman !lvm1 !lvm2create_initrd !thin )
> systemd? ( udev ) static? ( !udev )
>
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> root@fireball / # emerge -vp eudev
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R   ~] sys-fs/eudev-2.1.1::gentoo  USE="gudev hwdb
> introspection keymap kmod modutils rule-generator static-libs -doc
> (-selinux) {-test}" ABI_X86="(64) -32 (-x32)" 0 KiB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> root@fireball / #
>
> I included emerge -vp eudev as well.  It seems it doesn't like something
> about its USE flag.  I see static-libs in the USE list tho.  I had to do
> that a while back.  I think it had something to do with me having a
> seperate /usr and trying to avoid the init thingy.  I think.
>
> Jeepers.


Your basic problem is that you have static and static-libs in USE. When
applied to lvm, a whole bunch of blockers kick in and you get what you
got. So take them out of USE.

USE="static static-libs" has it's uses, it's great for building rescue
disks, busybox and maybe some disk repair utils, but makes very little
sense on a regular workstation. If you break your workstation, you'll
boot off a rescue disk and use the tools on it to fix your install, so
you don't need it on the main system.

There is nothing wrong with your eudev.
lvm2 is bitching about blockers between lvm2 built with "USE=static" and
udev - there's some incompatibility there and the ebuild knows about them


-- 
Alan McKinnon
alan.mckinnon@×××××.com