public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: covici@ccs.covici.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 14:57:49 -0400	[thread overview]
Message-ID: <21720.1282503469@ccs.covici.com> (raw)
In-Reply-To: <201008221822.55851.alan.mckinnon@gmail.com>

Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> Apparently, though unproven, at 15:29 on Sunday 22 August 2010, Arttu V. did 
> opine thusly:
> 
> > On 8/22/10, covici@ccs.covici.com <covici@ccs.covici.com> wrote:
> > > Hi.  I am running the unstable gentoo 32-bit and today I emerged --
> > > amoung other packages in a system update -- glibc-2.12.1-r1, however
> > > after doing this at least one package had an undefined reference to
> > > S_ISCHR.   I tried to downgrade glibc, but apparently this is not
> > > supported and I am a bit stumped as to how to fix this problem.
> > > 
> > > Any ideas on this would be appreciated.
> > 
> > Which package is failing? Please check if it is already reported, and
> > if not then please report a new bug, and if possible make it block
> > this tracker bug:
> > 
> > http://bugs.gentoo.org/show_bug.cgi?id=331665
> > 
> > A wild guess out of the blue would be that the error could be simply a
> > missing include of stat.h in the package's sources. But there might be
> > other omissions as well, so please provide more info.
> > 
> > I think that unless API/ABIs were changed then the older, already
> > installed version should still work just fine, as then the missing
> > includes would only affect compile-time situation.
> 
> 
> 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?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com



  reply	other threads:[~2010-08-22 19:04 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 [this message]
2010-08-22 19:19       ` Alan McKinnon
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=21720.1282503469@ccs.covici.com \
    --to=covici@ccs.covici.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