Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument

2022-07-11 Thread Michael Hudson-Doyle
On Tue, 12 Jul 2022 at 04:30, Aurelien Jarno wrote: > On 2022-07-11 10:06, Michael Hudson-Doyle wrote: > > It looks like a no-change rebuild fixed this in Ubuntu fwiw. > > Thanks, I confirm that in Debian too. Do you have an idea why? It could > be a missing or too loose dependency. > No. I got

Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument

2022-07-11 Thread Aurelien Jarno
On 2022-07-11 10:06, Michael Hudson-Doyle wrote: > It looks like a no-change rebuild fixed this in Ubuntu fwiw. Thanks, I confirm that in Debian too. Do you have an idea why? It could be a missing or too loose dependency. > On Mon, 11 Jul 2022 at 09:54, Aurelien Jarno wrote: > > > Source:

Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument

2022-07-10 Thread Michael Hudson-Doyle
It looks like a no-change rebuild fixed this in Ubuntu fwiw. On Mon, 11 Jul 2022 at 09:54, Aurelien Jarno wrote: > Source: glibc, wcc > Control: found -1 glibc/2.34-0experimental4 > Control: found -1 wcc/0.0.2+dfsg-4.1 > Severity: important > Tags: experimental > > Dear maintainers, > > The

Bug#1014729: glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument

2022-07-10 Thread Aurelien Jarno
Source: glibc, wcc Control: found -1 glibc/2.34-0experimental4 Control: found -1 wcc/0.0.2+dfsg-4.1 Severity: important Tags: experimental Dear maintainers, The autopkgtest of wcc fails in sid on amd64 when that autopkgtest is run with the binary packages of glibc from experimental. It passes