* UpdateManager/UpdateManager.py:
- use /var/lib/apt/periodic/update-success-stamp for the
calculation when the last update was performed (LP: #185894)
* DistUpgrade/DistUpgradeController.py:
- if the upgrade can not be calculated in partial upgrade mode,
do not recommend reporting a bug (most likely transient anyway)
* DistUpgradeView/DistUpgradeViewText.py:
- make the restart required question more clear (LP: #155554)
* UpdateManager/Core/DistUpgradeFetcherCore.py:
- tidy up output when show authentication message
* data/update-manager.8:
- man page fixes (LP: #185615)
* update-manager:
- run gtk.init_check() to catch errors when DISPLAY is not
set (pygtk does not do that automatically)
-- Michael Vogt <email address hidden> Wed, 06 Feb 2008 18:11:45 +0100
This bug was fixed in the package update-manager - 1:0.87.5
---------------
update-manager (1:0.87.5) hardy; urgency=low
* UpdateManager/ UpdateManager. py: apt/periodic/ update- success- stamp for the DistUpgradeCont roller. py: /DistUpgradeVie wText.py: Core/DistUpgrad eFetcherCore. py: manager. 8:
- use /var/lib/
calculation when the last update was performed (LP: #185894)
* DistUpgrade/
- if the upgrade can not be calculated in partial upgrade mode,
do not recommend reporting a bug (most likely transient anyway)
* DistUpgradeView
- make the restart required question more clear (LP: #155554)
* UpdateManager/
- tidy up output when show authentication message
* data/update-
- man page fixes (LP: #185615)
* update-manager:
- run gtk.init_check() to catch errors when DISPLAY is not
set (pygtk does not do that automatically)
-- Michael Vogt <email address hidden> Wed, 06 Feb 2008 18:11:45 +0100