apparmor profile is not disabled on upgrade from jaunty firefox-3.5

Bug #436221 reported by Jamie Strandboge on 2009-09-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox-3.5 (Ubuntu)
High
Jamie Strandboge
Karmic
High
Jamie Strandboge

Bug Description

Binary package hint: firefox-3.5

The preinst script handles upgrades during the Karmic cycle, but not from Jaunty to Karmic, since Jaunty's 3.5 is already higher than what was in Karmic at the time the profile was introduced.

Related branches

Changed in firefox-3.5 (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
importance: Undecided → High
status: New → In Progress
Jamie Strandboge (jdstrand) wrote :

Hmmm... I see that the versioning accomplishes this just fine. Sorry for the noise.

Changed in firefox-3.5 (Ubuntu):
importance: High → Undecided
status: In Progress → Invalid
Jamie Strandboge (jdstrand) wrote :

I am clearly not thinking properly. This *is* an issue as soon as we upgrade firefox-3.5 to 3.5.3.

Changed in firefox-3.5 (Ubuntu):
importance: Undecided → High
status: Invalid → In Progress
tags: added: regression-potential
Changed in firefox-3.5 (Ubuntu):
milestone: none → ubuntu-9.10-beta
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox-3.5 - 3.5.3+build1+nobinonly-0ubuntu3

---------------
firefox-3.5 (3.5.3+build1+nobinonly-0ubuntu3) karmic; urgency=low

  [ Jamie Strandboge <email address hidden> ]
  * disable profile on upgrades from earlier Ubuntu releases (LP: #436221)
    - update debian/firefox-3.5.preinst.in

 -- Alexander Sack <email address hidden> Mon, 28 Sep 2009 10:35:46 +0200

Changed in firefox-3.5 (Ubuntu Karmic):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers