Hi, On 12/01/23 at 18:42 +0100, Andreas Tille wrote: > Hi Santiago, > > thanks again for watching me. ;-) > > Am Thu, Jan 12, 2023 at 05:10:50PM +0100 schrieb Santiago Vila: > > This is really weird. > > +1 > > > This package also failed for me on bookworm, with the same error > > which happened to Lucas (the one in the Subject). > > > > But today I tried again (in bookworm) and it worked, without any source > > change at all. > > (mricron version 1.2.20211006+dfsg-1). > > > > I see that this change was made to try to fix the bug: > > > > * Build-Depends: libx11-dev. Closes: #1026734 > > > > but libx11-dev was already being installed when the package was built: > > > > https://buildd.debian.org/status/fetch.php?pkg=mricron&arch=amd64&ver=1.2.20211006%2Bdfsg-1&stamp=1637004231&raw=0 > > > > (probably because of a build-dependency which in turn had a dependency on > > libx11-dev). > > Yes, this is what I assumed ... but I wanted to be super sure. > > > So, even if adding libx11-dev was probably correct and formally necessary, > > as -lX11 was being used, I think it was not the real reason for the failure. > > > > (Cc to Lucas, just in case he reported similar bugs in other packages). > > I'd be also curious what might have caused that problem.
I don't think that there was a large number of similar failures when I reported that bug. But yes it was probably a bug in another package. You could try to 'bisect' using snapshot.debian.org to find the package that introduced the problem, but it's fairly time consuming. Lucas
