Control: tags -1 + moreinfo unreproducible On 06.10.2012 00:41, David Starner wrote: > Package: autofs > Version: 5.0.7-1 > Severity: serious > > $ sudo apt-get install autofs udev > Reading package lists... Done > Building dependency tree > Reading state information... Done > udev is already the newest version. > The following NEW packages will be installed: > autofs
> 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Now this is interesting. autofs 5.0.7 is declared as breaking autofs5 << 5.0.6. Yes when you ask to install new autofs package, apt does not offer to update autofs5 at the same time. Yet you said you have "old autofs5 install" in the subject. However, later you mention that there's NO autofs5 package installed, according to the dpkg -l output -- I think it was installed in the past but not purged. Now, I wonder which version of old autofs5 did you have installed. Because when I do that (install+remove) with squeeze version of autofs5, I can install sid version of autofs just fine. Can it be that you had lenny version of autofs5 maybe, or even something older? > Need to get 720 kB of archives. > After this operation, 1,649 kB of additional disk space will be used. > Do you want to continue [Y/n]? y > Get:1 http://ftp.us.debian.org/debian/ unstable/main autofs amd64 > 5.0.7-1 [720 kB] > Fetched 720 kB in 1s (494 kB/s) > Selecting previously unselected package autofs. > (Reading database ... 278805 files and directories currently installed.) > Unpacking autofs (from .../autofs_5.0.7-1_amd64.deb) ... > Processing triggers for man-db ... > fopen: Permission denied > Setting up autofs (5.0.7-1) ... > Installing new version of config file /etc/init.d/autofs ... > ucfr: Attempt from package autofs to take /etc/auto.master away from > package autofs5 > ucfr: Aborting. This is the following code: # transfer ownership from old autofs5 package case "$(ucfq -w /etc/default/autofs)" in *:autofs5:*) force=--force ;; *) force= ;; esac for map in master net misc smb; do ucfr $force autofs /etc/auto.$map ucf /usr/share/autofs/conffiles/auto.$map /etc/auto.$map done ucfr $force autofs /etc/default/autofs ucf /usr/share/autofs/conffiles/default/autofs /etc/default/autofs we force-transfer ownership only when it currently belongs to autofs5. When old autofs5 is installed, the first ucfq query above on my system returns this: $ ucfq -w /etc/default/autofs /etc/default/autofs:autofs5:Yes:No so it properly uses --force when default/autofs is registered to autofs5. But in your case, apparently, default/autofs is not registered to autofs5, but /etc/auto.master is, and it stays first on the list to transfer ownership. Do you know if there was a version of old autofs which did not register /etc/default/autofs but registered /etc/auto.master? Or maybe it had /etc/default/autofs5 instead of default/autofs? Please show me the output of grep autofs /var/lib/ucf/registry Meanwhile I'll try to make this code fragment more robust by querying ownership for every file it touches instead of just one. Thank you! /mjt > dpkg: error processing autofs (--configure): > subprocess installed post-installation script returned error exit status 4 > Errors were encountered while processing: > autofs > E: Sub-process /usr/bin/dpkg returned an error code (1) > > $ dpkg -l autofs\* > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version > Architecture Description > +++-================================-=====================-=====================-===================================================================== > iF autofs 5.0.7-1 amd64 > kernel-based automounter for Linux > un autofs5 <none> > (no description available) > > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
