From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.12.1
Date: Wed, 18 Aug 2010 07:32:32 +0800 [thread overview]
Message-ID: <1282087952.8769.8.camel@rattus> (raw)
In-Reply-To: <201008171734.59882.alan.mckinnon@gmail.com>
Hi Alan, a suggestion - for "mission critical" clone one of your systems
into a vm (dd), get it working, upgrade and test.
Or clone to a chroot and do the same.
Not quite 100% - but allows some peace of mind!
BillK
On Tue, 2010-08-17 at 17:34 +0200, Alan McKinnon wrote:
> On Tuesday 17 August 2010 15:21:35 Peter Ruskin wrote:
> > On Tuesday 17 August 2010 09:33:09 Alan McKinnon wrote:
> > > Hi,
> > >
> > > Anyone successfully built and using glibc-2.12.1 yet?
> > >
> > > I see the tree just pushed an update down from 2.11.2 to 2.12.1,
> > > and downgrading that package is decidedly non-trivial. Only
> > > comment I can find at this early stage is flameeye's blog, and
> > > this makes me quadruple nervous:
> > >
> > >
> > >
> > >
> > > And if you say that “the new GLIBC works for me”, are you saying
> > > that the package itself builds or if it’s actually integrated
> > > correctly? Because, you know, I used to rebuild the whole system
> > > whenever I made a change to basic system packages when I
> > > maintained Gentoo/FreeBSD, and saying that it’s ready for ~arch
> > > when you haven’t even rebuilt the system (and you haven’t, or you
> > > would have noticed that m4 was broken) is definitely something
> > > I’d define as reckless and I’d venture to say you’re not good
> > > material to work on the quality assurance status.
> > >
> > > “correctness” in the case of the system C library would be “it a
> > > t least leaves the system set building and running”; glibc 2.12
> > > does not work this way.
> >
> > OK here on ~amd64, but you got me worried so I emerged m4 to check
> > and that went OK too.
>
>
> I got a couple of replies, all like this one - positive.
>
> Thanks, all. I'll start the update later on tonight and let 'er run.
>
>
>
--
William Kenworthy <billk@iinet.net.au>
Home in Perth!
next prev parent reply other threads:[~2010-08-18 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 8:33 [gentoo-user] glibc-2.12.1 Alan McKinnon
2010-08-17 9:56 ` Graham Murray
2010-08-17 13:21 ` Peter Ruskin
2010-08-17 15:34 ` Alan McKinnon
2010-08-17 16:30 ` Zhu Sha Zang
2010-08-17 23:32 ` William Kenworthy [this message]
2010-08-18 14:05 ` Alan McKinnon
2010-08-19 12:49 ` Neil Bothwick
2010-08-19 15:55 ` Alan McKinnon
2010-08-19 17:28 ` Neil Bothwick
2010-08-20 9:21 ` Alan McKinnon
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=1282087952.8769.8.camel@rattus \
--to=billk@iinet.net.au \
--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