Re: 02/02: gnu: linux-libre: Update to 6.9.

[Efraim Flashner <efraim@flashner.co.il>]

[-- Attachment #1: Type: text/plain, Size: 3086 bytes --]

On Wed, Jun 05, 2024 at 09:00:59PM +0000, Kaelyn wrote:
> Hi,
> 
> On Wednesday, June 5th, 2024 at 11:27 AM, Leo Famulari <leo@famulari.name> wrote:
> 
> > 
> > 
> > On Tue, Jun 04, 2024 at 08:41:47AM +0200, Ludovic Courtès wrote:
> > 
> > > It seems that it broke ‘x86-energy-perf-policy’ and ‘zfs-auto-snapshot’:
> > > 
> > > https://ci.guix.gnu.org/eval/1374635?status=newly-failed
> > 
> > 
> > Aha, a new feature in the CI web interface! Wonderful!
> > 
> > The failure of 'x86-energy-perf-policy' appears to be spurious, caused by
> > the builder running out of memory, which happens often on our i686-linux
> > build environment on ci.guix.gnu.org:
> > 
> > ------
> > xz: (stdin): Cannot allocate memory
> > ------
> > https://ci.guix.gnu.org/build/4794093/details
> > 
> > But the failure of 'zfs-auto-snapshot' is real:
> > 
> > ------
> > checking whether bdev_open_by_path() exists... configure: error:
> > *** None of the expected "blkdev_get_by_path()" interfaces were detected.
> > *** This may be because your kernel version is newer than what is
> > *** supported, or you are using a patched custom kernel with
> > *** incompatible modifications.
> > ***
> > *** ZFS Version: zfs-2.2.3-1
> > *** Compatible Kernels: 3.10 - 6.7
> > 
> > error: in phase 'really-configure': uncaught exception:
> > ------
> > 
> > As menitoned in the error message, this package does not support kernels
> > newer than 6.7. And, development appears to be suspended:
> 
> As a ZFS user, I'd like to offer a bit of clarification: zfs-auto-snapshot doesn't depend on any specific kernel versions, but zfs itself does. For example, zfs 2.2.3 supports up to kernel 6.7, and zfs 2.2.4 supports up to kernel 6.8 (ref: https://github.com/openzfs/zfs/releases). I suspect zfs is failing to build with the default kernel as a dependency of zfs-auto-snapshot.
> 
> Cheers,
> Kaelyn
> 
> P.S. If there is interest, I can see about submitting my custom ZFS packages. I split it so that the "zfs" package is just the user-space tools without the kernel module (which should also make it substitutable since it no longer includes binaries with combined GPL and CDDL code), and created a function "make-zfs-for-kernel" that generates a package containing just the kernel modules, built for the given kernel package. This also addresses the issue of the zfs package depending on a kernel package that may or may not be needed (and which it may not compile against), and the user having to create a custom non-substitutable version--including all of the user-space tools--for the specific kernel they are running.

I imagine this would be a nice change for people who use ZFS.
Considering how often a kernel version update brakes the zfs package I
could also see switching the 'default' zfs package to use the default
lts kernel.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]