[master] nfs-common makes upgrade calculation impossible (was: Could not calculate the upgrade)

Bug #157763 reported by Kallewoof
56
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Invalid
High
Unassigned
Hardy
Fix Released
High
Michael Vogt

Bug Description

TEST CASE:
1. install dapper server
2. install "nfs-common" and "update-manager-core"
3. run "sudo do-release-upgrade -d"
4. verify that it fails to calculate the upgrade

5. enabled dapper-proposed
6. run "sudo do-release-upgrade -d"
7. verify that the upgrade can be calculated

Revision history for this message
Kallewoof (kalle-enrogue) wrote :
Revision history for this message
Kallewoof (kalle-enrogue) wrote :
Revision history for this message
Kallewoof (kalle-enrogue) wrote :
Revision history for this message
Kallewoof (kalle-enrogue) wrote :
Michael Vogt (mvo)
Changed in update-manager:
importance: Undecided → High
Revision history for this message
Raymond (raymond-m) wrote :

Could not calculate the upgrade
report bug against update-manager
Hardy Heron Alpha 2

Revision history for this message
Elias K Gardner (zorkerz) wrote :

I get this error "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report." I get this when running a partial upgrade as part of the normal update process in hardy heron. I don't know if its helpful or not to throw in my copies of these files so I will.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

main.log and term.log also appear in my /var/log/dist-upgrade/ but they have not been modified in 4 days so I would imagine do not have relevant info if otherwise let me know.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Several duplicates. Setting to confirmed

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

The problem with the dapper->hardy upgrade calculation is that libnfsidmap1 has priority "standard" while libnfsidmap2 has priority "optinal". That makes apt prefer the former one over the later one and that breaks the upgrade.

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

The alternative to updating the priority would be to add a (empty) transitional libnfsidmap1 package.

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

Unfortunately this can not be fixed with a quirks rule in update-manager because the apt resolver breaks in cache.upgrade(True) already before any quirk rules can be applied.

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

I uploaded a new util-linux package that adds a conflicts against libnfsidmap1 to mount. That helps the resolver remove it early. I milestone this as it breaks for a lot of dapper users (with nfs-common installed).

Changed in update-manager:
milestone: none → ubuntu-8.04.1
description: updated
Revision history for this message
Michael Vogt (mvo) wrote :

Diff for the changes:

diff -u util-linux-2.13.1/debian/changelog util-linux-2.13.1/debian/changelog
--- util-linux-2.13.1/debian/changelog
+++ util-linux-2.13.1/debian/changelog
@@ -1,3 +1,11 @@
+util-linux (2.13.1-5ubuntu2) hardy-proposed; urgency=low
+
+ * debian/control:
+ - add a conflict against "libnfsidmap1" to "mount" to help the
+ apt resolver calculate dapper->hardy upgrades (LP: #157763)
+
+ -- Michael Vogt <email address hidden> Tue, 29 Apr 2008 12:25:51 +0200
+
 util-linux (2.13.1-5ubuntu1) hardy; urgency=low

   * New Debian version: remaining ubuntu changes:
diff -u util-linux-2.13.1/debian/control util-linux-2.13.1/debian/control
--- util-linux-2.13.1/debian/control
+++ util-linux-2.13.1/debian/control
@@ -45,6 +45,7 @@
 Pre-Depends: ${shlibs:Depends}
 Suggests: nfs-common (>=1:1.1.0-13)
 Breaks: nfs-common (<<1:1.1.0-7)
+Conflicts: libnfsidmap1
 Description: Tools for mounting and manipulating filesystems
  This package provides the mount(8), umount(8), swapon(8),
  swapoff(8), and losetup(8) commands.

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

I just verified the fix in my automatic upgrade tester, with the updated package it works, without it it fails.

Changed in update-manager:
assignee: nobody → mvo
status: Confirmed → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into hardy-proposed, please test.

Changed in util-linux:
assignee: nobody → mvo
importance: Undecided → High
milestone: none → ubuntu-8.04.1
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

This is not relevant for intrepid, only for dapper->hardy upgrades.

Changed in util-linux:
assignee: mvo → nobody
milestone: ubuntu-8.04.1 → none
status: Fix Committed → Invalid
Revision history for this message
Brian Murray (brian-murray) wrote :

I have verified the fix by following the test case provided. Without dapper-proposed enabled I was unable to calculate the upgrade when nfs-common was installed. After enabling dapper-proposed the upgrade was calculated and started successfully.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates.

Changed in util-linux:
status: Fix Committed → Fix Released
Revision history for this message
Funkwarrior (funkwarrior-spam) wrote :

It's possibile there are problems with the ntfs-3g? I've problem with myfstab configuration...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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