© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
[sts-sponsors]
Debian uses autopkgtest for 'version' w/ restriction superficial as follows:
Tests: version
Restrictions: superficial
https:/
superficial
The test does not provide significant test coverage, so if it passes, that does not necessarily mean that the package under test is actually functional. If a superficial test fails, it will be treated like any other failing test, but if it succeeds, this is only a weak indication of success. Continuous integration systems should treat a package where all non-superficial tests are skipped as equivalent to a package where all tests are skipped.
Additionally, since that ".tarball-version" only focus on upstream version "3.3.16". The version won't change unless ones bump the version (which won't happen in stable release) unless under serious exception. So this value is unlikely to be removed or changes any time soon in Focal.
Usually, adding autopkgtest inside an SRU is not a desired change.
For the above reasons, I think it is safe to skip the autopkgtest and only focus on the version fix.