On 2 January 2011 11:44, Mario 'BitKoenig' Holbe <mario.ho...@tu-ilmenau.de> wrote: > Package: snort > Version: 2.8.5.2-6 > > Hello, > > the new snort.debian.conf handling adds a -p to snort/options on each > re-install if snort/disable_promiscuous is true: (...)
You are right, this is because the DEBIAN_SNORT_OPTIONS value is read on package configuration and is used to populate the debconf values in case the admin manually changes the file. Since the value is used for two debconf settings (snor/disable_promiscuous and I have a fix ready for this which just removes the trailing ' -p' from that variable (if it exists) that is introduced automatically. > Btw: the new handling considers *each* snort.debian.conf from an older > package version as manually changed, because the (comments) header of > the new template changed and no old md5sum file exists. Are you sure about this? I cannot reproduce this, I explicitly added a check to verify if the user is using the autogenerated file from previous releases and it (transparently) handles the update to the new file (with the new comment headers). > Btw2: why do you re-invent all that changes-tracking and implement it > all on your own? Why don't you just put snort.debian.conf under ucf > control? ucf does everything you want and does it better - it asks the > user whether to replace a changed file or not and retains the old or > new version depending on user's choice similar to dpkg, for example. I might consider ucf in the future, the current system is good enough in order to ensure that user's changes are preserved with minimal hassle and dpkg-reconfigure works as expected (changing the config file even if it does not change through upgrades). It is based on x11-common's config/postinst code, so I'm not trying to reinvent the wheel here. Regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
