Control: severity -1 normal
         # this is no policy violation and doesn't make the package
         # unsuitable for release
         # /etc/default/iodine is not shipped and is no conffile
Control: found -1 0.6.0~rc1-13
Control: tag -1 + confirmed

         
On Sat, 21 Jun 2014 19:58:24 +0000, Debian bug at v.nix.is wrote:

> Package: iodine
> Version: 0.6.0~rc1-19
> Severity: serious
> 
> I couldn't find out how to re-open an existing bug 

unarchive + reopen.
Cf. https://www.debian.org/Bugs/server-control

> but this issue that
> I reported & was resolved a while ago is now happening again:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612723
> 
> Upgrading from 0.6.0~rc1-12 to 0.6.0~rc1-19 yields a munged config
> file as noted in 612723, since that bug was solved back in 2011 I've
> upgraded iodine several times, so this must be some regression in the
> control scripts for it.

Hm.

Ah, there it is:

#v+
iodine (0.6.0~rc1-13) unstable; urgency=low

..
  * Rewrite handling of /etc/default/iodine according to debconf-devel(7)
    in debian/config and debian/postinst.
...

 -- gregor herrmann <gre...@debian.org>  Thu, 09 May 2013 15:35:58 +0200
#v-

which touches debian/config and is the reason for this regression.


Alright, working on a fix.


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Pink Floyd: The Dogs of War

Attachment: signature.asc
Description: Digital Signature

Reply via email to