| 1 |
On 04/18/10 11:00, Tanstaafl wrote: |
| 2 |
> Crap, doesn't look like this will work... |
| 3 |
> |
| 4 |
> After masking gcc (and glibc - same argument there), I get: |
| 5 |
> |
| 6 |
> emerge -pev world |
| 7 |
|
| 8 |
<snip> |
| 9 |
|
| 10 |
> !!! All ebuilds that could satisfy "virtual/libc" have been masked. |
| 11 |
> !!! One of the following masked packages is required to complete your |
| 12 |
> request: |
| 13 |
> - sys-libs/glibc-2.11-r1 (masked by: package.mask, ~amd64 keyword) |
| 14 |
> - sys-libs/glibc-2.11 (masked by: package.mask, ~amd64 keyword) |
| 15 |
<snip> |
| 16 |
> For more information, see the MASKED PACKAGES section in the emerge |
| 17 |
> man page or refer to the Gentoo Handbook. |
| 18 |
> |
| 19 |
> myhost : Sun Apr 18, 10:56:51 : ~ |
| 20 |
> # |
| 21 |
> |
| 22 |
> Any other ideas? |
| 23 |
|
| 24 |
This is normal, it's informing you that those packages are masked, but |
| 25 |
not actually blocking the other updates. If you do: |
| 26 |
|
| 27 |
#emerge -e world -av |
| 28 |
|
| 29 |
i.e ask instead of pretend, it will output those warnings, and then ask |
| 30 |
you if you want to proceed with updating the rest. I'm using the |
| 31 |
unstable portage, but I'm pretty sure it's worked like this for quite a |
| 32 |
while on the stable branch too. |
| 33 |
|
| 34 |
Good luck :). |
Archives