Bug#839102: (no subject)

2020-01-12 Thread David Bremner 
Michael Bemmerl  writes:

> 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/debian/postinst/#L36
>
> I just executed that command manually on a dummy remotes file and it
> exactly corrupted the config as described above.

Yes, that sounds right. Leaving aside for the moment that the sed is
pretty unmaintainable, the underlying problem seems to be the
roundtripping of /etc/nullmailer/remotes via a colon separated list in
debconf. Probably this should be reworked to use debconf multiline
support. For my own use just deleting the whole "magic" (re)creation of
/etc/nullmailer/remotes would work fine, but I tend to have a minimalist
view of what debian packages should do.

d

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/debian/postinst/#L36

I just executed that command manually on a dummy remotes file and it
exactly corrupted the config as described above.

Regards,
Michael



signature.asc
Description: OpenPGP digital signature

Bug#839102: (no subject)

2020-01-11 Thread David Bremner 
Michael Bemmerl  writes:

>
> FYI: This bug is also present in Version 1:2.2-3 (updating from stretch
> to buster).

This is almost certainly related to the maintainer scripts using : as a
replacement for newline when storing /etc/nullmailer/remotes in the
debconf database.

It all looks like a pretty bad idea to me, but I don't know how easy it
is to change.

d

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
MvwAn2ZqFfQXhSAYO78xXACjSLcZEa9C
=WYSA
-END PGP SIGNATURE-

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
-END PGP SIGNATURE-