On Tue, 2025 Sep 23 02:36-04:00, Martin-Éric Racine wrote: > > The delta between 10.1 and 10.2 is too big to even remotely consider > pushing that into proposed-updates. Full stop. > > If you find the right upstream Git commit to fix this and we can > reasonably check that it won't break something else, we can push a > targeted fix.
Why do you assume that some commit from the upstream Git repo will yield a better targeted fix? No such fix was noted in the release notes, so the issue could well have been addressed as a side effect of other changes. Maybe you could extract some particular edit from the commit that fixes the crash. But then, why would that edit be any better than mine? At least I went after this bug specifically. > If not, we won't. Gentle reminder that *you* are the maintainer of this package, and as such it is your responsibility, not mine, to address bugs that are reported against it. I am happy to assist you in this as I can. But requiring me to do a full Git bisection in a component that is quite cumbersome to test, is a bit much---especially when I've already provided and tried out a fix. (To say nothing of the fact that "we won't" effectively means keeping a known segfault bug in a critical networking component of a default Debian stable system.)
