> > In either case, if you make a debdiff between 3.5.1-6.1 and 3.5.1-6.2 > > you will see that the changes made between those two versions may not > > be the reason for this bug. In other words, the bug should be > > somewhere else (toolchain, whatever), not in this source package. > > Or in the dependency chain, maybe a rebuild is sufficient to fix this > like in #804311?
The error is very similar indeed. But in theory we should not need to rebuild things. We have policies regarding package names and ABIs and transitions and all that. If this is one of those cases where a transition should have happened but it did not, it would be good at least to recognize it before fixing it with a no-change rebuild. (Note: I hope the maintainers can tell something about this. I'm not even a user of this package). Thanks.
