summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGabriel F. T. Gomes <gabriel@inconstante.eti.br>2018-12-12 23:28:43 -0200
committerGabriel F. T. Gomes <gabriel@inconstante.eti.br>2018-12-12 23:28:43 -0200
commit7d413831f1a8ac1181f21efdae594fc8ac5ec0f3 (patch)
treefb6e5bdc829b52ebe5df3394b7ac2eddd208f94f
parente55d81a56ae89ee0b9cd3bc1e6fc683a33c17991 (diff)
downloadbash-completion-7d413831f1a8ac1181f21efdae594fc8ac5ec0f3.tar.gz
Purge conffiles files deleted in version 1:1.3-2 (bug #645439)
The commits: commit 4bfa85b495bff991ee9d142f7584b2a1b198c344 Author: David Paleino <dapal@debian.org> Date: Mon Apr 11 11:50:14 2011 +0200 Re-implement triggers and commit a98c7d29191dbd44a29b58623fa4fa8b4f7c6fcb Author: David Paleino <dapal@debian.org> Date: Sun Apr 10 15:53:39 2011 +0200 Fix cronscript name deleted the conffiles /etc/apt/apt.conf.d/99-bash-completion and /etc/cron.monthly/bash-completion.cron, respectively, without updating the maintainer scripts to purge the files. This patch adds the files to debian/maintscript, setting the version to the next release of bash-completion, as required by dpkg-maintscript-helper: rm_conffile conffile [prior-version [package]] prior-version Defines the latest version of the package whose upgrade should trigger the operation. It is important to calculate prior-version correctly so that the operations are correctly performed even if the user rebuilt the package with a local version. If prior-version is empty or omitted, then the operation is tried on every upgrade (note: it's safer to give the version and have the operation tried only once). If the conffile has not been shipped for several versions, and you are now modifying the maintainer scripts to clean up the obsolete file, prior-version should be based on the version of the package that you are now preparing, not the first version of the package that lacked the conffile. This applies to all other actions in the same way. For example, for a conffile removed in version 2.0-1 of a package, prior-version should be set to 2.0-1~. This will cause the conffile to be removed even if the user rebuilt the previous version 1.0-1 as 1.0-1local1. Or a package switching a path from a symlink (shipped in version 1.0-1) to a directory (shipped in version 2.0-1), but only performing the actual switch in the maintainer scripts in version 3.0-1, should set prior-version to 3.0-1~.
-rw-r--r--debian/maintscript2
1 files changed, 2 insertions, 0 deletions
diff --git a/debian/maintscript b/debian/maintscript
index 0d418cd5..400575db 100644
--- a/debian/maintscript
+++ b/debian/maintscript
@@ -6,6 +6,8 @@ rm_conffile /etc/bash_completion.d/dcop 1:2.8-5~
rm_conffile /etc/bash_completion.d/mock 1:2.8-5~
rm_conffile /etc/bash_completion.d/modules 1:2.8-5~
rm_conffile /etc/bash_completion.d/repomanage 1:2.8-5~
+rm_conffile /etc/apt/apt.conf.d/99-bash-completion 1:2.8-5~
+rm_conffile /etc/cron.monthly/bash-completion.cron 1:2.8-5~
rm_conffile /etc/bash_completion.d/helpers/perl 1:2.0-1
rm_conffile /etc/bash_completion.d/abook 1:2.0-1
rm_conffile /etc/bash_completion.d/ant 1:2.0-1