Your message dated Sat, 30 Oct 2021 10:03:33 +0000
with message-id <e1mgld3-000chw...@fasolo.debian.org>
and subject line Bug#970964: fixed in pymupdf 1.19.1+ds1-1
has caused the Debian Bug report #970964,
regarding pymupdf: 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 ow...@bugs.debian.org
immediately.)


-- 
970964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymupdf
Severity: important
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Dear Maintainer,

It has been noticed that the autopkgtest in pymupdf is running a
trivial command that does not provide significant test coverage:

        -Test-Command: env --chdir=/ python3 -c "import fitz"

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: pymupdf
Source-Version: 1.19.1+ds1-1
Done: Bastian Germann <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pymupdf, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <b...@debian.org> (supplier of updated pymupdf 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 30 Oct 2021 10:37:35 +0200
Source: pymupdf
Architecture: source
Version: 1.19.1+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 970964
Changes:
 pymupdf (1.19.1+ds1-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
     contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
     layout.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Bastian Germann ]
   * autopkgtest: Mark superficial (Closes: #970964)
   * New upstream version 1.19.1+ds1
   * d/copyright: license change to AGPL
   * Rebase patches
Checksums-Sha1:
 d860c408e33959f77c160eb4c777f798d3c35615 2017 pymupdf_1.19.1+ds1-1.dsc
 59ab0d75ffe3e65b3ea1ece716aaefcb53b636ef 6099060 pymupdf_1.19.1+ds1.orig.tar.xz
 ba524a23abb9dfd962222dc5d94e07ca1854317e 16112 
pymupdf_1.19.1+ds1-1.debian.tar.xz
 3d046d5658d4658010101b1519a8b51c1a615303 7578 
pymupdf_1.19.1+ds1-1_source.buildinfo
Checksums-Sha256:
 c18b618da7957b3f71df6d261ebd472eda64676765cb8333dd9a0854f04f0b9c 2017 
pymupdf_1.19.1+ds1-1.dsc
 2abea008424e74d3945ec77648f7f05a7224620391a9d1c09ba33a6cad85a10d 6099060 
pymupdf_1.19.1+ds1.orig.tar.xz
 05d28ca6d5bb3aa66fb3cdb6036c3ca403c872e0676f05304a037cb78658c147 16112 
pymupdf_1.19.1+ds1-1.debian.tar.xz
 12ef79bdcf361b41c9414640c4bb7910897c100a43df730656a78a5ce580ea34 7578 
pymupdf_1.19.1+ds1-1_source.buildinfo
Files:
 9df2081f38b3805e474a5aa341f82bb8 2017 python optional pymupdf_1.19.1+ds1-1.dsc
 05fb3a8a6257d4da14cb2b8fc3573c83 6099060 python optional 
pymupdf_1.19.1+ds1.orig.tar.xz
 91ce562f85d5df7fb544ab9ad53c00a5 16112 python optional 
pymupdf_1.19.1+ds1-1.debian.tar.xz
 4b984a0656e00f16bf42e5cb1d3dcfdd 7578 python optional 
pymupdf_1.19.1+ds1-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmF9EvMACgkQH1x6i0VW
QxRFBAv5AYP2/sjj/kY63x2loKOcy8HPL8ewoysI5QXWe8NxhX+3/zwJmlTu/fFe
rqqVf6JxvRnkITGsAGmlHA6bxN7DFuRMvcyXOsA4IYSOfTM6Tacy8Su0m3ZWAXYT
gi+ddBCaHncMZQ6YIgbaq39so2mMZDjcWwO2Geo5RjQ3Wj3F78BQDEVnoDZrWnV1
+9D/1sKbxD8DcXfUsLuDh4Y5zKB2YMRbwJqIbGTsJ5jqh1Q4YXlLcaJXEwVc44Ef
xyhxS7chFzGne4rG9S7+33kPZYqsGaFmg1Arh+LrPhvb6LJnwUu/yMZfuF9tZMwr
2Y0uy3URUSZ/q/Ea2/y0r/wQwFlm7Fyjwx4X2fgwtYJafV0/C9peqVU1fcGFzECQ
ncjaoXMn6fOHyDVgr+VBNlZ2YEnhKllQGARIEYtDBHuqc2m8jsuMplDGvP5oNZJ1
Id0tlqXcgh2cAPx3uVSleSC6S6hU8OG8qz8ReJD4WmhpBnxRW2W3oDRsefub74hf
OOJJNoL/
=9Rhl
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

Reply via email to