Offrez-vous une expérience de vie différente à Bouskoura

2020-09-30 Thread FAL GREEN
Afin de voir votre message, cliquez sur le lien: 
http://link.news-sarouty.ma/v/443/de86ac2aa9610f17dc44b290187174a20347b033abdf7d3b

Bug#971498: python-mplexporter: autopkgtest must be marked superficial

2020-09-30 Thread Sudip Mukherjee
Source: python-mplexporter
Severity: important
Usertags: superficialtest
X-Debbugs-CC: elb...@debian.org

Dear Maintainer,

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

- testcommand: import mplexporter

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



lxctl is marked for autoremoval from testing

2020-09-30 Thread Debian testing autoremoval watch
lxctl 0.3.1+debian-4 is marked for autoremoval from testing on 2020-10-16

It (build-)depends on packages with these RC bugs:
966278: lxc: fails to migrate to testing for too long: unresolved RC bug and 
autopkgtest regression
 https://bugs.debian.org/966278



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl



transfermii is marked for autoremoval from testing

2020-09-30 Thread Debian testing autoremoval watch
transfermii 1:0.6.1-4 is marked for autoremoval from testing on 2020-11-06

It (build-)depends on packages with these RC bugs:
970763: wminput: wminput immedinately exits with Segmentation Fault on use
 https://bugs.debian.org/970763



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl