On Sun, Oct 17, 2021 at 11:56:35PM +0200, Christoph Berg wrote: > Re: tony mancill > > I am tempted to upload a new source package to trigger a rebuild to see > > if that solves the problem with the deb in the archive. Perhaps wsjtx > > got caught up in a transition causing this subtle failure? > > > > Christoph or Dave, do you have any suggestions on how to track down the > > root cause? > > Since it works for me I don't have any idea how to debug this, except > maybe to diffoscope the two debs. That's a good idea. The diffoscope results in 100MB of diff, almost all of it in the resulting binaries, so I'm opting to focus on the build environments for now. There are a number of differences, most of which appear to be benign. The only significant ones are the GCC-10 -> GCC-11 transition and hamlib 4.1 -> 4.3 If anyone would like to take a look at the buildinfo from the archive and locally build packages or the full diffoscope between the binary packages, those files can be found here: https://people.debian.org/~tmancill/wsjtx-995198/. > No objections to trying a rebuild of course. > > > [1] https://buildd.debian.org/status/fetch.php?pkg=wsjtx&arch=armhf&ver=2.5.0%2Brepack-1&stamp=1632820833&raw=0 > > Maybe the problem is architecture-specific? The OP is on amd64 like > me, though. Yeah, I was surprised when it occurred for me. Of course, I'm making an assumption that the behavior I saw is the same as that from the original bug report. The fact that the "Tune" button couldn't even key my radio, despite the fact that I'm using CAT, makes me suspect that I might have found a issue with running a binary compiled against hamlib 4.1 against a system with 4.3 installed. That upload was on 2021-10-12, which would explain why I didn't see it a week ago; I updated my system on 2021-10-16. But that still doesn't explain why you didn't see the problem. Hmm... Thank you, tony
Attachment:
signature.asc
Description: PGP signature