do not overwrite logs
Bug #111819 reported by
Michael Vogt
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt | ||
Bug Description
Binary package hint: update-manager
On a edgy->feisty upgrade a logfile called /var/log/
Related branches
| Changed in update-manager: | |
| assignee: | nobody → mvo |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Changed in update-manager: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in update-manager: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package update-manager - 1:0.97
---------------
update-manager (1:0.97) jaunty; urgency=low
* UpdateManager/
- remove debug message (LP: #310046)
* UpdateManager/
- when initializing the proxy configuration, do in this
order:
* check apt setting
* check synaptic setting
* check users gconf
* check http_proxy environment
(LP: #24250)
* UpdateManager/
- ensure correct error message if downloading failed
(LP: #113658)
- when fetching from mirrors, add fallback if the mirror
is too loaded to cope
- improve logic that detects what mirror is in use by
sources.list inspection (LP: #107983)
* DistUpgrade/
- re-factor and make code more modular
- do not overwrite existing log files on upgrade
(LP: #111819)
* reorganize the imports and get rid of "Common" submodule
and merge that all into "Core"
* improve the debug output via the "DEBUG_
environment
-- Michael Vogt <email address hidden> Mon, 26 Jan 2009 17:26:40 +0100