public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc 2.12.1-r1 seems to not be working correctly
Date: Sun, 22 Aug 2010 21:19:56 +0200	[thread overview]
Message-ID: <201008222119.56944.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <21720.1282503469@ccs.covici.com>

Apparently, though unproven, at 20:57 on Sunday 22 August 2010, 
covici@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



  reply	other threads:[~2010-08-22 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22 12:52 [gentoo-user] glibc 2.12.1-r1 seems to not be working correctly covici
2010-08-22 13:22 ` Alex Schuster
2010-08-22 13:29 ` Arttu V.
2010-08-22 13:47   ` covici
2010-08-22 16:22   ` Alan McKinnon
2010-08-22 18:57     ` covici
2010-08-22 19:19       ` Alan McKinnon [this message]
2010-08-22 19:44         ` covici
2010-08-22 19:56           ` Alan McKinnon
2010-08-22 20:25           ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008222119.56944.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox