[Piuparts-commits] [SCM] piatti.debian.org configuration files branch, master, updated. 148332ef45997ba3aaf38cc2c9a28441083bad49

Holger Levsen holger at layer-acht.org
Fri Dec 23 10:24:04 UTC 2011 

The following commit has been merged in the master branch:
commit ccf37c238bbdc049552beb6248f63838abbe3226
Author: Holger Levsen <holger at layer-acht.org>
Date:   Sun Nov 27 14:18:01 2011 +0100

    share my templates for filing bugs

diff --git a/org/piuparts.debian.org/etc/templates/mail/command_not_found_during_purge.mail b/org/piuparts.debian.org/etc/templates/mail/command_not_found_during_purge.mail
new file mode 100644
index 0000000..c4c8fff
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/command_not_found_during_purge.mail
@@ -0,0 +1,26 @@
+To: submit at bugs.debian.org
+Subject: "command not found" during purge
+
+Package:
+Version:
+Severity: normal
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed a "command not found" during purge, the
+relevant lines from the attached logfile (scroll down to the end) are:
+
+
+
+From the third paragraph about the meaning of the depends field in
+http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps
+
+The Depends field should also be used if the postinst, prerm or postrm scripts
+require the package to be present in order to run. __Note, however, that the
+postrm cannot rely on any non-essential packages to be present during the
+purge phase__.
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/cronjob_exits_with_error_after_package_removal.mail b/org/piuparts.debian.org/etc/templates/mail/cronjob_exits_with_error_after_package_removal.mail
new file mode 100644
index 0000000..8a0ccef
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/cronjob_exits_with_error_after_package_removal.mail
@@ -0,0 +1,19 @@
+To: submit at bugs.debian.org
+Subject: cronjob exits with error after package removal
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your packages cronjob exits with
+error after the package has been removed.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/cronjob_produces_output_after_package_removal.mail b/org/piuparts.debian.org/etc/templates/mail/cronjob_produces_output_after_package_removal.mail
new file mode 100644
index 0000000..99b3742
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/cronjob_produces_output_after_package_removal.mail
@@ -0,0 +1,19 @@
+To: submit at bugs.debian.org
+Subject: cronjob produces output after package removal
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your packages cronjob produce output
+after the package has been removed.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/doesnt_use_invoke-rc.d.mail b/org/piuparts.debian.org/etc/templates/mail/doesnt_use_invoke-rc.d.mail
new file mode 100644
index 0000000..8f4dc72
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/doesnt_use_invoke-rc.d.mail
@@ -0,0 +1,24 @@
+To: submit at bugs.debian.org
+Subject: doesnt use invoke-rc.d
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package starts processes where it
+shouldnt. This is very probably due to not using invoke-rc.d as mandated by
+policy 9.3.3.2. This is seriously disturbing! ;-)
+
+See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3
+and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well
+as /usr/share/doc/sysv-rc/README.policy-rc.d.gz
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_install.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_install.mail
new file mode 100644
index 0000000..e174623
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_install.mail
@@ -0,0 +1,20 @@
+To: submit at bugs.debian.org
+Subject: fails to install
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package failed to install. As per
+definition of the release team this makes the package too buggy for a
+release, thus the severity.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_install_due_to_incorrect_dependencies_in_init.d_LSB_header.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_install_due_to_incorrect_dependencies_in_init.d_LSB_header.mail
new file mode 100644
index 0000000..18cfd8d
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_install_due_to_incorrect_dependencies_in_init.d_LSB_header.mail
@@ -0,0 +1,21 @@
+To: submit at bugs.debian.org
+Subject: fails to install due to incorrect dependencies in init.d LSB header
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+User:     initscripts-ng-devel at lists.alioth.debian.org
+Usertags: incorrect-dependency
+
+Hi,
+
+during a test with piuparts I noticed your package failed to install due to
+incorrect dependencies in the init.d LSB header. Some debian notes are
+available from at http://wiki.debian.org/LSBInitScripts
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_install_trying_to_overwrite_other_packages_files.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_install_trying_to_overwrite_other_packages_files.mail
new file mode 100644
index 0000000..e447276
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_install_trying_to_overwrite_other_packages_files.mail
@@ -0,0 +1,22 @@
+To: submit at bugs.debian.org
+Subject: fails to install, trying to overwrite other packages files
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package failed to install because
+it tries to overwrite other packages files without declaring a replaces
+relation.
+
+See policy 7.6 at
+http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_purge.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge.mail
new file mode 100644
index 0000000..c66f7b8
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge.mail
@@ -0,0 +1,18 @@
+To: submit at bugs.debian.org
+Subject: fails to purge
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package failed to purge.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_-_command_(deluser|adduser)_in_postrm_not_found.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_-_command_(deluser|adduser)_in_postrm_not_found.mail
new file mode 100644
index 0000000..997dd4d
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_-_command_(deluser|adduser)_in_postrm_not_found.mail
@@ -0,0 +1,30 @@
+To: submit at bugs.debian.org
+Subject: fails to purge - command (deluser|adduser) in postrm not found
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package failed to purge due 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...):
+
+The fix should be easy: your package is using adduser or deluser from the
+adduser package, which is only priority important. Using useradd or userdel
+from the passwd package should fix this problem.
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_-_command_in_postrm_not_found.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_-_command_in_postrm_not_found.mail
new file mode 100644
index 0000000..42cfa7b
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_-_command_in_postrm_not_found.mail
@@ -0,0 +1,27 @@
+To: submit at bugs.debian.org
+Subject: fails to purge - command in postrm not found
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package failed to purge due 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...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_due_to_incorrect_dependencies_in_init.d_LSB_header.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_due_to_incorrect_dependencies_in_init.d_LSB_header.mail
new file mode 100644
index 0000000..9101acc
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_purge_due_to_incorrect_dependencies_in_init.d_LSB_header.mail
@@ -0,0 +1,21 @@
+To: submit at bugs.debian.org
+Subject: fails to purge due to incorrect dependencies in init.d LSB header
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+User:     initscripts-ng-devel at lists.alioth.debian.org
+Usertags: incorrect-dependency
+
+Hi,
+
+during a test with piuparts I noticed your package failed to purge due to
+incorrect dependencies in the init.d LSB header. Some debian notes are
+available from at http://wiki.debian.org/LSBInitScripts
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_remove.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_remove.mail
new file mode 100644
index 0000000..ba03a8d
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_remove.mail
@@ -0,0 +1,17 @@
+To: submit at bugs.debian.org
+Subject: fails to remove
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package fails to remove.
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/fails_to_upgrade_from_lenny.mail b/org/piuparts.debian.org/etc/templates/mail/fails_to_upgrade_from_lenny.mail
new file mode 100644
index 0000000..884a6e7
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/fails_to_upgrade_from_lenny.mail
@@ -0,0 +1,18 @@
+To: submit at bugs.debian.org
+Subject: : fails to upgrade from lenny
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package fails to upgrade from
+lenny. It installed fine in lenny, then the upgrade to squeeze fails.
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/modifying_files_from_another_package.mail b/org/piuparts.debian.org/etc/templates/mail/modifying_files_from_another_package.mail
new file mode 100644
index 0000000..3e825c0
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/modifying_files_from_another_package.mail
@@ -0,0 +1,20 @@
+To: submit at bugs.debian.org
+Subject: modifying files from another package
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package modifies files from another
+package in /usr. This is so wrong, I'm not even bothered to look up the part
+of policy this violates ;-P
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/owned_after_purge_(policy_6.8_+_10.7.3).mail b/org/piuparts.debian.org/etc/templates/mail/owned_after_purge_(policy_6.8_+_10.7.3).mail
new file mode 100644
index 0000000..da63b1a
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/owned_after_purge_(policy_6.8_+_10.7.3).mail
@@ -0,0 +1,21 @@
+To: submit at bugs.debian.org
+Subject: owned after purge (policy 6.8 + 10.7.3)
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left owned files on the
+system after purge, which is a violation of policy 6.8 and 10.7.3:
+
+http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
+http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/owned_and_unowned_files_after_purge_(policy_6.8_+_10.7.3).mail b/org/piuparts.debian.org/etc/templates/mail/owned_and_unowned_files_after_purge_(policy_6.8_+_10.7.3).mail
new file mode 100644
index 0000000..6848525
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/owned_and_unowned_files_after_purge_(policy_6.8_+_10.7.3).mail
@@ -0,0 +1,22 @@
+To: submit at bugs.debian.org
+Subject: owned and unowned files after purge (policy 6.8 + 10.7.3)
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left owned and
+unowned files on the system after purge, which is a violation of policy 6.8
+and 10.7.3:
+
+http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
+http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3
+
+From the attached log (scroll to the bottom...):
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/package_removed_processes_still_running.mail b/org/piuparts.debian.org/etc/templates/mail/package_removed_processes_still_running.mail
new file mode 100644
index 0000000..264631a
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/package_removed_processes_still_running.mail
@@ -0,0 +1,22 @@
+To: submit at bugs.debian.org
+Subject: package removed, processes still running
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left processes running
+after the package has been removed and/or purged.
+
+In http://lists.debian.org/debian-devel/2009/08/msg00182.html and followups 
+it has been agreed that these bugs are to be filed with severity serious.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/prompting_due_to_modified_conffiles_which_where_not_modified_by_the_user.mail b/org/piuparts.debian.org/etc/templates/mail/prompting_due_to_modified_conffiles_which_where_not_modified_by_the_user.mail
new file mode 100644
index 0000000..e83c3e2
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/prompting_due_to_modified_conffiles_which_where_not_modified_by_the_user.mail
@@ -0,0 +1,34 @@
+To: submit at bugs.debian.org
+Subject: prompting due to modified conffiles which where not modified by the user
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package failed the piuparts upgrade
+test because dpkg detected a conffile as being modified and then prompted the
+user for an action. As there is no user input, this fails. But this is not
+the real problem, the real problem is that this prompt shows up in the first
+place, as there was nobody modifying this conffile at all, the package has
+just been installed and upgraded...
+
+This is a violation of policy 10.7.3, see
+http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which
+says "[These scripts handling conffiles] must not ask unnecessary questions
+(particularly during upgrades), and must otherwise be good citizens."
+
+http://wiki.debian.org/DpkgConffileHandling should help with figuring out how
+to do this properly.
+
+In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it
+has been agreed that these bugs are to be filed with severity serious.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/prompts_user_without_following_Debian_Configuration_Management_Specification.mail b/org/piuparts.debian.org/etc/templates/mail/prompts_user_without_following_Debian_Configuration_Management_Specification.mail
new file mode 100644
index 0000000..69bccf9
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/prompts_user_without_following_Debian_Configuration_Management_Specification.mail
@@ -0,0 +1,45 @@
+To: submit at bugs.debian.org
+Subject: prompts user without following Debian Configuration Management Specification
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package prompts the user badly.
+Prompting in maintainer scripts must be done by communicating through a
+program such as debconf which conforms to the Debian Configuration management
+specification, version 2 or higher.
+
+Refer to Debian Policy Manual section 3.9.1 (Prompting in maintainer scripts)
+for details. Quoting from
+http://www.debian.org/doc/debian-policy/ch-binary.html#s-maintscriptprompt
+
+------------------------------------------------------------------------------
+[ 3.9.1 Prompting in maintainer scripts ]
+Package maintainer scripts may prompt the user if necessary. Prompting must be
+done by communicating through a program, such as debconf, which conforms to
+the Debian Configuration Management Specification, version 2 or higher.
+
+Packages which are essential, or which are dependencies of essential packages,
+may fall back on another prompting method if no such interface is available
+when they are executed.
+
+The Debian Configuration Management Specification is included in the
+debconf_specification files in the debian-policy package.
+------------------------------------------------------------------------------
+
+From the attached log (scroll to the bottom...):
+
+
+
+And as it's not possible to set two usertags at the same time, this also
+should to be done:
+
+User: lintian-maint at debian.org
+Usertags: read-in-maintainer-script
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/unowned_directories_in_usr_local_after_purge_(policy_6.8_and_9.1.2).mail b/org/piuparts.debian.org/etc/templates/mail/unowned_directories_in_usr_local_after_purge_(policy_6.8_and_9.1.2).mail
new file mode 100644
index 0000000..3b1e354
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/unowned_directories_in_usr_local_after_purge_(policy_6.8_and_9.1.2).mail
@@ -0,0 +1,25 @@
+To: submit at bugs.debian.org
+Subject: unowned directories in /usr/local after purge (policy 6.8 and 9.1.2)
+
+Package:
+Version:
+Severity: normal
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left unowned files on the
+system after purge, which is a violation of policy 6.8:
+
+http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
+
+From the attached log (scroll to the bottom...):
+
+
+Leaving directories in /usr/local after purge is also a violation of a
+should-directive in
+http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/unowned_files_after_purge_(policy_6.8)_violating_FHS_(policy_9.1)_too.mail b/org/piuparts.debian.org/etc/templates/mail/unowned_files_after_purge_(policy_6.8)_violating_FHS_(policy_9.1)_too.mail
new file mode 100644
index 0000000..a1b4b64
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/unowned_files_after_purge_(policy_6.8)_violating_FHS_(policy_9.1)_too.mail
@@ -0,0 +1,25 @@
+To: submit at bugs.debian.org
+Subject: unowned files after purge (policy 6.8) violating FHS (policy 9.1) too
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left unowned files on the
+system after purge, which is a violation of policy 6.8:
+
+http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
+
+From the attached log (scroll to the bottom...):
+
+
+As putting files into /usr/local is also a violation of
+http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting
+the severity to serious.
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/unowned_files_after_purge_(policy_6.8_and_10.8).mail b/org/piuparts.debian.org/etc/templates/mail/unowned_files_after_purge_(policy_6.8_and_10.8).mail
new file mode 100644
index 0000000..e3f49ee
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/unowned_files_after_purge_(policy_6.8_and_10.8).mail
@@ -0,0 +1,24 @@
+To: submit at bugs.debian.org
+Subject: unowned files after purge (policy 6.8, 10.8)
+
+Package:
+Version:
+Severity: important
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left unowned files on the
+system after purge, which is a violation of policy 6.8 (or 10.8):
+
+http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
+
+Filing this as important as having a piuparts clean archive is a release goal
+since lenny.
+
+From the attached log (scroll to the bottom...):
+
+
+
+cheers,
diff --git a/org/piuparts.debian.org/etc/templates/mail/unowned_files_in_usr_local_after_purge_(policy_6.8).mail b/org/piuparts.debian.org/etc/templates/mail/unowned_files_in_usr_local_after_purge_(policy_6.8).mail
new file mode 100644
index 0000000..2194d79
--- /dev/null
+++ b/org/piuparts.debian.org/etc/templates/mail/unowned_files_in_usr_local_after_purge_(policy_6.8).mail
@@ -0,0 +1,25 @@
+To: submit at bugs.debian.org
+Subject: unowned files in /usr/local after purge (policy 6.8)
+
+Package:
+Version:
+Severity: serious
+User: debian-qa at lists.debian.org
+Usertags: piuparts piuparts.d.o
+
+Hi,
+
+during a test with piuparts I noticed your package left unowned files on the
+system after purge, which is a violation of policy 6.8:
+
+http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
+
+From the attached log (scroll to the bottom...):
+
+
+As putting files into /usr/local is also a violation of
+http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting
+the severity to serious.
+
+
+cheers,

-- 
piatti.debian.org configuration files

More information about the Piuparts-commits mailing list