1 |
Hi Alan, a suggestion - for "mission critical" clone one of your systems |
2 |
into a vm (dd), get it working, upgrade and test. |
3 |
|
4 |
Or clone to a chroot and do the same. |
5 |
|
6 |
Not quite 100% - but allows some peace of mind! |
7 |
|
8 |
BillK |
9 |
|
10 |
On Tue, 2010-08-17 at 17:34 +0200, Alan McKinnon wrote: |
11 |
> On Tuesday 17 August 2010 15:21:35 Peter Ruskin wrote: |
12 |
> > On Tuesday 17 August 2010 09:33:09 Alan McKinnon wrote: |
13 |
> > > Hi, |
14 |
> > > |
15 |
> > > Anyone successfully built and using glibc-2.12.1 yet? |
16 |
> > > |
17 |
> > > I see the tree just pushed an update down from 2.11.2 to 2.12.1, |
18 |
> > > and downgrading that package is decidedly non-trivial. Only |
19 |
> > > comment I can find at this early stage is flameeye's blog, and |
20 |
> > > this makes me quadruple nervous: |
21 |
> > > |
22 |
> > > |
23 |
> > > |
24 |
> > > |
25 |
> > > And if you say that “the new GLIBC works for me”, are you saying |
26 |
> > > that the package itself builds or if it’s actually integrated |
27 |
> > > correctly? Because, you know, I used to rebuild the whole system |
28 |
> > > whenever I made a change to basic system packages when I |
29 |
> > > maintained Gentoo/FreeBSD, and saying that it’s ready for ~arch |
30 |
> > > when you haven’t even rebuilt the system (and you haven’t, or you |
31 |
> > > would have noticed that m4 was broken) is definitely something |
32 |
> > > I’d define as reckless and I’d venture to say you’re not good |
33 |
> > > material to work on the quality assurance status. |
34 |
> > > |
35 |
> > > “correctness” in the case of the system C library would be “it a |
36 |
> > > t least leaves the system set building and running”; glibc 2.12 |
37 |
> > > does not work this way. |
38 |
> > |
39 |
> > OK here on ~amd64, but you got me worried so I emerged m4 to check |
40 |
> > and that went OK too. |
41 |
> |
42 |
> |
43 |
> I got a couple of replies, all like this one - positive. |
44 |
> |
45 |
> Thanks, all. I'll start the update later on tonight and let 'er run. |
46 |
> |
47 |
> |
48 |
> |
49 |
|
50 |
-- |
51 |
William Kenworthy <billk@×××××××××.au> |
52 |
Home in Perth! |