[Canonical-ubuntu-qa] [Bug 2076381] Re: [MIR] retry
** Also affects: retry (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: retry (Ubuntu Oracular) Importance: Undecided Status: Fix Released ** Also affects: retry (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry Status in retry package in Ubuntu: Fix Released Status in retry source package in Jammy: New Status in retry source package in Noble: New Status in retry source package in Oracular: Fix Released Bug description: [Availability] The package `retry` is already in Ubuntu universe. The package `retry` build for the architectures it is designed to work on. It currently builds and works for architectures: any Link to package https://launchpad.net/ubuntu/+source/retry [Rationale] This package is required in ubuntu/main as it is a dependency for `autopkgtest`, which is already in main (https://launchpad.net/ubuntu/+source/autopkgtest). Also, this package only consist of a single binary produced from less than 700 lines of quite clear modern C, including error handling and built-in usage (--help). It basically eases creating retry loop in scripts, with non trivial features such as variable delay between retries, and stdout/stderr handling. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/retry/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=retry - Upstream's bug tracker, e.g., GitHub Issues: https://github.com/minfrin/retry/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because there is no test suite in the upstream repository. - The package runs a non-trivial autopkgtest, and is currently passing on all architectures, link to test logs: https://autopkgtest.ubuntu.com/packages/retry - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This package does not yield massive lintian Warnings, Errors - https://buildd.debian.org/status/fetch.php?pkg=retry&arch=arm64&ver=1.0.5-3&stamp=1674427627&raw=1 - `lintian --pedantic` doesn't yield anything - This package does not rely on obsolete or about to be demoted packages. - The package will not be installed by default - Packaging and build is easy, link to debian/rules: https://git.launchpad.net/ubuntu/+source/retry/tree/debian/rules?h=applied/1.0.5-3&id=30ac5a739df4896a8094615af83ecb9962806f9e [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - I suggest the owning team to be Foundations, more specifically Ubuntu Release Management Team, and as part of that team, I certify that we agree to maintain the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built within the last 3 months in PPA - Build link on launchpad: https://launchpad.net/~hyask/+archive/ubuntu/tests/+build/28725690 [Background information] The Package description explains the package well. Upstream Name is `retry` Link to upstream project: https://github.com/minfrin/retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2076381] Re: [MIR] retry
REVIEW FOR NOBLE: $ rmadison retry retry | 1.0.4-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry | 1.0.4-3 | jammy/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry | 1.0.5-3 | noble/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry | 1.0.5-3 | oracular | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry has the same version in both O and N. All dependencies (lib6) already in main. MIR team ACK. ** Changed in: retry (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry Status in retry package in Ubuntu: Fix Released Status in retry source package in Jammy: New Status in retry source package in Noble: In Progress Status in retry source package in Oracular: Fix Released Bug description: [Availability] The package `retry` is already in Ubuntu universe. The package `retry` build for the architectures it is designed to work on. It currently builds and works for architectures: any Link to package https://launchpad.net/ubuntu/+source/retry [Rationale] This package is required in ubuntu/main as it is a dependency for `autopkgtest`, which is already in main (https://launchpad.net/ubuntu/+source/autopkgtest). Also, this package only consist of a single binary produced from less than 700 lines of quite clear modern C, including error handling and built-in usage (--help). It basically eases creating retry loop in scripts, with non trivial features such as variable delay between retries, and stdout/stderr handling. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/retry/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=retry - Upstream's bug tracker, e.g., GitHub Issues: https://github.com/minfrin/retry/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because there is no test suite in the upstream repository. - The package runs a non-trivial autopkgtest, and is currently passing on all architectures, link to test logs: https://autopkgtest.ubuntu.com/packages/retry - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This package does not yield massive lintian Warnings, Errors - https://buildd.debian.org/status/fetch.php?pkg=retry&arch=arm64&ver=1.0.5-3&stamp=1674427627&raw=1 - `lintian --pedantic` doesn't yield anything - This package does not rely on obsolete or about to be demoted packages. - The package will not be installed by default - Packaging and build is easy, link to debian/rules: https://git.launchpad.net/ubuntu/+source/retry/tree/debian/rules?h=applied/1.0.5-3&id=30ac5a739df4896a8094615af83ecb9962806f9e [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - I suggest the owning team to be Foundations, more specifically Ubuntu Release Management Team, and as part of that team, I certify that we agree to maintain the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built within the last 3 months in PPA - Build link on launchpad: https://launchpad.net/~hyask/+archive/ubuntu/tests/+build/28725690 [Background information] The Package description explains the package well. Upstream Name is `retry` Link to upstream project: https://github.com/minfrin/retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2076381] Re: [MIR] retry
REVIEW FOR JAMMY: $ rmadison retry retry | 1.0.4-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry | 1.0.4-3 | jammy/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry | 1.0.5-3 | noble/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x retry | 1.0.5-3 | oracular | source, amd64, arm64, armhf, ppc64el, riscv64, s390x In Jammy retry version is 1.0.4-3. The changes between 1.0.4 and 1.0.5 are trivial(see attached diff) and do not change the essence of previous review. Again no further dependencies to get in main. MIR team ACK. ** Attachment added: "retry-diff_1-0-4_1-0-5" https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+attachment/5816295/+files/retry-diff_1-0-4_1-0-5 ** Changed in: retry (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry Status in retry package in Ubuntu: Fix Released Status in retry source package in Jammy: In Progress Status in retry source package in Noble: In Progress Status in retry source package in Oracular: Fix Released Bug description: [Availability] The package `retry` is already in Ubuntu universe. The package `retry` build for the architectures it is designed to work on. It currently builds and works for architectures: any Link to package https://launchpad.net/ubuntu/+source/retry [Rationale] This package is required in ubuntu/main as it is a dependency for `autopkgtest`, which is already in main (https://launchpad.net/ubuntu/+source/autopkgtest). Also, this package only consist of a single binary produced from less than 700 lines of quite clear modern C, including error handling and built-in usage (--help). It basically eases creating retry loop in scripts, with non trivial features such as variable delay between retries, and stdout/stderr handling. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/retry/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=retry - Upstream's bug tracker, e.g., GitHub Issues: https://github.com/minfrin/retry/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because there is no test suite in the upstream repository. - The package runs a non-trivial autopkgtest, and is currently passing on all architectures, link to test logs: https://autopkgtest.ubuntu.com/packages/retry - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This package does not yield massive lintian Warnings, Errors - https://buildd.debian.org/status/fetch.php?pkg=retry&arch=arm64&ver=1.0.5-3&stamp=1674427627&raw=1 - `lintian --pedantic` doesn't yield anything - This package does not rely on obsolete or about to be demoted packages. - The package will not be installed by default - Packaging and build is easy, link to debian/rules: https://git.launchpad.net/ubuntu/+source/retry/tree/debian/rules?h=applied/1.0.5-3&id=30ac5a739df4896a8094615af83ecb9962806f9e [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - I suggest the owning team to be Foundations, more specifically Ubuntu Release Management Team, and as part of that team, I certify that we agree to maintain the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built within the last 3 months in PPA - Build link on launchpad: https://launchpad.net/~hyask/+archive/ubuntu/tests/+build/28725690 [Background information] The Package description explains the package well. Upstream Name is `retry` Link to upstream project: https://github.com/minfrin/retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subs
[Canonical-ubuntu-qa] [Bug 2076381] Re: [MIR] retry
So, retry are in the release pocket for focal and noble, it seems we can’t do post-release promotion in those pockets (which are surely read only): I’m getting: Override component to main retry 1.0.5-3 in noble: universe/misc -> main retry 1.0.5-3 in noble amd64: universe/utils/optional/100% -> main retry 1.0.5-3 in noble arm64: universe/utils/optional/100% -> main retry 1.0.5-3 in noble armhf: universe/utils/optional/100% -> main retry 1.0.5-3 in noble ppc64el: universe/utils/optional/100% -> main retry 1.0.5-3 in noble riscv64: universe/utils/optional/100% -> main retry 1.0.5-3 in noble s390x: universe/utils/optional/100% -> main Override [y|N]? y Traceback (most recent call last): File "/home/didrocks/tools/bin/ubuntu-archive-tools/./change-override", line 231, in main() File "/home/didrocks/tools/bin/ubuntu-archive-tools/./change-override", line 227, in main change_overrides(options, args) File "/home/didrocks/tools/bin/ubuntu-archive-tools/./change-override", line 147, in change_overrides if publication.changeOverride(**kwargs): File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 642, in __call__ response, content = self.root._browser._request( File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 484, in _request raise error lazr.restfulclient.errors.BadRequest: HTTP Error 400: Bad Request Response headers: --- -content-encoding: gzip connection: close content-length: 40 content-security-policy: frame-ancestors 'self'; content-type: text/plain;charset=utf-8 date: Thu, 12 Sep 2024 15:20:05 GMT server: gunicorn status: 400 strict-transport-security: max-age=15552000 transfer-encoding: chunked vary: Accept,Accept-Encoding x-content-type-options: nosniff x-frame-options: SAMEORIGIN x-launchpad-revision: 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0 x-lazr-notifications: [] x-powered-by: Zope (www.zope.org), Python (www.python.org) x-request-id: 4a0db52c-7b76-4da2-a113-61b5fcaa2572 x-vcs-revision: 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0 x-xss-protection: 1; mode=block --- Response body: --- b"Cannot change overrides in suite 'noble'" --- It probably means we need to SRU them, as a no-change rebuild, and then, we can promote them in -updates. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry Status in retry package in Ubuntu: Fix Released Status in retry source package in Jammy: In Progress Status in retry source package in Noble: In Progress Status in retry source package in Oracular: Fix Released Bug description: [Availability] The package `retry` is already in Ubuntu universe. The package `retry` build for the architectures it is designed to work on. It currently builds and works for architectures: any Link to package https://launchpad.net/ubuntu/+source/retry [Rationale] This package is required in ubuntu/main as it is a dependency for `autopkgtest`, which is already in main (https://launchpad.net/ubuntu/+source/autopkgtest). Also, this package only consist of a single binary produced from less than 700 lines of quite clear modern C, including error handling and built-in usage (--help). It basically eases creating retry loop in scripts, with non trivial features such as variable delay between retries, and stdout/stderr handling. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/retry/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=retry - Upstream's bug tracker, e.g., GitHub Issues: https://github.com/minfrin/retry/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because there is no test suite in the upstream repository. - The package runs a non-trivial autopkgtest, and is currently passing on all architectures, link to test logs: https://autopkgtest.ubuntu.com/packages/retry - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This packag
