Upgrading to Edgy Eft

[Derek Broughton]

Mario Vukelic wrote:

> On Tue, 2006-06-27 at 12:12 -0300, Derek Broughton wrote:
>> I'm curious as to why people seem to get _upset_ that we try this?
> 
> I don't think people get upset about this at all. But I think what does
> upset some people is if users upgrade to edgy, then post to the list
> "something is broken, I have package conflicts", and ask for help.

No, when I went looking for my locales problem, forum users (yeah, well, I'm
anti-forum, anyway :-) ) we're imo abusive about it.  The OP had posted
good details (certainly good enough for the responders to know _exactly_
what his - and my - problem was) and he was told in no uncertain terms that
he shouldn't be using Edgy.  That's (a) nuts and (b) against The Code.

> Some people seem to think that it's a certified right to use a working
> unstable dist very early in the cycle, and that is has to be possible in
> Ubuntu because it worked in Debian.

That wasn't the situation in the case I observed.  Now, I realize that I
can't generalize from this one situation, but really I think people should
be encouraged to use edgy, not discouraged.
> 
> That's just not the case. If it's broken, it is just as expected 

Absolutely.

> (see the edgy schedule on the wiki).

Well, that's _another_ of my bugbears.  Everybody says "see the wiki", but
nobody seems to have URLs.  At least a pointer to "the wiki" if not the
correct page would be nice.

> I know from your postings that you have the skills to help yourself and
> will be able to provide useful feedback to the devs, but nobody is upset
> about you :)

LOL.  I expect plenty of people get upset about me :-)  but I get your
point.  

fwiw, if you use a non-standard locale and want to upgrade to edgy: remove
libc6-i686 first (it gets in the way if you try to back it out later, and
you don't actually need it), upgrade to edgy, if locales are still broken
(you'll know - just about everything generates warning messages), then
change your source repo back to dapper, reinstall libc6 from dapper. 
Whether it works or not, you can reinstall libc6-i686 after the fact.  Of
course, by now that bug may be fixed and entirely new ones exist!  The only
things this problem actually broke were Postgres & Samba, but it was
extremely irritating in many other cases.
-- 
derek