1 |
On Tue, Oct 6, 2015 at 8:01 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Tue, 6 Oct 2015 13:31:54 +0300, Ran Shalit wrote: |
3 |
> |
4 |
>> >=virtual/libudev-215-r1 abi_x86_32 |
5 |
>> Would you like to add these changes to your config files? [Yes/No] Y |
6 |
>> Autounmask changes successfully written. |
7 |
>> * IMPORTANT: 8 config files in '/etc/portage' need updating. |
8 |
> |
9 |
> This is the important line |
10 |
> |
11 |
>> * See the CONFIGURATION FILES section of the emerge |
12 |
>> * man page to learn how to update config files. |
13 |
>> !!! All ebuilds that could satisfy |
14 |
>> ">=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(-)?]" |
15 |
>> have been masked. |
16 |
>> !!! One of the following masked packages is required to complete your |
17 |
>> request: |
18 |
>> - sys-libs/zlib-1.2.8-r1::gentoo (masked by: ) |
19 |
>> (dependency required by "media-libs/lcms-2.6-r1::gentoo" [ebuild]) |
20 |
>> (dependency required by |
21 |
>> "app-emulation/wine-9999::gentoo[abi_x86_32,lcms]" [ebuild]) |
22 |
>> (dependency required by "wine" [argument]) |
23 |
>> For more information, see the MASKED PACKAGES section in the emerge |
24 |
>> man page or refer to the Gentoo Handbook. |
25 |
>> gentoo ~ # |
26 |
> |
27 |
> You need to run etc-update, or your preferred alternative config manager, |
28 |
> to merge the changes into /etc/portage/package.use. Portage only puts |
29 |
> them in a temporary ._cfg00* files, it doesn't apply them directly, you |
30 |
> are expected to manage that. |
31 |
> |
32 |
|
33 |
Correct. In addition to accepting the auto-unmask which will set the |
34 |
32-bit abi use flag on zlib, you should undo the changes you |
35 |
inadvertently made: |
36 |
Edit /etc/portage/package.keywords to remove the zlib line you added |
37 |
Edit /var/lib/portage/world to remove zlib (which was added when you |
38 |
ran emerge zlib without a -1 option). If you don't do this you might |
39 |
run into trouble in a few years if somebody comes out with libREz and |
40 |
it gets virtualized. In general you always want to run emerge -1 when |
41 |
you're just rebuilding things to try to troubleshoot. |
42 |
|
43 |
-- |
44 |
Rich |