Your message dated Thu, 26 Feb 2026 10:14:07 +0000
with message-id <[email protected]>
and subject line Bug#970970: fixed in sipvicious 0.3.3-2.1
has caused the Debian Bug report #970970,
regarding sipvicious: 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.)


-- 
970970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970970
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sipvicious
Severity: important
Usertags: superficialtest
X-Debbugs-CC: [email protected]

Dear Maintainer,

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

        -Test-Command: svmap -h 
        -Test-Command: svwar -h 
        -Test-Command: svcrack -h 
        -Test-Command: svcrash -h 
        -Test-Command: svreport -h

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: sipvicious
Source-Version: 0.3.3-2.1
Done: Adrian Bunk <[email protected]>

We believe that the bug you reported is fixed in the latest version of
sipvicious, 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.
Adrian Bunk <[email protected]> (supplier of updated sipvicious 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: Thu, 12 Feb 2026 19:30:17 +0200
Source: sipvicious
Architecture: source
Version: 0.3.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Marcio de Souza Oliveira <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 970970 1083772
Changes:
 sipvicious (0.3.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove unnecessary dependency on python3-pkg-resources.
     (Closes: #1083772)
   * Mark the autopkgtests as superficial. (Closes: #970970)
Checksums-Sha1:
 2e08c8349197c25f3e216a106e60daee7d9b5b2c 1960 sipvicious_0.3.3-2.1.dsc
 b3c762116e060a7972bef72f1dad2f2d7a887c2d 4188 
sipvicious_0.3.3-2.1.debian.tar.xz
Checksums-Sha256:
 fa54d3adc1f9b86fb904c8f2593a99887bc54ae57ea2185d4593709a0ae83923 1960 
sipvicious_0.3.3-2.1.dsc
 a68719b203a5238ef24bc4453b5c8d43b8167adf7980f2bc86f425d6eb25c01b 4188 
sipvicious_0.3.3-2.1.debian.tar.xz
Files:
 beeda7b42cdb0d4af05755588b61639b 1960 misc optional sipvicious_0.3.3-2.1.dsc
 b77b5b897e3818923264f51b464cc450 4188 misc optional 
sipvicious_0.3.3-2.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmmODukACgkQiNJCh6LY
mLE0MhAAghRdMMaVG7XEmaE5GHxLmAXR7fmf/SBCvsR9s+MDh3iDJJTPW2DNRMiF
dW+nugWM6XcZxVBdcWejc0M14ZJM5WcWj4rHEJJ+R0dxlmNnM4YUuhoVeSdtnTxE
vX9hFXAJ66lF7WDWRTgWZNBU5c5mSufs03nM9Cil1gu0NFAgUKG/vV4C7/nkLjB1
WrT4HrJ/CK2Qy7tNIe7ojZHgiGfrkyQC0HCnFjO/W4lEt4/8vrC07n8Z2ywtQmI/
rAT/Bgsn5ymYTpIWUVPq4xsgDqnbeyIzEt6CfblV1OsAQtPBoCoKff7A3zZnsyle
JsV6M+avc6ULtGEtUNDhex5WFFt3jUEEAGxV8EY1hytgM7kCSTk7HZwtTEVPCmRp
bFZi7haVeI+2HkpS1movhFOi36YNu6bMdZ0ood0EEMI3WQPMj3qIVCtC/KfB2hB+
vKt7h0uHqHQC04Ez5yGf2CV/dB4YXQFPFATDrpMh7QtMDHI+NVIAUCatwsvc5xZN
tIQbihFLbguQLxyaYkslemHrneEkTwYq0IGgUiaVVDwTylBjueobGjD0bfUuft0Z
tpHpax+aJ9lSXiv1Nu2vpn9Xx5Z62YMrIUBIC4jHQpaGug00FdtbCJTNa09SNsIc
voO6OMCvGwMCoki+fl4qmhTCKl2qA05IupqOicth5skDK+EtXDw=
=y3Lf
-----END PGP SIGNATURE-----

Attachment: pgpPSZ5X3gzdO.pgp
Description: PGP signature


--- End Message ---

Reply via email to