[pkg-bacula-commits] [bacula] 01/04: Updated TODO
Carsten Leonhardt
leo at moszumanska.debian.org
Mon Aug 29 10:52:53 UTC 2016
This is an automated email from the git hooks/post-receive script.
leo pushed a commit to branch migrate-files
in repository bacula.
commit d627941f0667ed8b328c3529ae96dc1297bfac02
Author: Carsten Leonhardt <leo at debian.org>
Date: Mon Aug 29 11:24:32 2016 +0200
Updated TODO
---
debian/TODO | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/debian/TODO b/debian/TODO
index abd5e34..4363be7 100644
--- a/debian/TODO
+++ b/debian/TODO
@@ -6,7 +6,16 @@ High:
- Use ucf to handle conffiles
- Guard calls to ucf / ucfr with checks for existence of ucf / ucfr
- check that all conffiles are correctly owned by its package
- * Don't "rm -fr" so much during purge of bacula-common
+ - maybe refer to old development git tag
+ development/migrate-to-ucf-2012-06-07
+ * Find a better solution to "rm -fr /etc/bacula" during purge of
+ bacula-common:
+ The problem: some bacula packages with conffiles are removed but
+ not purged. If bacula-common is then purged, it deletes all the
+ config files, even those owned by other, still unpurged
+ packages. ucf will think the user deleted the config files, which
+ leads to the situation that if bacula is now reinstalled, ucf
+ will not reinstall the conffiles that it thinks the user deleted.
Normal:
@@ -44,4 +53,3 @@ Review unmerged old changes:
* Ask for passwords via debconf (git tag development/2011-04-29)
d4676fc19978a0588bb09a58234cf451d15859d6 Don't set passwords at build time but ask for them
aea2145a4f135fa6d18d33384a1af2c2bffc8617 Get rid of useless common-functions
- * migrate config files to ucf (git tag development/migrate-to-ucf-2012-06-07)
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-bacula/bacula.git
More information about the pkg-bacula-commits
mailing list