[Debian-med-packaging] Bug#688433: analysing

Olivier Sallou olivier.sallou at irisa.fr
Mon Sep 24 09:34:30 UTC 2012

I gonna analyse this deeply, but looking at the code vs policy:

- local changes are preserved during a package upgrade
- configuration files is preserved when the package is removed, and only
deleted when the package is purged.

The package "updates", indeed, the conf file at upgrades etc.. but only
regarding debconf data. If debconf data are not changed, the code
"updates" the file (data modified), but with the same content, keeping
user modifications.
At first install, debconf questions update the conf file to get the
package ready to run.

Code could check for updates to avoid rewriting the file "for nothing".
I gonna see if this can be changed at upstream.

So I do not think, at this time of the analysis, that Policy is not
followed and that severity could be reduced waiting for upstream
modification to avoid an update when not required (reconfigure or new
debconf questions).

If issue is related to the 1rst modification with debconf questions, I
understand that the file should not be in conffiles but postinst should
use a template to generate it in /etc/biomaj at first use, but also
manage the purge deletion.



gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20120924/e594811f/attachment-0001.html>

More information about the Debian-med-packaging mailing list