Am 19.05.25 um 07:46 schrieb Antonio Russo:
There is progress on this, but it is occurring in real time. My suggestion
is to wait for upstream to decide they understand it, finalize the PR,
merge
it, and then back port the fix to 2.3. This last step may be painful,
since
the analysis may have to be re-done on the early state of the code in 2.3.
The fix has just been merged into master so it seems like upstream
thinks it's finalized enough.
As for backporting, should be fairly easy. I took a look at the affected
file, and that file (or at least the related code) hasn't been modified
since it was introduced 6 years ago, so should be fairly simple to
backport to whatever version, even way back to 2.0.0 if necessary.
Unless I'm missing something?
I would recommend reducing the severity of this bug to important so that
zfs is not removed from trixie.
I thought a bug with potential data loss would be correctly classified
as "grave", but I don't know much about how Debian usually handles
situations like these where the bug has existed for a long time already.
I'm happy to downgrade this to important (if necessary) if the package
will be removed from trixie otherwise. But right now, at least to me,
there should still be enough time to get this fixed, right?
Best,
Florian Bach
