On Thu, 9 Apr 2020 16:35:13 +0200 Sebastian Andrzej Siewior <sebast...@breakpoint.cc> wrote: > I suggested already something in [0]. Back then we were hoping for some > feedback from the debhelper team. > Now I was just asking if Jonathan is handling this and/or if we could > also bump to current upstream version while at it. > > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945961#10
As Dimitri pointed out we have also been affected by this but in Ubuntu - we found it out recently when doing archive rebuilds on Focal. The proposed fix in #10 does workaround the issue and it is not necessary to change the build-arch rules as Dimitri suggested. I do wonder if this is in fact a regression in debhelper. I tracked it down to debhelper 12.4 to 12.5 and while I haven't been able to pinpoint exactly what particular change there is causing it I believe it is in how double colon rules are being interpreted. It seems the debhelper changes somehow fail to detect the build-arch rules. Unless someone knows enough perl to dig into debhelper changes between 12.4 and 12.5 and check if that is in fact a regression, I would suggest to simply apply the proposed change in comment #10. Thanks for your help =) Tiago Daitx
