Bug#969812: marked as done (cldump: autopkgtest should be marked superficial)
Your message dated Thu, 10 Sep 2020 19:18:34 +0000
with message-id <E1kGS5a-000Ayc-Bb@fasolo.debian.org>
and subject line Bug#969812: fixed in cldump 0.11~dfsg-4
has caused the Debian Bug report #969812,
regarding cldump: autopkgtest should 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 owner@bugs.debian.org
immediately.)
--
969812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969812
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: cldump
Severity: serious
Usertags: superficialtest
X-Debbugs-CC: elbrus@debian.org
Hi,
The test done in the autopkgtest of 'cldump' does not provide
significant test coverage and it should be marked with "Restrictions:
superficial".
Ref: https://people.debian.org/~eriberto/README.package-tests.html
Examples of tests which are not significant includes (its not a
complete list):
1) Executing the binary to check version
Test-Command: foo -v
Test-Command: foo -V
Test-Command: foo --version
2) Executing the binary to check help (foo -h)
Test-Command: foo -h
Test-Command: foo --help
3) checking for files installed with 'ls'.
Test-Command: ls -l /usr/lib/*/foo.so
4) A Python or Perl library runs import foo or require Foo; but does
not attempt to use the library beyond that.
Test-Command: python3 -c "import foo"
Please add "Restrictions: superficial" to 'debian/tests/control' of
'cldump'.
--
Sudip
--- End Message ---
--- Begin Message ---
Source: cldump
Source-Version: 0.11~dfsg-4
Done: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
We believe that the bug you reported is fixed in the latest version of
cldump, 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 969812@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sudip Mukherjee <sudipm.mukherjee@gmail.com> (supplier of updated cldump 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 10 Sep 2020 19:54:56 +0100
Source: cldump
Architecture: source
Version: 0.11~dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Closes: 969812
Changes:
cldump (0.11~dfsg-4) unstable; urgency=medium
.
* QA upload.
* Mark autopkgtest as superficial. (Closes: #969812)
Checksums-Sha1:
677dc1d0b34d4d4b837e53020ce751cb32e9eb32 1705 cldump_0.11~dfsg-4.dsc
6bbe93c1aff1742397bbd5d66f00a45db312da00 2688 cldump_0.11~dfsg-4.debian.tar.xz
a181ca9da29c0bf532c94aa93ba15886ff65f1ab 5685 cldump_0.11~dfsg-4_amd64.buildinfo
Checksums-Sha256:
c255754e8d6be886e47fdd1dd43bd4a980930d41fde519cc5bbddc0e79b8f04b 1705 cldump_0.11~dfsg-4.dsc
66d332a59ae4c9a945b75048421da5710d9d6e46c0a6311f2cb99e977d7599ea 2688 cldump_0.11~dfsg-4.debian.tar.xz
a4981d0c0efd20f43e4af1dc192d36c130e682224b0f608a4149b2749482526a 5685 cldump_0.11~dfsg-4_amd64.buildinfo
Files:
ce1dd85457eede591ac5443c5c069c8d 1705 misc optional cldump_0.11~dfsg-4.dsc
1dd7f54b8cfb5eb39e3731b43fff55f1 2688 misc optional cldump_0.11~dfsg-4.debian.tar.xz
02b283d8484729b10d3c598bb5fd67fc 5685 misc optional cldump_0.11~dfsg-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl9ad6EACgkQR5mjUUbR
KzW6Ig//dkYrNr1YZ0rS+bZRNG7Q2FRFY9uf/31FUhjZT6K6zqXVfYP7OZdHYbWV
2oBr6JwdLgbeBLEjTKctNGM9Ld+i4OZ0oNzkxjDR33vIYakS9HCCqeKhhH65WoAa
STy5kwroy7xc2xA6XEfGZzYSa+H1F+8TLWtcVPknY06L4lPPbCkrS7fEUFZRM0+Y
2brCsMF0MHXoiO55dGHX+1vADzXRg4kTB8sOU/HAtpHQPGPjgJi1lsWOljKtP0uZ
JIsqdC2/bHE6O4ImJ8oZlvrqn9p582ub52wSW+VkR5ZURX210fIl8EwY/NV3NYLH
gXROHsy3UIHZ1mz172cCm+NRBoqeoxqPLnUv4SPquTgM4p1FqJbJonq3V2DcHJ2q
oSKuP6ssOPEGfIQS6fFK5OUVRNeUlg7PP9iHwxRHF4a0C1zXn1YHmB8n3XLW8qOH
ZIAHlrJxKcm7ZHHfF+jdvlVLwzoLieLum0qINeYRiNBBG2D50iRe9XhN9IpVVecQ
QXcMMaEM8KDcbWQ5csL3mJOsIBpsyM935HgjdQSS5WFiRTUauTBDsARJYS/TIqHt
vcE/hZSMsK5N4UzZRhoctVb00RCIPGm5GeZq0xGtCaSqPr1h0tPoiBz7zXfXMxs+
rC5Tp89WX52Akl8Vog451bKUCaESiMMcLB2WnDb31Z2Idp6LM5k=
=SEF5
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: