| 1 |
On 8 December 2011 11:17, Jarry <mr.jarry@×××××.com> wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I just upgraded gcc and after switching to the new version |
| 5 |
> I want to update system too. But it wants to emerge |
| 6 |
> baselayout-2 as dependency of system: |
| 7 |
> |
| 8 |
> !!! All ebuilds that could satisfy "sys-apps/baselayout" have |
| 9 |
> !!! been masked. One of the following masked packages is required |
| 10 |
> !!! to complete your request: |
| 11 |
> - sys-apps/baselayout-2.1::gentoo (masked by: package.mask, |
| 12 |
> ~amd64 keyword) |
| 13 |
> /etc/portage/package.mask: |
| 14 |
> - sys-apps/baselayout-2.0.3::gentoo (masked by: package.mask) |
| 15 |
> (dependency required by "@system" [argument]) |
| 16 |
> |
| 17 |
> I do not want to upgrade to baselayout-2, but I want to |
| 18 |
> re-emerge system. So how can I do it now, when all 1.x |
| 19 |
> versions have been removed from portage? |
| 20 |
|
| 21 |
I think that the standard answer is "you can't". I mean, you could |
| 22 |
fetch an old copy of the ebuild from cvs, and add it to a local |
| 23 |
overlay, but you'd be completely unsupported (unsupportable?). |
| 24 |
|
| 25 |
A better question would be - Why do you want to? |
Archives