SRU of change to phased updater percentage calculation to consider source not binary packages

Bug #1192332 reported by Brian Murray
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Won't Fix
Undecided
Unassigned
Raring
Fix Released
Medium
Brian Murray

Bug Description

The following change in saucy should be SRU'ed to raring as that is where we will first be implementing phased updates.

update-manager (1:0.187) saucy; urgency=low

  [ Brian Murray ]
  * Modify phased update percentage to use source packages and not binary
    packages, additionally add a test for this.

 -- Brian Murray <email address hidden> Wed, 05 Jun 2013 10:02:51 -0700

[ Test Case ]
The update to update-manager includes a test case which can be run in the source package by running nosetests3, or in adt-run.

[ Regression Potential ]
The change only affects the calculation for installing updates with a Phased-Update-Percentage set of which there are none now, so there is little chance for regression.

Changed in update-manager (Ubuntu):
status: New → Won't Fix
Changed in update-manager (Ubuntu Raring):
status: New → In Progress
assignee: nobody → Brian Murray (brian-murray)
importance: Undecided → Medium
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Brian, or anyone else affected,

Accepted update-manager into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/update-manager/1:0.186.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in update-manager (Ubuntu Raring):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote :

I tested this by downloading the source package (apt-get --download-only update-manager) on a raring system and running nosetests3 in the tests directory of the extracted package. This initially failed as I did not have the new version of update-manager installed. After installing update-manager version 1:0.186.1 the test passed.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Colin Watson (cjwatson) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.186.1

---------------
update-manager (1:0.186.1) raring-proposed; urgency=low

  * Modify phased update percentage to use source packages and not binary
    packages, additionally add a test for this. (LP: #1192332)
 -- Brian Murray <email address hidden> Fri, 07 Jun 2013 15:54:23 -0700

Changed in update-manager (Ubuntu Raring):
status: Fix Committed → Fix Released
Revision history for this message
Terrius Richardson (terriusrichardson662) wrote :

want open package manager

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.