Package: iodine Version: 0.6.0~rc1-19 Severity: serious I couldn't find out how to re-open an existing bug 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. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iodine depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii libc6 2.19-1 ii udev 204-8 ii zlib1g 1:1.2.8.dfsg-1 iodine recommends no packages. Versions of packages iodine suggests: ii dnsutils 1:9.9.5.dfsg-4 pn fping | oping <none> ii gawk 1:4.1.1+dfsg-1 ii ipcalc 0.41-4 ii iproute2 3.14.0-2 -- debconf information: iodine/daemon_options: -c -p 5252 172.31.255.1/27 gg.nix.is iodine/start_daemon: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
