Package: mount
Version: 2.12r-19
Severity: grave
Justification: renders package unusable

It seems to be impossible to install the latest version of
mount in unstable:

# apt-get install mount nfs-common
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nfs-common is already the newest version.
The following packages will be upgraded:
  mount
1 upgraded, 0 newly installed, 0 to remove and 65 not upgraded.
Need to get 0B/133kB of archives.
After unpacking 28.7kB disk space will be freed.
(Reading database ... 106061 files and directories currently installed.)
Preparing to replace mount 2.12r-19 (using .../mount_2.13~rc2-4_i386.deb) ...
You have NFS mounts, and this version of mount requires that nfs-common
be upgraded before NFS mounts will work.

Aborting install.
dpkg: error processing /var/cache/apt/archives/mount_2.13~rc2-4_i386.deb 
(--unpack):
 subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/mount_2.13~rc2-4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

# dpkg -l | grep -i nfs-common
ii  nfs-common                       1:1.1.0-13                 NFS support 
files common to client and serve


It might be relevant to note that this computer is running diskless, 
with root on NFS.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22.1 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=C, LC_CTYPE=no_NO.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages mount depends on:
ii  libblkid1                     1.40.2-1   block device id library
ii  libc6                         2.6-5      GNU C Library: Shared libraries
ii  libuuid1                      1.40.2-1   universally unique id library

mount recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to