update-manager needs to handle mount/nfs-common transition for gutsy

Bug #141559 reported by LaMont Jones
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

Binary package hint: update-manager

with 2.13, upstream for util-linux dropped nfs support, which is now handled by nfs-common (which now delivers mount.nfs)

Debian fails with the code below in mount.preinst, update-manager should make sure it's dealt with for gutsy:
        if [ Debian = "$DISTRO" ]; then
          if [ -f /var/lib/dpkg/info/nfs-common.list ] && [ -f /proc/mounts ]; then
              NFS_IN_USE=$(sed -n '/^[^ ]* [^ ]* nfs /p' /proc/mounts)
          else
              NFS_IN_USE=""
          fi
          if [ -n "$NFS_IN_USE" ] && [ ! -x /sbin/mount.nfs ] ; then
              cat << EOF
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.
EOF
              exit 1
          fi
        fi

If there are active nfs mounts, then nfs-common (>= 1:1.1.0-13) must be installed.

Revision history for this message
Alex Mauer (hawke) wrote :

It should perhaps be noted that sfs also counts as an nfs mount, even though the user may not think of it as such.

Revision history for this message
Michael Vogt (mvo) wrote :

<lamont> and then mix that with debian #443466
<ubotu> Debian bug 443466 in mount "mount: upgrade fails if nfs-common is in removed but not purged" [Normal,Open] http://bugs.debian.org/443466

Michael Vogt (mvo)
Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → High
status: New → Confirmed
Revision history for this message
LaMont Jones (lamont) wrote :

443466 does not apply to ubuntu, since the check is only done on Debian. (and fixed in 2.13-7, which has not been propagated to ubuntu yet.)

Likewise, it may be that this is "not a bug" in ubuntu, since feisty dpkg has Breaks: support, and therefore the ubuntu uploads indicate that mount Breaks: nfs-common (<<1:1.1.0-7), which (I believe) will cause nfs-common to be upgraded in the same pass as mount being installed.

If my understanding is correct, please close the bug. If it's not, please remind me to update the GutsyGibbon/ReleaseNotes page.

Revision history for this message
Michael Vogt (mvo) wrote :

If feisty nfs works without nfs-common is installed, then update-manager needs to ensure that there is a transition by checking /proc/mounts for nfs mounts.

If there is no way in feisty to have nfs mounts without nfs-common, then the breaks should ensure the right ordering.

My tests indicate that nfs mounting does work in feisty without nfs-common so I guess transitional code is required.

Changed in update-manager:
status: Confirmed → Fix Committed
Revision history for this message
Michael Vogt (mvo) wrote :

update-manager (1:0.76) gutsy; urgency=low

  [ Michael Vogt ]
  * DistUpgrade/DistUpgradeCache.py:
    - ensure that the util-linux -> nfs-common transition
      happens (LP: #141559)

  [ Jonathan Riddell ]
  * DistUpgrade/DistUpgradeViewKDE.py:
    - copy Xauthority file if necessary

 -- Michael Vogt <email address hidden> Mon, 24 Sep 2007 19:49:17 +0200

Changed in update-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.