Bug#761658: urgency of a fix before stretch

2017-06-03 Thread Martin Steigerwald
martin f krafft - 03.06.17, 08:12: > also sprach Norbert Preining [2017-06-03 00:12 +0200]: > > Then how are you planning to deal with this serious bug after > > years of inactivity? > > Sounds like it might need ctte attention. I agree to that, since a discussion

Bug#761658: urgency of a fix before stretch

2017-06-03 Thread Marco d'Itri
On Jun 03, Norbert Preining wrote: > >As one of the systemd maintainers I am explicitly and publicly > >requesting that you do not introduce this unwanted change. > Then how are you planning to deal with this serious bug after years of > inactivity? I think that I have

Bug#761658: urgency of a fix before stretch

2017-06-03 Thread martin f krafft
also sprach Norbert Preining [2017-06-03 00:12 +0200]: > Then how are you planning to deal with this serious bug after > years of inactivity? Sounds like it might need ctte attention. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian

Bug#761658: urgency of a fix before stretch

2017-06-02 Thread Norbert Preining
Good morning, >As one of the systemd maintainers I am explicitly and publicly >requesting that you do not introduce this unwanted change. Then how are you planning to deal with this serious bug after years of inactivity? Norbert On June 3, 2017 5:49:39 AM GMT+09:00, m...@linux.it wrote: >On

Bug#761658: urgency of a fix before stretch

2017-06-02 Thread Marco d'Itri
On Jun 02, Norbert Preining wrote: > I am planning to upload an NMU fixing this issue to DELAY3 and hope that > release managers allow this fix into stretch. You cannot do a NMU just because the maintainers of a package disagree with you. As one of the systemd

Bug#761658: urgency of a fix before stretch

2017-06-02 Thread Michael Biebl
Am 02.06.2017 um 16:32 schrieb Norbert Preining: > Dear maintainers, > > leaking information, whatsoever, is not acceptable in Debian, and against > policy, at least lintian errors out on many occasions with > privacy-foobar* > errors. > > Setting the default servers to Google is not

Bug#761658: urgency of a fix before stretch

2017-06-02 Thread Norbert Preining
Dear maintainers, leaking information, whatsoever, is not acceptable in Debian, and against policy, at least lintian errors out on many occasions with privacy-foobar* errors. Setting the default servers to Google is not acceptable. Ignoring this fact with the explanation that one can