Your message dated Wed, 23 Dec 2020 11:34:25 +0000
with message-id <[email protected]>
and subject line Bug#974381: fixed in node-time-stamp 2.2.0-1
has caused the Debian Bug report #974381,
regarding node-time-stamp: 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.)
--
974381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974381
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: node-time-stamp
X-Debbugs-CC: [email protected]
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-time-stamp is running a
trivial command that does not provide significant test coverage:
- nodejs -e "require('time-stamp');"
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: node-time-stamp
Source-Version: 2.2.0-1
Done: Xavier Guimard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
node-time-stamp, 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.
Xavier Guimard <[email protected]> (supplier of updated node-time-stamp 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: Wed, 23 Dec 2020 12:07:38 +0100
Source: node-time-stamp
Architecture: source
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<[email protected]>
Changed-By: Xavier Guimard <[email protected]>
Closes: 974381
Changes:
node-time-stamp (2.2.0-1) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Use secure URI in debian/watch.
* Bump debhelper from deprecated 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Apply multi-arch hints.
+ node-time-stamp: Add Multi-Arch: foreign.
.
[ Xavier Guimard ]
* Bump debhelper compatibility level to 13
* Declare compliance with policy 4.5.1
* Add "Rules-Requires-Root: no"
* Change section to javascript
* Add debian/gbp.conf
* Update debian/watch to use npm registry
* Use dh-sequence-nodejs auto install (Closes: #974381)
* New upstream version 2.2.0
* Update copyright
Checksums-Sha1:
0e8c5a06b87693d848f6575ddc554b7904e5dee7 2053 node-time-stamp_2.2.0-1.dsc
917e0a66905688790ec7bbbde04046259af83f57 3880 node-time-stamp_2.2.0.orig.tar.gz
187331beb272f6723470861d89a35c7f218dc812 2484
node-time-stamp_2.2.0-1.debian.tar.xz
Checksums-Sha256:
62e35b84cc208f361432cbc08b5a55eb045117675267cf05841bb19b502e8383 2053
node-time-stamp_2.2.0-1.dsc
6805a14f5f942c7c9d17e1d98058405d10573fc627a5aa4203088b44ebf84cf1 3880
node-time-stamp_2.2.0.orig.tar.gz
fedbd58dadabd38c3ed560fbbbc6f5210956a1a44e2b025257bb389734bf9b6c 2484
node-time-stamp_2.2.0-1.debian.tar.xz
Files:
68f3bd6ba31ed0cbf43904ea7fd6c7d1 2053 javascript optional
node-time-stamp_2.2.0-1.dsc
dbaf487cc996d16b438a44b77bbb75d2 3880 javascript optional
node-time-stamp_2.2.0.orig.tar.gz
b18a60aeadd9998ab93e1c28cda7859a 2484 javascript optional
node-time-stamp_2.2.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/jJUwACgkQ9tdMp8mZ
7uklbw/+IaBy7dFjBugYaREdVrJr7eqKESFD+R8kcP0i/vv+IaKHffIj72da6BJd
dRzUOGZNlQOrMzC99ELPP6G0GXd7EqRJPZUQu8i0SrnlPpcNRFH/ATL1n+nyvdu3
U2Rk7zF4qDj3zf0WIAS1JDA5Dk/Ma+Yq7cGvhxhtJRwqbjVSTb70z74jCAv28tDj
Ai6kE5aww+1Zwu48M+wDPiPzbMNP7m6Yd4G0tY/vrdUd9FG8fmVvJZNyXNKBgcpT
ldPpdihdMVEnL7qo/13mH8q8mRaEf/RQkbhbf6KT61JEBN/DpDGb44Ia38P36YcP
hJo0x30NqF2EQsjyQtMI8WvNYXwUu6V8L7m8QFsqS+AjAYoBWM3ZzqYUlWFDXdTc
0lQZORgMqsSRdHuMtsGSj944TCTEoqa+FaS8xXaXx8FlNMgicYXNqwiJyrRR9xJF
q0OTanu5km5quc/B8pok2Vsql61KYhgWF/VNBGQ73trKx41OF5ZQWMbtyfJGyzue
6LOB5viXWnzXJwxC8tLf/aZPuxvDfAtbMauBQfEPPQdrXq2rqVKVVLvoLQiAk79i
ew3XH0NTzihp83j5bAbVfgt7DiTPpYROnw84tyUYpeboBgPZnPg/JRVl8p6nx6cc
aGzF2djiGcjVeTDUkOtbdgBHzNe2bUFBnekuLzY+v4y59glbhzM=
=/Uye
-----END PGP SIGNATURE-----
--- End Message ---
