Hello all,
Paul Gevers [2018-10-19 21:07 +0200]:
> With a recent upload of dnsmasq the autopkgtest of systemd fails in
> testing when that autopkgtest is run with the binary packages of dnsmasq
> from unstable.
I fixed (or rather, worked around) this recently in
Hi
Am 08.11.18 um 22:08 schrieb Simon Kelley:
> To test this, please could you apply
>
> http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=a220545c4277cba534be5ef4638b5076fc7d2cf4
>
> to 2.80 and run the test again? If that fixes the problem, I'll gladly
> take to bug back and issue a
On 07/11/2018 15:17, Michael Biebl wrote:
> Hi Simon,
>
> I see that you reassigned this back to systemd, but I know too little
> about DNS(SEC) to assess the situation. So your help on this issue would
> be most welcome.
>
> What I did is, to run the test against v2.79 and v2.80
>
> This
Hi Simon,
I see that you reassigned this back to systemd, but I know too little
about DNS(SEC) to assess the situation. So your help on this issue would
be most welcome.
What I did is, to run the test against v2.79 and v2.80
This starts a dnsmasq process like this:
nobody 11531 0.0 0.3
On 21/10/2018 00:05, Michael Biebl wrote:
> After rebuilding the LXC chroot, I was able to reproduce the issue after
> all.
>
> Runnig a git bisect shows the following as the first faulty commit
>
>
> commit 1682d15a744880b0398af75eadf68fe66128af78
> Author: Simon Kelley
> Date: Fri Aug 3
reassign -1 src:dnsmasq 2.80-1
affects -1 src:systemd
user debian...@lists.debian.org
usertags -1 - needs-update
thanks
On 21-10-18 01:05, Michael Biebl wrote:
> At this point I consider this a dnsmasq issue and leave it up to Simon
> to deal with it.
> Simon, if you see in an issue in how
After rebuilding the LXC chroot, I was able to reproduce the issue after
all.
Runnig a git bisect shows the following as the first faulty commit
commit 1682d15a744880b0398af75eadf68fe66128af78
Author: Simon Kelley
Date: Fri Aug 3 20:38:18 2018 +0100
Add missing EDNS0 section.
EDNS0
Am 19.10.18 um 21:07 schrieb Paul Gevers:
> ==
> ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
> resolved: domain-restricted DNS servers
>
Am 20.10.18 um 19:43 schrieb Paul Gevers:
> Hi Michael,
>
> On 20-10-18 01:01, Michael Biebl wrote:
>> Am 19.10.18 um 21:07 schrieb Paul Gevers:
>>
>>> ==
>>> ERROR: test_resolved_domain_restricted_dns
Hi Michael,
On 20-10-18 01:01, Michael Biebl wrote:
> Am 19.10.18 um 21:07 schrieb Paul Gevers:
>
>> ==
>> ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
>> resolved: domain-restricted DNS servers
>>
Am 19.10.18 um 21:07 schrieb Paul Gevers:
> ==
> ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
> resolved: domain-restricted DNS servers
>
Source: dnsmasq, systemd
Control: found -1 dnsmasq/2.80-1
Control: found -1 systemd/239-10
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainers,
With a recent upload of dnsmasq the autopkgtest of systemd fails in
testing when
12 matches
Mail list logo
