Re: Testing system upgrade from sarge to etch

2006-03-16 Thread Justin Pryzby
On Wed, Mar 15, 2006 at 02:53:24PM +0200, Lars Wirzenius wrote: > ti, 2006-03-14 kello 21:52 -0500, Justin Pryzby kirjoitti: > > On Tue, Mar 14, 2006 at 10:02:06PM +0200, Lars Wirzenius wrote: > > What "optional" sarge packages aren't co-installable? > > Lots of them. I didn't keep a list. > > >

Re: Testing system upgrade from sarge to etch

2006-03-15 Thread Lars Wirzenius
ti, 2006-03-14 kello 21:52 -0500, Justin Pryzby kirjoitti: > On Tue, Mar 14, 2006 at 10:02:06PM +0200, Lars Wirzenius wrote: > > I attempted to install all optional packages from sarge and do the test > > with them, but that failed: it seems not all optional packages in sarge > > are co-installable

Re: Testing system upgrade from sarge to etch

2006-03-14 Thread Raphael Hertzog
On Tue, 14 Mar 2006, Lars Wirzenius wrote: > I've just ran it, and with the exception of lpr, there were no problems. > lpr does cause a problem, but it seems to be because the chroot does not > contain /proc and the preinst that runs on upgrade calls > start-stop-daemon, which fails due to the lac

Re: Testing system upgrade from sarge to etch

2006-03-14 Thread Justin Pryzby
On Tue, Mar 14, 2006 at 10:02:06PM +0200, Lars Wirzenius wrote: > I wrote a little script (attached) that creates a sarge chroot, installs > all packages of standard or higher priority, and then upgrades the whole > thing to etch. > > I've just ran it, and with the exception of lpr, there were no