Your message dated Tue, 08 Jul 2025 06:16:55 +0000
with message-id <[email protected]>
and subject line unblock zfs-linux
has caused the Debian Bug report #1108224,
regarding unblock: zfs-linux/2.3.2-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1108224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108224
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: unblock
Control: affects -1 src:zfs-linux
Dear release managers,
Please unblock package zfs-linux (pre-approval request).
Please see [1] for current state of the package, and [2] for diff
between 2.3.3-1 and 2.3.2-1 (current in trixie).
[ Reason ]
There are two main reasons for this unblock request:
1. zfs has released a stable release 2.3.3, which contains multiple bug
fixes, especially the RC bug #1106035. We would like to include this
version in trixie.
2. zfs does not run any autopkgtest on i386 due to no kernel image is
availble on that platform (but userspace tools are still useful). So
it will be blocked by britney even after the delay.
[ Impact ]
Since there's an RC bug, we need to cherry-pick fixes to prevent zfs
from being removed. This will however lead to another unblock request
due to reason 2.
[ Tests ]
* zfs has its test suites covering multiple distributions & kernels.
* I have run both autopkgtest (smoking tests) and zfs test suites
manually on my trixie install.
[ Risks ]
The whole changes are large, but mostly upstream diff. Since the code
is a upstream stable release, and that they are heavily tested, I reckon
this part to be relatively safe.
For the debian part, I did not make non-trivial modifications.
My changes include:
* refresh of patch sets (only line offsets changed)
* tiny changes to library symbol list (there are some deletions, but
these libraries are internally used and we use strict version
dependency, so this is not a ABI break).
* changes to d/copyright to make lintian happy.
[ Checklist ]
[*] all changes are documented in the d/changelog
[*] I reviewed all changes and I approve them
[ ] attach debdiff against the package in testing -- no, please see
above for explanation
unblock zfs-linux/2.3.3-1
[1]:
https://salsa.debian.org/zfsonlinux-team/zfs/-/commit/ea33dd4d6fe6464f9739c3dad013637984c1ddf9
[2]:
https://salsa.debian.org/zfsonlinux-team/zfs/-/compare/debian%2F2.3.2-1...master?from_project_id=13840
--- End Message ---
--- Begin Message ---
Unblocked.
--- End Message ---
