Bug#839102: (no subject)

2020-01-11 Thread Michael Bemmerl
David Bremner schrieb: > > This is almost certainly related to the maintainer scripts using : as a > replacement for newline when storing /etc/nullmailer/remotes in the > debconf database. I can confirm it is the sed command in postinst, line 36. https://sources.debian.org/src/nullmailer/1:2.2-3/

Bug#839102: (no subject)

2020-01-11 Thread Michael Bemmerl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Version: 1:2.2-3 FYI: This bug is also present in Version 1:2.2-3 (updating from stretch to buster). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAl4aNgsACgkQKmk3pLlDYV77rQCcCvg66nbyPwE7wZ+Lf72AlDjy MvwAn2ZqFfQXhSAYO78xX

Bug#839102: (no subject)

2018-04-29 Thread Michael Bemmerl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Version: 1:1.13-1.2 FYI: This bug is also present in Version 1:1.13-1.2 (stretch). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlrmOVwACgkQKmk3pLlDYV6rrQCeNRN2iFaEujHTINybh+SVzzLo 6+cAnjojjLJfGZkskchJg2EgQz/1arcg =UOrU -

Bug#839102: nullmailer: Update to 1:1.13-1+deb8u1 corrupts entry in "remotes"

2016-09-28 Thread Michael Bemmerl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: nullmailer Version: 1:1.13-1+deb8u1 Severity: important The latest update (installed by apt) from 1:1.13-1 to 1:1.13-1+deb8u1 corrupted my nullmailer remotes configuration. I'm using a somewhat cryptic password with special chars. Something