Summary: | sys-apps/portage-2.2.1: emerge x11-libs/libpciaccess wants to rebuild sys-libs/zlib for no apparent reason | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Daniel Nilsson <gentoo> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge -pv --debug x11-libs/libpciaccess |
Description
Daniel Nilsson
2013-10-04 15:43:58 UTC
Created attachment 360122 [details]
emerge -pv --debug x11-libs/libpciaccess
I think this is what happens when the libpciaccess dep goes from just "sys-libs/zlib" to "sys-libs/zlib[$MULTILIB_USEDEP]" which expands to (something like): sys-libs/zlib[abi_x86_32(-),abi_x86_64(-)] I would guess that this vague rebuild is reproducible in other cases where a dep goes from "cat/libfoo" to "cat/libfoo[bar(-)]" where the current version of libfoo does not have any "bar" in IUSE. Kind of a funny portage quirk, not exactly a disaster though. I can reproduce this too, btw: # emerge -pv x11-libs/libpciaccess These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-libs/zlib-1.2.7 USE="-minizip -static-libs" 0 kB [ebuild N ] x11-libs/libpciaccess-0.13.2 USE="zlib -minimal -static-libs" ABI_X86="(64) (-32) (-x32)" 351 kB Total: 2 packages (1 new, 1 reinstall), Size of downloads: 351 kB # For a more concrete example: # emerge --noreplace -pv "sys-libs/zlib" These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB # emerge --noreplace -pv "sys-libs/zlib[-abi_x86_32(-),abi_x86_64(-)]" These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-libs/zlib-1.2.7 USE="-minizip -static-libs" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB # Even though it shows no ABI_X86 flags available, it's still affected by the dep. |