update-manager doing hardy->lucid should stop apparmor
Bug #559433 reported by
Kees Cook
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: update-manager
In an effort to avoid potentially confusing situations like bug 556343, we would like to have apparmor stopped before starting package upgrades on a hardy->lucid upgrade (though not in karmic->lucid, this is currently expected to be okay). Just calling "sudo /etc/init.
While the above bug doesn't appear to cause us any "real" problems, we'd like to be a little more proactive towards fixing possible unknown breakages and at least avoid the scary warnings.
Thanks!
Changed in update-manager (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
milestone: | none → ubuntu-10.04 |
Changed in update-manager (Ubuntu Lucid): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package update-manager - 1:0.134.1
---------------
update-manager (1:0.134.1) lucid; urgency=low
* DistUpgrade/ DistUpgradeCont roller. py: FRONTEND= noninteractive" on pkg failure (LP: #538206) DistUpgradeQuir ks.py: DistUpgradeCach e.py, DistUpgrade/ build-tarball. sh: DistUpgradeView Text.py: Core/MyCache. py: ubuntu. com uses Core/MetaReleas e.py:
- honor "DEBIAN_
* DistUpgrade/
- stop apparmor before dpkg starts on hardy -> lucid upgrades to
avoid potentially confusing error messages during the upgrade
(LP: #559433)
* DistUpgrade/
- include obselte nvidia pkgnames to properly transition old
to new drivers (LP: #553369)
* DistUpgrade/
- show packages that will be removed (because they were auto installed)
as well (LP: #558438)
- fix i18n bug in details output
* UpdateManager/
- support third party changelogs by using ArchiveURI() and
append a similar structure as changelogs.
(LP: #45129)
* UpdateManager/
- do not crash if meta-release file can not be parsed, just remove
the broken file instead (LP: #558396)
-- Michael Vogt <email address hidden> Mon, 12 Apr 2010 18:32:59 +0200