Ubuntu

Update to 25.0.1

Reported by Chris Coulson on 2013-11-15
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Undecided
Unassigned
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 25.0.1+build1-0ubuntu0.13.10.1

---------------
firefox (25.0.1+build1-0ubuntu0.13.10.1) saucy-security; urgency=low

  * New upstream stable release (FIREFOX_25_0_1_BUILD1)
    - see LP: #1251576 for USN information
 -- Chris Coulson <email address hidden> Fri, 15 Nov 2013 10:27:58 +0000

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 25.0.1+build1-0ubuntu0.12.04.1

---------------
firefox (25.0.1+build1-0ubuntu0.12.04.1) precise-security; urgency=low

  * New upstream stable release (FIREFOX_25_0_1_BUILD1)
    - see LP: #1251576 for USN information
 -- Chris Coulson <email address hidden> Fri, 15 Nov 2013 10:34:19 +0000

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 25.0.1+build1-0ubuntu0.12.10.1

---------------
firefox (25.0.1+build1-0ubuntu0.12.10.1) quantal-security; urgency=low

  * New upstream stable release (FIREFOX_25_0_1_BUILD1)
    - see LP: #1251576 for USN information
 -- Chris Coulson <email address hidden> Fri, 15 Nov 2013 10:33:13 +0000

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Bib (bybeu) wrote :

Hi
What is this "see LP: #1251576 for USN information" that directly loops to itself?

Chris Coulson (chrisccoulson) wrote :

Oops, sorry, I didn't update the bug

description: updated
Andi Hechtbauer (anti-dotu) wrote :

Does this address any or all of CVE-2013-1739, CVE-2013-1741, CVE-2013-2566, CVE-2013-5605, CVE-2013-5606, CVE-2013-5607?

Or different known (as in: has a CVE Number) issue(s)?

If so, I suggest putting the specifics of this information into the changelog and description of this ticket instead of "..." or a reference to the empty ticket.

Chris Coulson (chrisccoulson) wrote :

Did you not read the USN?

We don't add them to the changelog because the issues are not public when we build the package. Putting them in the changelog would require us to delay starting builds until after Mozilla have actually released, which would add a significant delay to our release. We use a placeholder bug report instead, and then link the USN from it after release

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers