SRU of ubuntu-dev-tools 0.201ubuntu2

Bug #2057716 reported by Steve Langasek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Committed
Undecided
Unassigned
Mantic
Fix Committed
Undecided
Unassigned

Bug Description

[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our Ubuntu developers have access to these improvements.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/UbuntuDevToolsUpdates

autopkgtests will be run for ubuntu-dev-tools as part of the SRU.

The following changes affect how ubuntu-dev-tools interfaces with other packages:

- there are no changes since 0.193ubuntu4 (the last SRUed version) that affect interfaces with other packages.

[Where problems could occur]
These are mostly changes already well-tested in mantic. There is introduction of a few new tools (pm-helper, running-autopkgtests) which pose no risk of regression. There are several small bugfixes in tools (mk-sbuild, pull-*-source, check-mir, syncpackage) that post-date mantic and could cause regressions but the chances of this are low. The biggest change that could be a problem is a complete refactor of the ubuntu-build tool; however, I believe almost no one is using this tool. The most likely users of this tool would be archive admins and I was completely unaware of the existence of this tool in ubuntu-dev-tools until about 3 months ago - I had my own local scripts for retrying builds, and I believe most other people doing mass-retries of failed builds do as well, with the possible exception of Gianfranco who acked my merge. So it's worth risking some short-term issues with behavior changes, in exchange for having a standard and supported tool that Ubuntu devs actually consume for triggering build retries.

Steve Langasek (vorlon)
Changed in ubuntu-dev-tools (Ubuntu):
status: New → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Steve, or anyone else affected,

Accepted ubuntu-dev-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.201ubuntu2~23.10.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 on 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, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in ubuntu-dev-tools (Ubuntu Mantic):
status: New → Fix Committed
tags: added: verification-needed verification-needed-mantic
Changed in ubuntu-dev-tools (Ubuntu Jammy):
status: New → Fix Committed
tags: added: verification-needed-jammy
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Steve, or anyone else affected,

Accepted ubuntu-dev-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/0.201ubuntu2~22.04.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 on 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, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Steve Langasek (vorlon) wrote :

I overlooked reverting the build dependency on the new python3-launchpadlib-desktop package, which I knew I needed to do but then failed to actually handle. Will do a new upload with this fix soon-ish.

tags: added: verification-failed-jammy verification-failed-mantic
removed: verification-needed verification-needed-jammy verification-needed-mantic
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.