do-release-upgrade calculates /boot size from apt and does not check against actual /boot

Bug #287826 reported by ClaesBas
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

The script do-release-upgrade downloads the file intrepid.tar.gz which does some checks in DistUpgradeController.py ... That checks calculate from what it thinks is installed, NOT what's physically free on the partition!

If you have removed old kernals and friends directly from /boot , then do-release-upgrade could say for example that you need to have 88.1M free space on /boot (even if you only have 12M files of 100M).

I think the checks should (instead/also) check what is physically free.

Michael Vogt (mvo)
Changed in update-manager:
importance: Undecided → Medium
milestone: none → ubuntu-9.04-beta
status: New → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

Michael, this got milestoned by someone. Setting you as assignee. If you think that this shouldn't be milestoned (sounds like it from my perspective), please un-milestone and un-assign as you see fit. Thanks!

Changed in update-manager:
assignee: nobody → mvo
Revision history for this message
Michael Vogt (mvo) wrote :

This should be fixed in jaunty bzr now.

Changed in update-manager (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.110.0

---------------
update-manager (1:0.110.0) jaunty; urgency=low

  * DistUpgrade/DistUpgradeCache.py:
    - take changes in update-initramfs into account when
      calculating the space requirements in /boot (LP: #287826)
    - when doing the space calculation, show the required space
      for each directory (if multiple need more space) LP: #219416
  * DistUpgrade/DevelReleaseAnnouncement:
    - updated for beta
  * UpdateManager/DistUpgradeFetcher.py:
    - set 5s timeout for the ReleaseNotes fetching (LP: #109397)
  * UpdateManager/UpdateManager.py:
    - pass the correct FetchProgress to the release-upgrade fetching
      code instead of the incorrect OpProgress

 -- Michael Vogt <email address hidden> Thu, 19 Mar 2009 16:48:11 +0100

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.

Other bug subscribers

Remote bug watches

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