Bug#928746: unblock: zfs-linux/0.7.13-1
Hi Paul,
On 2019-05-30 19:51, Paul Gevers wrote:
> or more severe in Debian BTS terms. I may have been wrong, but then
> please point me to the changes so important that you want them in
> buster. Please also be prepared to undo the new upstream release and
> just fix the bugs that are so important to you.
I've already forgotten them and I'm tired to review the diff.
Let's forget all the important stuff and only focus on the grave one:
Due to a stable kernel change (4.19.37->4.19.38) that makes me sad,
we got a grave RC for ZFS 0.7.12-2 (testing) which makes it not suitable
for the Buster release:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929929
We have two solutions for this stable RC:
1. just unblock 0.7.13-1 .
2. revert debdiff(0.7.12-2,0.7.12-5), then cherry-pick
the commits[1] that fix the build issue, then go
through t-p-u for 0.7.12-6 .
Patching the kernel is impossible because kernel maintainers
refused to do that. So that's an invalid solution.
> Be aware that requests like this one are draining energy from the
> release team. It isn't nice to turn a maintainer down on a request,
> repeating the process is worse. Your changes are huge (your explanation
> is appreciated), we get several unblock requests per day and we have a
> freeze policy in place to manage it. Please don't push your pet project
> so hard if it doesn't meet the policy that you are driving the
> volunteers in the release team away. Thanks for also considering our time.
Sorry for that. My motivation is just that 0.7.13-1 is really
expected to reduce the number of problems compared to 0.7.12-2...
Please make a choice between the two proposed solution above.
If release team doesn't trust every line of code, please just
choose 2. I'll never argue about ZFS unblock again for Buster.
[1] Patch:
https://github.com/zfsonlinux/zfs/commit/e22bfd814960295029ca41c8e116e8d516d3e730
Reply to: