Package: base-files
Version: 7.1wheezy6
Severity: normal

Dear Maintainer,

Since sysadmins tend to (and are often told to) use /mnt for
temporary mounts, and sometimes forget those mounts and they go
stale (nfs), a package (in this case 'base-files') that includes
/mnt in the files section will result in a complete failure to
install.

------------------------------------------------
    SERVER:~# type aptup
    aptup is a function
    aptup () 
    { 
        read -p "Include any available kernel packages in update? [n]: " reply;
        test "$reply" || reply=no;
        aptitude update && if echo $reply | egrep -iq ^y; then
            aptitude full-upgrade;
        else
            aptitude install $(aptitude search -F %p '~U 
!~n"linux-(image|header)"');
        fi && aptitude clean
    }

    SERVER:~# aptup
    Include any available kernel packages in update? [n]: n
    ....
    The following packages will be upgraded: 
      a2ps apache2 apache2-mpm-prefork apache2-utils apache2.2-bin 
apache2.2-common apt apt-utils base-files bind9-host cups-bsd cups-client 
cups-common curl dbus dbus-x11 dnsutils 
    ....

    Preparing to replace base-files 7.1wheezy2 (using 
.../base-files_7.1wheezy6_amd64.deb) ...
--> Unpacking replacement base-files ...
    dpkg: error processing 
/var/cache/apt/archives/base-files_7.1wheezy6_amd64.deb (--unpack):
-->  unable to stat `./mnt' (which I was about to install): Stale NFS file 
handle
    Errors were encountered while processing:
     /var/cache/apt/archives/base-files_7.1wheezy6_amd64.deb
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    A package failed to install.  Trying to recover:
                                             
    SERVER:~# ls /mnt
    ls: cannot access /mnt: Stale NFS file handle
(d'oh sysadmin mounted other server months ago, which is now ESTALE,
but should not result in a fatal install failure in base-files)

    SERVER:X# dpkg --fsys-tarfile - 
/var/cache/apt/archives/base-files_7.1wheezy6_amd64.deb | tar tvf - | grep /mnt
--> drwxr-xr-x root/root         0 2014-06-11 21:07 ./mnt/
------------------------------------------------

I personally tend to use /{a,b,..} (Solaris background) to do my
temporary mounts, which helps avoid this condition, but still, if
you can modify the packaging script to avoid this (apparently)*
useless directory inclusion, that'd be desired. (this is the second
time in a few years i've run into this issue)

* 'find . -xdev -type f -exec grep -al '/mnt' {} +' on extract .deb
  doesn't match anything, so i don't think a postinst/preinst is
  using /mnt


-- System Information:
*** NOTE: I'm running bugreport on another system, so the following
*** isn't accurate for the system in question, but it is also
*** irrelevant:
Debian Release: 7.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.0.1+dfsg-2.1
ii  mawk [awk]  1.3.3-17

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information


Thanks,
--stephen


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to