Does not check if the cache can be locked
Bug #108446 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
Its currently possible the start the release-upgrader and it will not check if it can lock /var/lib/dpkg
| Changed in update-manager: | |
| assignee: | nobody → mvo |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| Changed in update-manager: | |
| status: | Confirmed → Fix Committed |
| Changed in update-manager: | |
| status: | Fix Committed → In Progress |
Revision history for this message
| to be removed (liw) wrote | #1 |
| Changed in update-manager (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
do-release-upgrade on jaunty does check that it can lock, but doesn't check it at the beginning. I think that's reasonable: it does the checking when it actually acquires the lock; doing a check earlier would just introduce a race condition.
Thus I think this bug can be closed. If you disagree, please re-open (and please accept my pre-emptive apologies).