Your message dated Wed, 15 Aug 2007 00:46:08 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#436901: can't update mount in pbuilder chroot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mount
Version: 2.13~rc2-6
Severity: important
Mount can't be upgraded inside a chroot if nfs volumes are mounted
outside the chroot and nfs-common isn't installed inside the chroot.
This occurs for example in pbuilder and cowbuilder setups.
I guess checking if nfs-common is actually installed before doing
the nfs check in preinst would solve this.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.22.1 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mount depends on:
ii libc6 2.6-5 GNU C Library: Shared libraries
ii libselinux1 2.0.15-2+b1 SELinux shared libraries
ii libvolume-id0 0.113-3 libvolume_id shared library
Versions of packages mount recommends:
ii nfs-common 1:1.1.0-13 NFS support files common to client
-- no debconf information
--- End Message ---
--- Begin Message ---
Fixed: 2.13~rc2-7
On Tue, Aug 07, 2007 at 02:11:03PM +0200, Bas Zoetekouw wrote:
> I guess checking if nfs-common is actually installed before doing
> the nfs check in preinst would solve this.
Done in -7
lamont
--- End Message ---
