On Tue, Oct 6, 2015 at 8:01 AM, Neil Bothwick <[email protected]> wrote: > On Tue, 6 Oct 2015 13:31:54 +0300, Ran Shalit wrote: > >> >=virtual/libudev-215-r1 abi_x86_32 >> Would you like to add these changes to your config files? [Yes/No] Y >> Autounmask changes successfully written. >> * IMPORTANT: 8 config files in '/etc/portage' need updating. > > This is the important line > >> * See the CONFIGURATION FILES section of the emerge >> * man page to learn how to update config files. >> !!! All ebuilds that could satisfy >> ">=sys-libs/zlib-1.2.8-r1:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]" >> have been masked. >> !!! One of the following masked packages is required to complete your >> request: >> - sys-libs/zlib-1.2.8-r1::gentoo (masked by: ) >> (dependency required by "media-libs/lcms-2.6-r1::gentoo" [ebuild]) >> (dependency required by >> "app-emulation/wine-9999::gentoo[abi_x86_32,lcms]" [ebuild]) >> (dependency required by "wine" [argument]) >> For more information, see the MASKED PACKAGES section in the emerge >> man page or refer to the Gentoo Handbook. >> gentoo ~ # > > You need to run etc-update, or your preferred alternative config manager, > to merge the changes into /etc/portage/package.use. Portage only puts > them in a temporary ._cfg00* files, it doesn't apply them directly, you > are expected to manage that. >
Correct. In addition to accepting the auto-unmask which will set the 32-bit abi use flag on zlib, you should undo the changes you inadvertently made: Edit /etc/portage/package.keywords to remove the zlib line you added Edit /var/lib/portage/world to remove zlib (which was added when you ran emerge zlib without a -1 option). If you don't do this you might run into trouble in a few years if somebody comes out with libREz and it gets virtualized. In general you always want to run emerge -1 when you're just rebuilding things to try to troubleshoot. -- Rich
