Your message dated Wed, 06 Feb 2019 15:35:03 +0000 with message-id <[email protected]> and subject line Bug#920938: fixed in pcapfix 1.1.4-2 has caused the Debian Bug report #920938, regarding autopkgtests fail with: Cannot open input file: No such file or directory 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.) -- 920938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920938 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:pcapfix Version: 1.1.4-1 Severity: normal Hi, Removing autopkgtest-satdep (0) ... autopkgtest [15:14:06]: test command1: pcapfix debian/test/test_2018.pcap autopkgtest [15:14:06]: test command1: [----------------------- [-] Cannot open input file: No such file or directory pcapfix 1.1.4 (c) 2012-2019 Robert Krause [*] Reading from file: debian/test/test_2018.pcap autopkgtest [15:14:07]: ERROR: testbed failure: testbed auxverb failed with exit code 254 The path to the .pcap file is wrong since 1.1.4-1. In addition, the last line shows that the exit status of the test command is making autopkgtest think that *it* failed rather than the test command. It only supports exit 0-125 - is there any chance you could chop off any larger exit codes please? In a script, something like (untested) #!/bin/sh pcapfix ...; RC=$? if [ "${RC}" -gt 125 ]; then RC=125 fi exit ${RC} (The closest bit of documentation I can find for this is in [0]: program's exit status will be that of the testbed command if the latter exits with a value from 0..125. ... If program fails it will exit 254 or 255 Where "program" is not the test program: it is an autopkgtest-internal program to execute a given command inside the testbed.) Thanks! -- Iain Lane [ [email protected] ] Debian Developer [ [email protected] ] Ubuntu Developer [ [email protected] ] [0] https://salsa.debian.org/ci-team/autopkgtest/blob/master/doc/README.virtualisation-server.rst
--- End Message ---
--- Begin Message ---Source: pcapfix Source-Version: 1.1.4-2 We believe that the bug you reported is fixed in the latest version of pcapfix, 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. Joao Eriberto Mota Filho <[email protected]> (supplier of updated pcapfix 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, 06 Feb 2019 12:50:48 -0200 Source: pcapfix Binary: pcapfix pcapfix-dbgsym Architecture: source amd64 Version: 1.1.4-2 Distribution: unstable Urgency: medium Maintainer: Joao Eriberto Mota Filho <[email protected]> Changed-By: Joao Eriberto Mota Filho <[email protected]> Description: pcapfix - repairs broken pcap and pcapng files Closes: 920938 Changes: pcapfix (1.1.4-2) unstable; urgency=medium . * debian/tests/control: fixed to point to debian/examples.d/ instead of debian/test/. (Closes: #920938) Checksums-Sha1: 105f47099333df2d5cb6977076194923427b6727 2077 pcapfix_1.1.4-2.dsc 6e10cfb8a6ae41bc98ae60f5310e12d4c3442fe4 15376 pcapfix_1.1.4-2.debian.tar.xz d1c61a9fe75c807ee18b4e2f6da1529591ab8e17 51732 pcapfix-dbgsym_1.1.4-2_amd64.deb 86853c993c9a20c44e7cb7d0348c30e662367f61 5422 pcapfix_1.1.4-2_amd64.buildinfo 5138b82e9540ff7fbf084deeaa31396bc75ab897 38928 pcapfix_1.1.4-2_amd64.deb Checksums-Sha256: 68bff1010256bfe347f722ab25a36993f3c25f7103754d56d4afdc120c0912a8 2077 pcapfix_1.1.4-2.dsc edd3bae513dad8dbb2d1250cebfcd3fb65cc59239fc13b809e16881b7370c4b7 15376 pcapfix_1.1.4-2.debian.tar.xz 53792a930f9e6653094cea6d002b103b8c0aeb99ea0860c0aec70879b846e81a 51732 pcapfix-dbgsym_1.1.4-2_amd64.deb dab9cfb224c6ee6ba8607ef7e6aa8b57c7986274e498ac086bfa5ca0d3c1b1b8 5422 pcapfix_1.1.4-2_amd64.buildinfo 04b372c3dbb71b226702189cf34d1de4a838c5e6f00f829a829b2cf944715bfa 38928 pcapfix_1.1.4-2_amd64.deb Files: d4e758b5ddfc5009780a542eab22006c 2077 net optional pcapfix_1.1.4-2.dsc 7a233ef8dd95669f324f09b0904c5a36 15376 net optional pcapfix_1.1.4-2.debian.tar.xz f2c1f3f6b8e61161c83c70da3ba4123f 51732 debug optional pcapfix-dbgsym_1.1.4-2_amd64.deb a6a953862aeb9b7b16ffcf215e1b83ef 5422 net optional pcapfix_1.1.4-2_amd64.buildinfo 857ec08cd9a5d494cf839d08ee67b644 38928 net optional pcapfix_1.1.4-2_amd64.deb -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlxa+hMACgkQ3mO5xwTr 6e+o0RAAkIX6CIsCV/r1cUM3MRP7pf9yyKCKiQM8GoQHXWQgJr+90+cht0+D/mDC 4VT9lKPYVqOdHOs4j7kPRzg7ukBZvAq/S1QI6BFSvw4t2WUazqzRMCIb9pj+LUrR tgFhH3OGZuoRsdotgnqbEQwKp0a8BikKF1SMptXMW+yyfMcXNDVkI0pNLWs2RrO1 nFl51BFA29f7NnZa/AR08L7ZJIrm+PtFipl+OcbKCFZA4CGncfhkOptkq2wzAs/N hEGy1wM/a1vkg7jVDRulwMFmN8P5nX7IC+7SDDTr9cGIkgkSB+aC1VfbXsE1OgLX 46JdAhBQtCNihf8GUXKdEk5XWH0+Rk5eFiULqt+yX9eif9kvcw1OcUyKk/COTwPf NNCI5ZyaMOKnZEDHASmJ/afQ7ENYEuC6bHiGZlrbSCv6JFfN47+2cEDJAgjZKnrU 7T+emE67LzqnBd4UhpknBdrNijOfg2vPiK4/l0sK5fiT2pMxDDePn/I1Rk691MeU dgFMUXNuR8CDf7dxFkSRhOT3D+K8PFEKl4YKLFfvKNPk+4V6vjjopr+5pYIWLWq7 rUWhy8IbG9MJBGbPVrlKc8Ne+PwidN725wj9FX9pGuwb4UlssuUNWSP7GXyQSZRD ZUIPjWpnQI1m86ZWh4HFOCxTYQpBHEhm7rMnWARfL7JcnLrHkHQ= =5dFk -----END PGP SIGNATURE-----
--- End Message ---
