[MIR] retry

[Skia]

[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
- 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