Hi, as announced at DebConf9 I'll now (slowly) start threads about different bug categories detected by piuparts, with the aim to agree on mass filing bugs with the correct severity. Having a piuparts clean archive is again a release goal for squeeze, currently http://piuparts.debian.org/squeeze/ shows 16198 successfully tested packages, 391 failures and 7800 packages cannot be tested for various reasons: depends which failed the piuparts tests, circular depends so piuparts cannot determine whether the depends have been tested successfully and a bug in piuparts master, preventing some packages to be tested, which could. For today I picked a simple category: packages which have processes running inside the chroot at the end of the piuparts run. This is probably due to directly calling /etc/rc.d/ scripts in packages maintainer scripts, which is a violation of policy 9.3.3.2 and must be replaced by using invoke-rc.d - see http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3. This is mandatory since policy version 3.7.0. http://piuparts.debian.org/squeeze/processes_running_error.html and http://piuparts.debian.org/squeeze/processes_running_error.html lists those packages. Only three packages have been detected which are affected, so I filed bugs with severity serious right away, as IMO this is a pretty clear case of violating a mandatory policy requierement, where the violation seriously disrupts user expectations. Also, filing three bugs is not exactly mass bug filing :-) Other bug categories detected by piuparts will IMO be more worth discussing ;-) regards, Holger P.S.: I've bcc:ed this mail to -qa@ and -release@ and do _not_ plan to continue to do this in the future, unless people ask me to.
Attachment:
signature.asc
Description: This is a digitally signed message part.