Première résidence sportive au Maroc
Afin de voir votre message, cliquez sur le lien: http://link.news-sarouty.ma/v/443/de86ac2aa9610f175977ef75a40843590347b033abdf7d3b
Bug#970915: isakmpd: outdated upstream source unacceptable for distribution
Source: isakmpd Version: 20041012-10 Severity: grave Our isakmpd sources are by now 16 years old. The sources in OpenBSD have in the meantime seen a number of improvements and security fixes, plus protocol fixes. Shipping such an old version with known security problems is a disgrace to our users. If we do not want to properly maintain this, lets stop shipping it at all - we have better IPsec VPN options to choose from. Chris
Bug#970916: vzctl: unusable without kernel support
Source: vzctl Version: 4.9.4-6 Severity: serious vzctl needs kernel support, specifically the "vz" patches. Debian hasn't shipped those in a long time. By now it appears upstream development has moved back behind more closed doors, and it's unlikely we'll see anything for bullseye. Also, IIRC, the RHEL8-based kernel trees would need newer tooling, not "vzctl". (Which also doesn't seem to be public.) Continuing shipping vzctl will not help anyone. I'll also file bugs against the related vzquota, vzstats programs. Chris
Bug#970917: vzquota: unusable without kernel support
Source: vzquota Version: 3.1-4 Severity: serious vzquota needs kernel support, specifically the "vz" patches. Debian hasn't shipped those in a long time. By now it appears upstream development has moved back behind more closed doors, and it's unlikely we'll see anything for bullseye. Continuing shipping vzquota will not help anyone. See #970916 for the vzctl bug. Chris
Processing of ticker_1.12_source.changes
ticker_1.12_source.changes uploaded successfully to localhost along with the files: ticker_1.12.dsc ticker_1.12.tar.xz ticker_1.12_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#928196: marked as done (ticker FTCBFS: fails configuring during clean)
Your message dated Fri, 25 Sep 2020 21:21:08 + with message-id and subject line Bug#928196: fixed in ticker 1.12 has caused the Debian Bug report #928196, regarding ticker FTCBFS: fails configuring during clean 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.) -- 928196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ticker Version: 1.11 Tags: patch User: helm...@debian.org Usertags: rebootstrap ticker fails to cross build from source, because it fails configuring for the build architecture. ./configure is run by make clean during dh_auto_clean. That's bad. Once that is fixed, the Makefile fails to use the cross compiler detected by the real ./configure invocation. The attached patch fixes both and makes ticker cross buildable. Please consider applying it. Helmut diff --minimal -Nru ticker-1.11/Makefile ticker-1.12/Makefile --- ticker-1.11/Makefile2015-08-28 04:35:08.0 +0200 +++ ticker-1.12/Makefile2019-04-29 16:24:17.0 +0200 @@ -8,7 +8,7 @@ all: ticker ticker: ticker.c - gcc ticker.c -o ticker $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) $(LIBS) + $(CC) ticker.c -o ticker $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) $(LIBS) demo: ticker PATH=.:$$PATH ./ticker "This is a test..." diff --minimal -Nru ticker-1.11/debian/changelog ticker-1.12/debian/changelog --- ticker-1.11/debian/changelog2015-08-30 23:16:07.0 +0200 +++ ticker-1.12/debian/changelog2019-04-29 16:24:17.0 +0200 @@ -1,3 +1,11 @@ +ticker (1.12) UNRELEASED; urgency=medium + + * Fix FTCBFS: (Closes: #-1) ++ Don't ./configure during make clean. ++ Propagate compiler from ./configure to make. + + -- Helmut Grohne Mon, 29 Apr 2019 16:24:17 +0200 + ticker (1.11) unstable; urgency=medium * QA upload. diff --minimal -Nru ticker-1.11/debian/rules ticker-1.12/debian/rules --- ticker-1.11/debian/rules2015-08-28 04:35:54.0 +0200 +++ ticker-1.12/debian/rules2019-04-29 16:24:14.0 +0200 @@ -5,3 +5,8 @@ %: dh $@ --with autoreconf + +override_dh_auto_clean: + # avoid running ./configure during make clean + touch makeinfo config.status + dh_auto_clean --- End Message --- --- Begin Message --- Source: ticker Source-Version: 1.12 Done: Leandro Cunha We believe that the bug you reported is fixed in the latest version of ticker, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Leandro Cunha (supplier of updated ticker 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: Tue, 22 Sep 2020 16:33:03 -0300 Source: ticker Architecture: source Version: 1.12 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Leandro Cunha Closes: 928196 Changes: ticker (1.12) unstable; urgency=medium . * QA upload. * debian/rules: - Avoid running configure during make clean. (Closes: #928196) * debian/copyright: - Add Upstream-Name and Upstream-Contact. - Update link format with HTTPS reported by Lintian. - Add myself. * debian/control: - Debhelper-compat level to 13. - Bumped Standards-Version to 4.5.0. - Add Vcs-Browser and Vcs-Git in Salsa. - Remove build-dep dh-autoreconf reported by Lintian. * Fixed spelling error in a manual page reported by Lintian. * Rename archives README with .md and GPL for LICENSE.md. * debian/tests: - Add control file for autopkgtest. * Add debian/salsa-ci.yml file. * Fix exit non-zero in help command reported by autopkgtest. Checksums-Sha1: 52819465961bce1ddc561dc3d7cc57766bb754c8 1581 ticker_1.12.dsc fbaf88dda2916751717e277cd883122abebd874b 46968 ticker_1.12.tar.xz b7d24fed5cbe1d136df59cdc7d0f045b02a41922 5246 ticker_1.12_source.buildinfo Checksums-Sha256: 0515c596a602550d4e6e22b9abcc89202361641c676102e49e8d103513becdb1 1581 ticker_1.12.dsc 036d65a1a4019c02b82e3502ec18c07b0cbe6ab2542d0213618560f5377960c4 46968 ticker_1.12.tar.xz 8d86d194184dc56a857d46542fa7be49e78753740ddb7abf5d16514a
ticker_1.12_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Sep 2020 16:33:03 -0300 Source: ticker Architecture: source Version: 1.12 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Leandro Cunha Closes: 928196 Changes: ticker (1.12) unstable; urgency=medium . * QA upload. * debian/rules: - Avoid running configure during make clean. (Closes: #928196) * debian/copyright: - Add Upstream-Name and Upstream-Contact. - Update link format with HTTPS reported by Lintian. - Add myself. * debian/control: - Debhelper-compat level to 13. - Bumped Standards-Version to 4.5.0. - Add Vcs-Browser and Vcs-Git in Salsa. - Remove build-dep dh-autoreconf reported by Lintian. * Fixed spelling error in a manual page reported by Lintian. * Rename archives README with .md and GPL for LICENSE.md. * debian/tests: - Add control file for autopkgtest. * Add debian/salsa-ci.yml file. * Fix exit non-zero in help command reported by autopkgtest. Checksums-Sha1: 52819465961bce1ddc561dc3d7cc57766bb754c8 1581 ticker_1.12.dsc fbaf88dda2916751717e277cd883122abebd874b 46968 ticker_1.12.tar.xz b7d24fed5cbe1d136df59cdc7d0f045b02a41922 5246 ticker_1.12_source.buildinfo Checksums-Sha256: 0515c596a602550d4e6e22b9abcc89202361641c676102e49e8d103513becdb1 1581 ticker_1.12.dsc 036d65a1a4019c02b82e3502ec18c07b0cbe6ab2542d0213618560f5377960c4 46968 ticker_1.12.tar.xz 8d86d194184dc56a857d46542fa7be49e78753740ddb7abf5d16514a6ba019c4 5246 ticker_1.12_source.buildinfo Files: 4f696ca38a4e7bdc423e0af5769f1cc2 1581 utils optional ticker_1.12.dsc 8710fce53b13c4b534230712df51128d 46968 utils optional ticker_1.12.tar.xz 3a8087331995712de75db5908ec351a9 5246 utils optional ticker_1.12_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9uVcQACgkQweDZLphv fH5WGA/7BxXpRTXhmbf31sJfb2ab/kAGcpeGweIgGXAFbBw7QO6xpP1E5GRW+OVd LY6V6Qyn15PhlFj3GOjWofFtt1hTPeHept9ZrCojR38n7Q8G95XMMGBufXiciEye shNH1E0VxdyRisDoDCZr/M/Jm+jWFVhlJ2n8AGo5t092iepP+q93KDjO2YnhyHi0 GNs8QPpyxUBzzyQDaswg+3PG5rtMhe6OqvHkL55Lan6E9g/2XXKezC7CtsJ9qacn fOWg1BJb0lDTYTXnQ6E6Ho8Bvn9YtHZ2+n4Jpvt26r+51ohjmZ8j9D7RH6UUArIZ Vvc+yHRj+S5im2HnUbwYZJbEuXoJwdesas9A3erNOlSMnXlrnJHT5HcEKTzKaWhu MY85ta+MJwtAJ/g1rf5OPVUCIKeJ7XEYVE9Q63p+wy4cwanVNszfyP8Gs2IO4F5l N6fTVu9jv8q7G1d/IJNU3LDpqxb9lpUQG3/INUvFhH8Ga+wZ1sdm+xinl9ntrO46 d7dCoapc0lk/Q1l9TcxXjI9SdWsOPjbSt8UkyUkL/WgSZtQ62hwS5iGaqaV7Y2EH Zutb/JKAIO/lr/T7KYdp30dYqyMB8mmyvvMEKHs1AgnR5IlxcvoL3ghrqzpuKsSZ 69OgDiFrbv06Lzsvpt6Dok09m/IxXxDPa5MXbv9pnRq0EIDwl1U= =Dt8W -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#970946: apngasm: autopkgtest must be marked superficial
Source: apngasm Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in apngasm is running a trivial command that does not provide significant test coverage: -Test-Command: apngasm | grep APNG 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
Bug#970945: acorn-fdisk: autopkgtest must be marked superficial
Source: acorn-fdisk Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in acorn-fdisk is running a trivial command that does not provide significant test coverage: -Test-Command: acorn-fdisk --help | grep Usage -Test-Command: acorn-fdisk --version | grep arm-fdisk 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
Bug#970947: bmf: autopkgtest must be marked superficial
Source: bmf Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in bmf is running a trivial command that does not provide significant test coverage: -Test-Command: bmf -V 2>&1 | grep version -Test-Command: bmf -h 2>&1 | grep Usage 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
Bug#970948: copyright-update: autopkgtest must be marked superficial
Source: copyright-update Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in copyright-update is running a trivial command that does not provide significant test coverage: -Test-Command: copyright-update --help 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
Bug#970955: herisvm: autopkgtest must be marked superficial
Source: herisvm Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in herisvm is running a trivial command that does not provide significant test coverage: -Test-Command: heri-eval -h 2>&1 | grep usage -Test-Command: heri-stat -h -Test-Command: heri-split -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
Bug#970962: procinfo: autopkgtest must be marked superficial
Source: procinfo Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in procinfo is running a trivial command that does not provide significant test coverage: -Test-Command: procinfo -h -Test-Command: procinfo -v 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
Bug#970957: mmorph: autopkgtest must be marked superficial
Source: mmorph Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in mmorph is running a trivial command that does not provide significant test coverage: -Test-Command: mmorph -h -Test-Command: mmorph -v 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
Bug#970956: lockout: autopkgtest must be marked superficial
Source: lockout Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in lockout is running a trivial command that does not provide significant test coverage: -Test-Command: lockout | grep -i version 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
Bug#970975: vlock: autopkgtest must be marked superficial
Source: vlock Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in vlock is running a trivial command that does not provide significant test coverage: -Test-Command: vlock -h -Test-Command: vlock -v 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
Bug#970974: trueprint: autopkgtest must be marked superficial
Source: trueprint Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in trueprint is running a trivial command that does not provide significant test coverage: -Test-Command: trueprint -H -Test-Command: trueprint -V 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
Bug#970968: rdist: autopkgtest must be marked superficial
Source: rdist Severity: important Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Dear Maintainer, It has been noticed that the autopkgtest in rdist is running a trivial command that does not provide significant test coverage: -Test-Command: rdist -V 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
