James Broadhead writes:
> On 8 December 2011 11:17, Jarry <mr.ja...@gmail.com> wrote:
> > I just upgraded gcc and after switching to the new version
> > I want to update system too.
> > But it wants to emerge
> > baselayout-2 as dependency of system:
> >
> > !!! All ebuilds that could satisfy "sys-apps/baselayout" have
> > !!! been masked. One of the following masked packages is required
> > !!! to complete your request:
> > - sys-apps/baselayout-2.1::gentoo (masked by: package.mask,
> > ~amd64 keyword)
> > /etc/portage/package.mask:
> > - sys-apps/baselayout-2.0.3::gentoo (masked by: package.mask)
> > (dependency required by "@system" [argument])
> >
> > I do not want to upgrade to baselayout-2, but I want to
> > re-emerge system. So how can I do it now, when all 1.x
> > versions have been removed from portage?
>
> I think that the standard answer is "you can't". I mean, you could
> fetch an old copy of the ebuild from cvs, and add it to a local
> overlay, but you'd be completely unsupported (unsupportable?).
The ebuilds of currently installed packages can also be found
as /var/db/pkg/<category>/<package>/<package>.ebuild.
They are masked now, but when putting the packages
in /etc/portage/package.unmask it should be possible to install them
again.
> A better question would be - Why do you want to?
Probably in order to deal with potential migration problems later, and
not risking to harm a system that is currently running fine. The
migration should be a smooth one, but some manual changes have to be
made, and the syntax in /etc/conf.d/net has changed.
But I'd just wait with the system update, and make the switch when I have
some time.
Wonko
