Public bug reported: TODO once the next devscripts version has been uploaded
## FFE ## [Rationale] 2.6.12 includes the rmadison change to swap from the madison.cgi endpoint to the Launchpad-API based implementation [1] which we would like to avoid adding an Ubuntu delta for. This change is critical to ensure rmadison functionality, since the old endpoint won't be migrated to the new Canonical cloud and will be shut down soon (meaning next few months). It also includes the lzip -> plzip swap relevant for the plzip MIR [2]. [ Scope ] The package is not seeded, but important developer tooling that many people and automations rely on. $ seeded-in-ubuntu devscripts devscripts's binaries are not seeded. Full git diff: https://salsa.debian.org/debian/devscripts/-/compare/c778373fc78af48834c953e35a8363126b74f130...main?from_project_id=18475 [ Regression Potential ] * Include this section for new upstream microreleases. * Think about what the upload changes in the software. Imagine the change is wrong or breaks something else: how would this show up? * It is assumed that any FFe candidate is well-tested before the upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This must never be "None" or "Low", or entirely an argument as to why your upload is low risk. * This both shows the release team that the risks have been considered, and provides guidance to testers in regression-testing the update. [ Testing ] * Smoke test: - PPA: <link to ppa> - Build: <link to the build logs> - Installation: <link to the installation test> - Upgrade: <link to the upgrade test> - Autopkgtest: <autopkgtest results> - Does it break other packages: <link related bugs> * If other testing is appropriate to perform before landing this update, this should also be described here. [ Other Info ] * Anything else you think is useful to include. * Anticipate questions from users, the Release Team, the +1 maintenance team, the security team, and the Technical Board, and address these questions in advance. [ Original Description ] * Include the original bug description, if present. [1]: https://salsa.debian.org/debian/devscripts/-/merge_requests/658 [2]: https://bugs.launchpad.net/ubuntu/+source/plzip/+bug/2154054 ** Affects: devscripts (Ubuntu) Importance: Undecided Status: New ** Description changed: TODO once the next devscripts version has been uploaded ## FFE ## [Rationale] 2.6.12 includes the rmadison change to swap from the madison.cgi endpoint to the Launchpad-API based implementation [1] which we would like to avoid adding an Ubuntu delta for. This change is critical to ensure rmadison functionality, since the old endpoint won't be migrated to the new Canonical cloud and will be shut down soon (meaning next few months). + It also includes the lzip -> plzip swap relevant for the plzip MIR [2]. + [ Scope ] The package is not seeded, but important developer tooling that many people and automations rely on. $ seeded-in-ubuntu devscripts devscripts's binaries are not seeded. - - Full git diff: https://salsa.debian.org/debian/devscripts/-/compare/c778373fc78af48834c953e35a8363126b74f130...main?from_project_id=18475 + Full git diff: + https://salsa.debian.org/debian/devscripts/-/compare/c778373fc78af48834c953e35a8363126b74f130...main?from_project_id=18475 [ Regression Potential ] * Include this section for new upstream microreleases. * Think about what the upload changes in the software. Imagine the - change is wrong or breaks something else: how would this show up? + change is wrong or breaks something else: how would this show up? * It is assumed that any FFe candidate is well-tested before the - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the event - of a regression. + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the event + of a regression. * This must never be "None" or "Low", or entirely an argument as to why - your upload is low risk. + your upload is low risk. * This both shows the release team that the risks have been considered, - and provides guidance to testers in regression-testing the update. + and provides guidance to testers in regression-testing the update. [ Testing ] * Smoke test: - - PPA: <link to ppa> - - Build: <link to the build logs> - - Installation: <link to the installation test> - - Upgrade: <link to the upgrade test> - - Autopkgtest: <autopkgtest results> - - Does it break other packages: <link related bugs> + - PPA: <link to ppa> + - Build: <link to the build logs> + - Installation: <link to the installation test> + - Upgrade: <link to the upgrade test> + - Autopkgtest: <autopkgtest results> + - Does it break other packages: <link related bugs> * If other testing is appropriate to perform before landing this - update, this should also be described here. + update, this should also be described here. [ Other Info ] * Anything else you think is useful to include. * Anticipate questions from users, the Release Team, - the +1 maintenance team, the security team, and the Technical Board, - and address these questions in advance. + the +1 maintenance team, the security team, and the Technical Board, + and address these questions in advance. [ Original Description ] - * Include the original bug description, if present. + * Include the original bug description, if present. [1]: https://salsa.debian.org/debian/devscripts/-/merge_requests/658 + [2]: https://bugs.launchpad.net/ubuntu/+source/plzip/+bug/2154054 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167756 Title: WIP: [FFe]: Please sync 2.6.12 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/2167756/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
