Starting from a (IIRC) rather basic potato system, I did (essentially): change sources.list to point to testing apt-get update apt-get dist-upgrade
I got the following error after much stuff had installed: Preparing to replace exim 3.12-10 (using .../archives/exim_3.31-1_i386.deb) ... mv: cannot create regular file `/etc/exim/exim.conf': No such file or directory dpkg: error processing /var/cache/apt/archives/exim_3.31-1_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Starting MTA: exim. Preparing to replace gettext-base 0.10.35-13 (using .../gettext-base_0.10.39-2_i386.deb) ... Unpacking replacement gettext-base ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.17-3_i386.deb) ... Moving /etc/tmac.man.local to /etc/groff/man.local. Replacing files in old package groff ... Errors were encountered while processing: /var/cache/apt/archives/exim_3.31-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) debian:/var/cache/apt# In fact, the directory: /etc/exim does not exist. I found Subject: Re: dist-upgrade from stable to testing http://lists.debian.org/debian-user/2001/debian-user-200108/msg02377.html Date: Tue, 14 Aug 2001 08:35:28 -0500 Which said: """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" On Tue, Aug 14, 2001 at 12:20:57AM -0600, Phil Reardon wrote: > On Monday 13 August 2001 11:36 pm, John Galt wrote: > > mkdir /etc/exim then rerun apt-get dist-upgrade... You won't have to > > re-download the 166M, BTW. > > > > On Mon, 13 Aug 2001, Phil Reardon wrote: > > >After apt-get update, apt-get dist-upgrade to testing, I got a successful > > >download of 166 MB. But during the install/config, I saw this message: > > > > > >mv: cannot create regjular file '/etc/exim/exim.conf' ; No such file or > > >directory. > > > .(stuff removed) > > Thanks, John: > > I tried creating the exim directory and even did a touch exim.conf there. > Then I did apt-get dist-upgrade again and it complained of unmet dependencies > and recommended apt-get -f install. I did that too, and then things > proceeded okay. I think I have Woody now! This is also fixed in exim 3.32-1 in unstable, by the way. exim (3.32-1) unstable; urgency=low [...] * debian/preinst: create /etc/exim before moving exim.conf (Closes: #106659, #107657) [...] -- Mark Baker <[EMAIL PROTECTED]> Wed, 8 Aug 2001 23:34:04 +0100 -- Colin Watson [EMAIL PROTECTED] """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" In my /v/c/a/a I have: @debian:/var/cache/apt/archives$ ls -al exim* -rwxr-xr-x 1 root root 650710 Jun 9 19:45 exim_3.12-10.1_i386.deb -rwxr-xr-x 1 root root 650572 May 2 2000 exim_3.12-10_i386.deb -rwxr-xr-x 1 root root 746472 Apr 11 17:28 exim_3.22-4_i386.deb -rwxr-xr-x 1 root root 747228 Jul 18 16:50 exim_3.31-1_i386.deb -rwxr-xr-x 1 root root 748988 Aug 14 17:30 exim_3.32-2_i386.deb @debian:/mnt/hda11/var/cache/apt/archives$ My Question: I don't know enough about Debian to know if this is a bug - would you please enlighten me? The msg from CW said, on 8/14, that exim 3.32-1 fixes this. I have exim 3.32-2 in my cache. Q: Since it is over 2 weeks past 8/14, shouldn't my dist-upgrade be using 3.32, which, presumably, has this bug fixed? Why is dist-upgrade using 3.31-1? Now, I did try a dist-upgrade to unstable a week or two ago, and perhaps that's how 3.32-2 got there. (That dist-upgrade was on another system.) I thought that after less than about 2 weeks the packages migrate from unstable to testing. So, that should be done now, therefore. Also, if this _is_ a bug that's not submitted yet, I don't know enough yet about the bug tracking system, etc., to properly submit this. So, I hope _you_, dear reader, will submit this bug to the system, if it is indeed a current, non-submitted bug. Thanks! :) __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com