From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 02/02: gnu: linux-libre: Update to 6.9.
Date: Wed, 5 Jun 2024 14:27:37 -0400 [thread overview]
Message-ID: <ZmCuGcBb4iMen-Zz@jasmine.lan> (raw)
In-Reply-To: <87r0dd8b10.fsf@gnu.org>
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:
https://github.com/zfsonlinux/zfs-auto-snapshot/issues/117
next prev parent reply other threads:[~2024-06-05 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171746516380.7429.1293440427932042426@vcs2.savannah.gnu.org>
[not found] ` <20240604013924.59F27C1F9EA@vcs2.savannah.gnu.org>
2024-06-04 6:41 ` 02/02: gnu: linux-libre: Update to 6.9 Ludovic Courtès
2024-06-05 18:27 ` Leo Famulari [this message]
2024-06-05 21:00 ` Kaelyn
2024-06-09 9:43 ` Efraim Flashner
2024-06-10 1:19 ` Leo Famulari
2024-06-10 9:26 ` Andreas Enge
2024-06-10 17:26 ` Kaelyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZmCuGcBb4iMen-Zz@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).