Alan McKinnon <alan.mckin...@gmail.com> wrote:
> Apparently, though unproven, at 20:57 on Sunday 22 August 2010,
> cov...@ccs.covici.com did opine thusly:
>
> > > There is a way to downgrade for the brave.
> > >
> > >
> > >
> > > quickpkg glibc
> > > move the 2.11.? version ebuild you want to your local overlay.
> > > Edit it and find the check that disallows downgrades. Comment it out.
> > > Mask glibc2.12
> > > update glibc
> > >
> > >
> > >
> > > At this point it's probably very wise to rebuild at least system, then
> > > revdep- rebuild. Note that rebuilding system might fail in which case
> > > you are really up the creek.
> > >
> > >
> > >
> > > Feel free to rip to pieces the dev that committed this version. It could
> > > not possibly have undergone decent testing
> >
> > I have another idea -- what would I have to restore from backup to
> > completely cancel the entire update process I have done since yesterday
> > -- and then I could mask off the bad glibc and be back to something at
> > least somewhat consistent?
>
>
> I too have another idea - look at emerge.log and tell us what you emerged
> since yesterday. Then restore those packages.
>
>
> --
> alan dot mckinnon at gmail dot com
If I tried that -- how would I downgrade glibc in the process -- I am
sure I could figure out all the packages, but that downgrade scares me
-- would I do the packages in reverse order, or what? I also changed my
gcc before this update, I could certainly reverse that as well.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
