[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Upgrading 1.3.1 -> 2.0 (was Re: predepends on libc6?)

On Tue, 25 Nov 1997, Christian Schwarz wrote:

> On Fri, 21 Nov 1997, Bdale Garbee wrote:
> > In bug report 15091, Christian Meder suggests to me that I make gzip predepend
> > on libc6.  It is not clear to me that this is a good thing to do.
> > 
> > What is the process by which we expect current Debian 1.3.1 users to upgrade
> > to Debian 2.0?  I used the libc5->libc6 mini-Howto when I upgraded my 
> > systems, and all went very smoothly.  Do we expect to suggest our users go
> > through a similarly manual process as part of the upgrade, or can we make it
> > all work without manual intervention?
> I personally would like to have the upgrade automatically by using dselect
> (i.e. without having to read a mini-howto). Note, that I think the
> mini-howto is an excellent piece of work. I just doubt that every user
> really reads the documentation before doing the upgrade. And `trail and
> error' really produces some `errors' in this situation.
> Can someone report what has to be done to make an automatic
> upgrade possible?

My latest test of upgrading ran reasonably smoothly, although bash still
got confused over the relocation of libreadline (ldconfig from an open
root shell fixed it). As far as I can see, it is no longer possible to
smash vital libraries by installing packages in the wrong order.  I had to
run through several install/config cycles in dselect, but it wasn't that
bad.  I've made a suggestion on getting the libreadline upgrade to go
smoother, but I haven't seen it implimented yet.  I hope to be getting a
new machine to do some more install/upgrade testing in a few weeks, at
which time I'll try to shake out installation problems.

Scott K. Ellis <storm@gate.net>                 http://www.gate.net/~storm/

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: