Your message dated Mon, 24 Feb 2025 02:39:02 +0000
with message-id <[email protected]>
and subject line Bug#974455: fixed in django-memoize 2.2.0+dfsg-6
has caused the Debian Bug report #974455,
regarding django-memoize: autopkgtest must be marked superficial
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
974455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974455
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: django-memoize
X-Debbugs-CC: [email protected]
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in django-memoize is running a
trivial command that does not provide significant test coverage:
- python3 -c "import memoize; print(memoize)"
Executing that command is considered to be a trivial test, which
does not provide significant coverage for a package as a whole.
But these tests are a useful way to detect regressions in dependencies
and prevent them from breaking your package.
However, it is important that we are realistic about the level of
test coverage provided by these commands: most regressions cannot be
detected in this way. So it is not appropriate for packages with only
superficial tests to have the reduced migration time to migrate from
unstable to testing as that means less opportunity for testing by users
compared to the package with no tests.
To support this, the keyword "Restrictions: superficial" has been
defined [1]. Packages where all tests are marked with this keyword are not
considered for the reduced migration age from unstable to testing, and
will not be allowed to migrate automatically in later stages of the
freeze [2].
Its always better to have more extensive testing than having
superficial testing, which again is better than having no test.
Please consider i) Adding a non-trivial test, and/or ii) Mark the
trivial test with "Restrictions: superficial", similar to
[3] or [4].
The Release Team has listed this issue in the list of Release Critical
Issues for bullseye [5] and has mentioned that the test must be marked
superficial if it is not testing one of its own installed binary
packages in some way. As a result, the severity of this bug report might
be increased to serious in future.
[1]
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions
[2] https://release.debian.org/bullseye/freeze_policy.html
[3]
https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468
[4]
https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3
[5] https://release.debian.org/bullseye/rc_policy.txt
--
Regards
Sudip
--- End Message ---
--- Begin Message ---
Source: django-memoize
Source-Version: 2.2.0+dfsg-6
Done: Colin Watson <[email protected]>
We believe that the bug you reported is fixed in the latest version of
django-memoize, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated django-memoize package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 24 Feb 2025 02:03:12 +0000
Source: django-memoize
Architecture: source
Version: 2.2.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 974455
Changes:
django-memoize (2.2.0+dfsg-6) unstable; urgency=medium
.
* Team upload.
* Use dh-sequence-sphinxdoc.
* Use pybuild-plugin-pyproject.
* Simplify a debhelper override.
* Run tests on all supported Python versions.
* Switch to autopkgtest-pkg-pybuild (closes: #974455).
Checksums-Sha1:
24a4c85391fd5d25ec32bc88a7a2e553f7295a13 2417 django-memoize_2.2.0+dfsg-6.dsc
f79af1875c7e1987b413b1351c30cfbc3ce139e6 5020
django-memoize_2.2.0+dfsg-6.debian.tar.xz
Checksums-Sha256:
f075f0009c49779bfb351a1c8cdcad94e450785d2bcb6c24fdcec01d219969d0 2417
django-memoize_2.2.0+dfsg-6.dsc
8537fa740ec58bcc0ae30ddb363b88faed8cfac836817de1238707a036cc2d5e 5020
django-memoize_2.2.0+dfsg-6.debian.tar.xz
Files:
b5564bb0c99d0b374dc91ded8e07e2d5 2417 python optional
django-memoize_2.2.0+dfsg-6.dsc
3ef1c717eedd47a64d8da19151cad611 5020 python optional
django-memoize_2.2.0+dfsg-6.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAme706UACgkQOTWH2X2G
UAvFZhAAgYgMpNZAAfKV0b1LTYhxj84NAqP4ctIDs6Gr67h98xXv/G0lC+Y+tykb
NCZmFhlvMaM26QIC/Tuy3GPk0K6LiAtwM8a60wY80h1Oi8HIRCtQDXUd5MOYOLSN
bNsohNBrgW2biH4JeqcmF2mQZmnaSZgQSKjZowtp/G6cZZ5jGV7wYBw3n7yZ39Ze
ypZZA3XwpflSkqMWwVSEYWX4caMgLWLX9F3F2oHg4x4/wN0rbNaF3Xpxgluh1nh4
HlYFH9Xd1umBz5B4WEXPwfRcYYLxenmsdN9UxZzVKyt+u0B3IZ4vyidud/wWKF2f
gpwGWe1V73D1X6UtjIfqbW1vsH6zpq+I97KVDqyxHFdENR+GxM2NEta+qEtDDcas
MNLHekkxB5LPPFcUXJdA+BOSxleMkn9DdLu0OJPw6C7KBOKJQlVq4skSTCrXWRnl
G3nnI5zSJnKHv07HEtXEitPKmhYRfP37rtjady03YopKXXrjIrPQRMnpPYVkUgg4
db02ITkGCkCNx0kOZRGFP9BUWWxEyAfqIw5qZNnh1O/B1L0+9afGe7zb4etdqOcg
SZp1j9nYPy44Bc19C5M5cJahgOkivqNwzfHbkKWpBFFCd3G1DxX0v05KmZBo2g3W
8gbzXHCrJVEm5p2xgL1aZhiLpTiSN/Tn0PHFan10FoqJsE/r1R0=
=tP5M
-----END PGP SIGNATURE-----
pgprTZrsNi1q9.pgp
Description: PGP signature
--- End Message ---
