Your message dated Mon, 24 Mar 2025 16:00:10 +0000
with message-id <[email protected]>
and subject line Bug#974496: fixed in reparser 1.4.3-4
has caused the Debian Bug report #974496,
regarding reparser: 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.)
--
974496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974496
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: reparser
X-Debbugs-CC: [email protected]
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in reparser is running a
trivial command that does not provide significant test coverage:
- $py -c "import reparser; print(reparser)"
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: reparser
Source-Version: 1.4.3-4
Done: Colin Watson <[email protected]>
We believe that the bug you reported is fixed in the latest version of
reparser, 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 reparser 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 Mar 2025 15:13:55 +0000
Source: reparser
Architecture: source
Version: 1.4.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 974496
Changes:
reparser (1.4.3-4) unstable; urgency=medium
.
* Team upload.
* Mark import-only autopkgtest as superficial (closes: #974496).
* Use dh-sequence-python3.
* Use pybuild-plugin-pyproject.
Checksums-Sha1:
ddc71b2408f1ed018458084dbcf52e12dd41a528 2169 reparser_1.4.3-4.dsc
4767e1b9261c17b695106fe944c2951f80d68e1b 2608 reparser_1.4.3-4.debian.tar.xz
Checksums-Sha256:
17e851df70a4cbd3bc01f433df6c3d7850195d110c047485245aaa2a44a49c61 2169
reparser_1.4.3-4.dsc
d2ec024fa98a812d813cdad5e4f690e62e108dfff7a3a934d83c866dc468dc47 2608
reparser_1.4.3-4.debian.tar.xz
Files:
aa7c9629aac9da261dc190ab2f5fc309 2169 python optional reparser_1.4.3-4.dsc
b2d92c62a1f8a8743afebb7470ea710f 2608 python optional
reparser_1.4.3-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmfhdt4ACgkQOTWH2X2G
UAsfsQ/+OYWErZNDE+kLjGXJmnEIWqjI478Hly8F5afgKHEgptSNUi2BEkPw8DYt
4vTwshVzAx3hFI3oOLYcQzPtAiBT2Wktdg3l14iJc/rv1GhAZjtgAjhrh4J0bexO
ymJ2vQ/yUbBdMaEPaomrnIBUfOfjmF5R6JFY3cc0WuWI6yZzZRvLouIiH0Fgzyur
sOSIlmxFYJh8Lp9DbOMjV13uCJYBaEBvSBb859xZy06WcuG7oOskl+wZSEpybwPQ
t3G1yGAf4m9L32JZWCFYQfIvZN7IwgnVT+glJMg8OxShHvebVvkrGOuUrvZdkGSH
DQC6w9yYRvitixj1AHUURnlpmFODiwndoe3hOZToFoShydy+ZclVn2Sps3kx4/qY
LQ4AbivIcstjtlKjAoIVbzQt8aMdxwWyKAfm+Knk0GLBVhSNG4Iy6n7cIj7wZ3le
4AF4S8M7YYRXR1fIEHgfndW4O83fiv+F6MRWDgXm/u61amYRUeNkNaBwLy4kB3Q0
oPVBp2hSNXKum+G+P0C1uchs11qd/AquyCcISmudMQH7KQs3LQa/tCBi4d/evK/P
w7v/il4Rf4ciR0fjqq3/qToQ95uBD2HLmXxN/5kIMaim0TEQYgkPdSZqNpjpoVie
iKfSVXmgzZfb4I1f7CdzUDw+eL+gs6PzX0QtrHn00Pe6ivXVi1w=
=IbLk
-----END PGP SIGNATURE-----
pgp0AOl5siuQO.pgp
Description: PGP signature
--- End Message ---
