Re: Beta-testing and the glibc 2.1 (Was: Missing ldd? Have libc6 on hold? Get ldso from slink...
Quoting "Seth M. Landsman" <seth@job.cs.brandeis.edu>:
> Okay, let's not turn this into a flame war. My point is that
> breakages in unstable are *REALLY BAD THINGS*. Yes, they happen, but the
> attitude that this one comes with is one of "it's your problem for trying
> unstable, not ours". If you manage to alienate the community of people
> who do real work, debian won't be tested on real work machines and won't
> be as stable as it should be. You haven't addressed this point.
> Oh, and my 20 gig DDS is in the shop. Sorry, telling people "back
> up often" is getting less realistic. The fact is, my important stuff is
> backed up in five places, but reinstalling is still a pita.
>
> Most people don't have that extra machine sitting around.
I took this change from a different standpoint. I knew this was coming
for a long time...(I just forgot it was that time)...I'm also expecting
a cluster when the new perl gets drop into potato...
but the thing is...I was told about it in advance...we were warned that
the potential for bad crap to happen was there. I run potato on
several machines...mainly because it is (most of the time) pretty stable.
But when this upgrade rolled out it screwed several things and it took
me a few days to work through them...and there are a few minor things still
doing weird things...but the thing is...if I had been paying attention when
I did the update/upgrade I would have noticed that it was glibc2.1 and I
would have been more cautious...(ie..checking the mailing list a little more
closely to see if there were issues..) but I didn't pay attention and thus
I had problems.
If the system you run potato on is one you don't want to crash...the only thing
I can say is that you should space your update/upgrade's a few days behind
the flow somehow...pay attention to what shows up as updated packages...and use
the hold option.
I'm sorry but I have to say this...unstable is unstable. I do agree with your
argument..but it's still unstable. You have to expect that something might
break everything...but there are still ways around that...
just my two bits..
Ivan
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ivan E. Moore II Rev. Krusty
http://snowcrash.tdyc.com rkrusty@tdyc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
GPG KeyID=0E1A75E3
GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Reply to: