Bug#864085: marked as done (unblock: dnsmasq/2.76-5)
Your message dated Tue, 06 Jun 2017 17:26:00 +0000
with message-id <ede30a57-933b-fb4a-2acd-2a1ad1140933@thykier.net>
and subject line Re: Bug#864085: unblock: dnsmasq/2.76-5
has caused the Debian Bug report #864085,
regarding unblock: dnsmasq/2.76-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
864085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864085
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package dnsmasq
The dnsmasq package in testing has a serious problem when dns-root-data is
installed, due to changes in the format of the dns-root-data files.
The effect is to render dnsmasq unusable.
There are several serious bugs filed to this effect, but they should
really be release-critical, eg 863896
There are also several bugs in the DNSSEC validation code, which are fixed
upstream, and really should be in stretch.
Therefore, if we can get dnsmasq-2.77-1, currently in unstable, into Stretch,
that would be a Good Thing. If not, it will need a point release.
Apologies for the short notice.
unblock dnsmasq/2.76-5
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-78-generic (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Jonathan Wiltshire:
> Control: tag -1 moreinfo
>
> On Sun, Jun 04, 2017 at 09:58:44AM +0100, ? wrote:
>> The dnsmasq package in testing has a serious problem when dns-root-data is
>> installed, due to changes in the format of the dns-root-data files.
>> The effect is to render dnsmasq unusable.
>
> Bother.
>
>> There are several serious bugs filed to this effect, but they should
>> really be release-critical, eg 863896
>>
>> There are also several bugs in the DNSSEC validation code, which are fixed
>> upstream, and really should be in stretch.
>>
>> Therefore, if we can get dnsmasq-2.77-1, currently in unstable, into Stretch,
>> that would be a Good Thing. If not, it will need a point release.
>
> The delta from testing to unstable right now is not really suitable this
> late in the process. I would prefer a targetted fix through t-p-u.
>
> However, I wonder if that format change in dns-root-data risks problems in
> other packages. Ondřej, is there any advantage to reverting that (keeping
> the RC fix for parse-root-anchors.sh)?
>
There was a fix to dns-root-data that should have solved the root issue.
We are pulling that in, which should make this change less critical.
Given that and the scope of the changes in dnsmasq, I am inclined to
close this bug as wont fix. If there are cherry-pickable changes to
dnsmasq, please consider them for a point release to Debian 9.
Thanks,
~Niels
--- End Message ---
Reply to: