Bug#498350: Do not check NFS on upgrade
On Thu, Jun 11, 2009 at 06:06:09PM +1000, Trent W. Buck wrote: > The most obvious way, I suppose, would be for mount to skip the test > if nfs-common is not installed. If nfs-common isn't installed, then > presumably any NFS entries it "sees" in /etc/mtab or /proc/mounts are > either stale or not relevant to the running environment. And that would specifically be the wrong answer, since it is the absence of nfs-common that is the failure case. The situation is: Upgrades of a machine with NFS mounts that do not have nfs-common installed result in a machine that cannot mount NFS mounts, quite possibly necessary in order to have the machine function, including installing packages. Traditional Depends: would result in every machine on the planet having portmapper and nfs-common installed, which would cause the security team to justifiably kill me. The check is one that we should be able to drop for squeeze, since it only matters going from etch to lenny. > If this is a bad idea, I'd appreciate explanatory details from the > maintainer(s) -- currently it looks like this has just been tagged > "wontfix" without any discussion. There was a great deal of discussion on the original bug report, iirc, which was closed when the package was uploaded. lamont -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498350: Do not check NFS on upgrade
On Tue, Sep 09, 2008 at 02:22:46PM +0300, Arie Skliarouk wrote: > I am running debian unstable as a virtual server under OpenVZ. > > The virtual server has [NFS] mounts, that are [re-]mounted using > "bind" option by the physical server. [...] The virtual server [...] > does not have any nfs-* packages installed. > > [...] new version of mount checks for nfs mounts and complain on NFS > mounts already mounted: > > # dpkg -i /var/cache/apt/archives/mount_2.13.1.1-1_i386.deb > (Reading database ... 40284 files and directories currently installed.) > Preparing to replace mount 2.13-7 (using .../mount_2.13.1.1-1_i386.deb) ... > You have NFS mount points currently mounted, and this version of mount > requires that nfs-common be upgraded before NFS mounts will work. I have the same symptoms. Rather than remove the test, I suggest detecting when a virtual environment is in place. The most obvious way, I suppose, would be for mount to skip the test if nfs-common is not installed. If nfs-common isn't installed, then presumably any NFS entries it "sees" in /etc/mtab or /proc/mounts are either stale or not relevant to the running environment. If this is a bad idea, I'd appreciate explanatory details from the maintainer(s) -- currently it looks like this has just been tagged "wontfix" without any discussion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498350: Do not check NFS on upgrade
Package: mount Version: 2.13.1.1-1 I am running debian unstable as a virtual server under openvz virtual server technology. The virtual server has several mounts, that are mounted using "bind" option by the physical server. One of these mounts is NFS filesystem that is mounted on the physical server and "exported" using "bind" option to the virtual servers. The virtual server itself can not do anything with these mounts. It even does not have any nfs-* packages installed. The mount command thought, shows the filesystem as NFS mounted: # mount | grep nfs fs-home:/home on /home type nfs (rw,relatime,vers=3,rsize=524288,wsize=524288,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.11.24) All this is nice and dandy, but new version of mount checks for nfs mounts and complain on NFS mounts already mounted: # dpkg -i /var/cache/apt/archives/mount_2.13.1.1-1_i386.deb (Reading database ... 40284 files and directories currently installed.) Preparing to replace mount 2.13-7 (using .../mount_2.13.1.1-1_i386.deb) ... You have NFS mount points currently mounted, 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.1.1-1_i386.deb (--install): subprocess pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/mount_2.13.1.1-1_i386.deb tester:~# Please advise. -- Arie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
