On Tue, Jun 10, 2025 at 08:26:12PM +0200, Helmut Grohne wrote:
> Hi Ted,
>
> I concur with your analysis am sorry for having introduced this. It's
> actually in the piuparts log
> https://piuparts.debian.org/sid/pass/fuse2fs_1.47.2-2.log, but it wasn't
> fatal.
No worries, it happens to all of us, and I really should have noticed
when I reviewed the patch.
How important is this that we get thes fix into Trixie? I'm not sure
how bad it will be that the diversion isn't going to be cleaned up.
WDYT?
I have a fix queued in my repo, but it will mean asking the release
time to do an unblock of a key package fairly late in the process. I
actually have a package update queued up to address a number of data
corruption bugs, and it's Murphy's law that this issue was discovered
*just* after I uploaded a package update and sent in a request to the
release time, literally just an hour or two afterwards. :-/
So I'll send an update request to the release team, but it would be
good for me to provide color commentary about this late-breaking fix.
Thanks,
- Ted
