[Piuparts-devel] [Git][debian/piuparts][develop] raise fails-to-purge severity to serious

Holger Levsen gitlab at salsa.debian.org
Tue Jan 8 15:02:11 GMT 2019


Holger Levsen pushed to branch develop at Debian / piuparts


Commits:
6350645f by Andreas Beckmann at 2019-01-08T14:58:11Z
raise fails-to-purge severity to serious

old bugs are filed/fixed and any failure due to a regression
in sid will block migration anyway

Signed-off-by: Andreas Beckmann <anbe at debian.org>

- - - - -


6 changed files:

- bug-templates/fails_to_purge.mail
- bug-templates/fails_to_purge_-_command_deluser_adduser_in_postrm_not_found.mail
- bug-templates/fails_to_purge_-_command_in_postrm_not_found.mail
- bug-templates/fails_to_purge_-_command_ucf_in_postrm_not_found.mail
- bug-templates/fails_to_purge_due_to_incorrect_dependencies_in_init.d_LSB_header.mail
- debian/changelog


Changes:

=====================================
bug-templates/fails_to_purge.mail
=====================================
@@ -3,7 +3,7 @@ Subject: fails to purge:
 
 Package:
 Version:
-Severity: important
+Severity: serious
 User: debian-qa at lists.debian.org
 Usertags: piuparts
 
@@ -13,12 +13,6 @@ during a test with piuparts I noticed your package failed to purge.
 According to policy 7.2 you cannot rely on the depends being available
 during purge, only the essential packages are available for sure.
 
-Filing this as important because a.) it's a clear policy violation (to
-not clean up at purge) b.) having a piuparts clean archive is a release
-goal since lenny and c.) this package being piuparts buggy blocks
-packages depending on it from being tested by piuparts (and thus
-possibly the detection of more severe problems).
-
 From the attached log (scroll to the bottom...):
 
 


=====================================
bug-templates/fails_to_purge_-_command_deluser_adduser_in_postrm_not_found.mail
=====================================
@@ -3,7 +3,7 @@ Subject: fails to purge - command (deluser|adduser) in postrm not found
 
 Package:
 Version:
-Severity: important
+Severity: serious
 User: debian-qa at lists.debian.org
 Usertags: piuparts
 
@@ -28,12 +28,6 @@ been decided it should be sufficient to have the postrm script ignore
 any errors from deluser:
   deluser ... || true
 
-Filing this as important because a.) it's a clear policy violation (to
-not clean up at purge) b.) having a piuparts clean archive is a release
-goal since lenny and c.) this package being piuparts buggy blocks
-packages depending on it from being tested by piuparts (and thus
-possibly the detection of more severe problems).
-
 From the attached log (scroll to the bottom...):
 
 


=====================================
bug-templates/fails_to_purge_-_command_in_postrm_not_found.mail
=====================================
@@ -3,7 +3,7 @@ Subject: fails to purge - command in postrm not found
 
 Package:
 Version:
-Severity: important
+Severity: serious
 User: debian-qa at lists.debian.org
 Usertags: piuparts
 
@@ -14,12 +14,6 @@ to a command not found. According to policy 7.2 you cannot rely on the
 depends being available during purge, only the essential packages are
 available for sure.
 
-Filing this as important because a.) it's a clear policy violation (to
-not clean up at purge) b.) having a piuparts clean archive is a release
-goal since lenny and c.) this package being piuparts buggy blocks
-packages depending on it from being tested by piuparts (and thus
-possibly the detection of more severe problems).
-
 From the attached log (scroll to the bottom...):
 
 


=====================================
bug-templates/fails_to_purge_-_command_ucf_in_postrm_not_found.mail
=====================================
@@ -3,7 +3,7 @@ Subject: fails to purge - command ucf in postrm not found
 
 Package:
 Version:
-Severity: important
+Severity: serious
 User: debian-qa at lists.debian.org
 Usertags: piuparts
 
@@ -17,12 +17,6 @@ available for sure.
 Please see the manpages ucf(1), ucfr(1) and the example maintainer
 scripts under /usr/share/doc/ucf/examples/ for correct usage of ucf.
 
-Filing this as important because a.) it's a clear policy violation (to
-not clean up at purge) b.) having a piuparts clean archive is a release
-goal since lenny and c.) this package being piuparts buggy blocks
-packages depending on it from being tested by piuparts (and thus
-possibly the detection of more severe problems).
-
 From the attached log (scroll to the bottom...):
 
 


=====================================
bug-templates/fails_to_purge_due_to_incorrect_dependencies_in_init.d_LSB_header.mail
=====================================
@@ -3,7 +3,7 @@ Subject: fails to purge due to incorrect dependencies in init.d LSB header
 
 Package:
 Version:
-Severity: important
+Severity: serious
 User: debian-qa at lists.debian.org
 Usertags: piuparts
 User:     initscripts-ng-devel at lists.alioth.debian.org


=====================================
debian/changelog
=====================================
@@ -12,6 +12,8 @@ piuparts (0.96) UNRELEASED; urgency=medium
     - Handle /etc/ca-certificates.conf stretch -> buster upgrade by
       normalizing the file to match fresh installations.  (Closes: #889852)
   * scripts-broken-symlinks: Unbreak more symlinks.
+  * bug-templates: Raise severity of "fails to purge" errors to serious.
+   (see #918379)
 
   [ Holger Levsen ]
   * master-bin/detect_piuparts_issues: ignore files which vanish during run.
@@ -50,8 +52,7 @@ piuparts (0.95) unstable; urgency=medium
 
   [ Andreas Beckmann ]
   * Clarify errors from installing objects over existing symlinks.
-  * bug-templates/copyright_file_missing_after_upgrade and
-    bug-templates/unhandled_symlink_to_directory_conversion: adjust advice as
+  * bug-templates: Do not mention ${misc:Pre-Depends} as
     symlink_to_dir/dir_to_symlink are supported by dpkg in oldstable.
 
  -- Holger Levsen <holger at debian.org>  Sun, 09 Dec 2018 22:27:41 +0100



View it on GitLab: https://salsa.debian.org/debian/piuparts/commit/6350645fc15befe5899bafc85732a5eb5775b956

-- 
View it on GitLab: https://salsa.debian.org/debian/piuparts/commit/6350645fc15befe5899bafc85732a5eb5775b956
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/piuparts-devel/attachments/20190108/7916685a/attachment-0001.html>


More information about the Piuparts-devel mailing list