sru request for update-manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-manager
Sru request for update-manager:
update-manager (1:0.59.22) feisty-proposed; urgency=low
* DistUpgrade/
- fix free space check when the dir checked is a symlink
(LP#106804)
- increase minAge for the apt cleanup cron job during the upgrade
to fix race for people with very slow network (LP#109548)
* cdromupgrade:
- do not call any authentication mechanism, that is the
responsib
* DistUpgrade/
- fix a bug in the cdrom progress (LP#107451)
* DistUpgrade/
- send correct package failure information to log (LP#109209)
* DistUpgrade/
- Fix bug report URL in crash dialogue (LP#108969)
* UpdateManager/
- fix in I-M-S 304 handling (LP#109216)
* DistUpgrade/
- check RemovalBlacklist early when removing a package to
work-around crash in problem resolver (LP#109014)
-- Michael Vogt <email address hidden> Tue, 24 Apr 2007 12:59:59 +0200
Each change has a diff in codebrowser, I will attach a full debdiff here for completness
TBH I do not think that bug 109548 is appropriate for an SRU. It has a lot of newly introduced code, modifies configuration files, etc. and the potential impact is not high enough to warrant destabilization (after all, running u-m again should usually fix it?)
Same applies for bug 107451; although the fix is small, it is only cosmetical.
changelog bug: #109209 is attributed to DistUpgradeView Text.py, but is apparently fixed in DistUpgradeView.py.
Can you please give a proper rationale why #106804 needs to go into stable?
Please generally be more verbose in the changelog; 'fix a bug in foo.py' is irrelevant, other descriptions are ok, but should be augmented with explaining the actual impact.