Package Details: zfs-linux-lts 2.2.3_6.6.22.1-1

Git Clone URL: https://aur.archlinux.org/zfs-linux-lts.git (read-only, click to copy)
Package Base: zfs-linux-lts
Description: Kernel modules for the Zettabyte File System.
Upstream URL: https://openzfs.org/
Licenses: CDDL
Groups: archzfs-linux-lts
Conflicts: spl-dkms, spl-dkms-git, spl-linux-lts, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-linux-lts-git, zfs-linux-lts-rc
Provides: spl, zfs
Replaces: spl-linux-lts
Submitter: demizer
Maintainer: minextu (archzfs-bot)
Last Packager: archzfs-bot
Votes: 77
Popularity: 0.92
First Submitted: 2016-04-24 19:05 (UTC)
Last Updated: 2024-03-18 15:11 (UTC)

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

gromit commented on 2024-03-18 17:36 (UTC)

@minextu, fix the script then please:

Automated PKGBUILD updates are used at your own risk and any malfunctioning accounts and their packages may be removed

Taken from https://wiki.archlinux.org/title/AUR_submission_guidelines#Maintaining_packages

I am also willing to contribute if you point me somewhere

minextu commented on 2024-03-18 17:10 (UTC)

@gromit: That is a limitation by the script generating this package. It's not ideal, but since the patches aren't actually applied anywhere, it doesn't make a difference to the built package

gromit commented on 2024-03-18 16:42 (UTC) (edited on 2024-03-18 16:42 (UTC) by gromit)

Again, the latest commit (3539a56fd4cf) introduces some weird patch file not needed to build the package for the lts kernel. This problem was already reported in https://aur.archlinux.org/packages/zfs-linux-lts#comment-953926 for the previous kernel iteration..

gromit commented on 2024-01-29 07:49 (UTC)

Why does 5da354537fd8 introduce some huge patch for kernel 6.7 while that is presumably not needed for the LTS version?

hoban commented on 2023-12-18 18:24 (UTC)

It looks like the CI build issues relate to the build infrastructure, rather than the package. I was able to build/install/run it locally without any issue:

❯ git clone https://aur.archlinux.org/zfs-linux-lts.git

❯ vim PKGBUILD
# <interactive output omitted, see diff below>

❯ git --no-pager diff
diff --git a/PKGBUILD b/PKGBUILD
index aad1ea7..71fdbb3 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -18,9 +18,9 @@
 pkgbase="zfs-linux-lts"
 pkgname=("zfs-linux-lts" "zfs-linux-lts-headers")
 _zfsver="2.2.2"
-_kernelver="6.1.66-1"
-_kernelver_full="6.1.66-1"
-_extramodules="6.1.66-1-lts"
+_kernelver="6.1.68-1"
+_kernelver_full="6.1.68-1"
+_extramodules="6.1.68-1-lts"

 pkgver="${_zfsver}_$(echo ${_kernelver} | sed s/-/./g)"
 pkgrel=1

❯ makepkg -scir
# <package building output omitted>

❯ ls
PKGBUILD  zfs-2.2.2.tar.gz  zfs.install  zfs-linux-lts-2.2.2_6.1.68.1-1-x86_64.pkg.tar.zst  zfs-linux-lts-headers-2.2.2_6.1.68.1-1-x86_64.pkg.tar.zst

❯ pacman -Q | grep 6.1.68
linux-lts 6.1.68-1
linux-lts-headers 6.1.68-1
zfs-linux-lts 2.2.2_6.1.68.1-1
zfs-linux-lts-headers 2.2.2_6.1.68.1-1

❯ uname -r
6.1.68-1-lts
# <the above was post-reboot>

theking2 commented on 2023-09-16 08:43 (UTC)

build error ERROR: Could not push packages to remote testing repo!

LazyGamble commented on 2023-08-02 07:58 (UTC)

"No space left on device" https://ci.archzfs.com/#/builders/6/builds/2189

Who is currently maintaining the buildbot?

manchmalscott commented on 2023-08-01 02:56 (UTC)

At this point, I've decided to set up my own instance of the build server from https://github.com/archzfs/archzfs-ci/ (which has been it's own nightmare, the Dockerfiles required some heavy modification to build). I've lost trust in the maintainers of this package.

Shubby commented on 2023-08-01 02:36 (UTC)

Something isn't right with the CI build, the "current" build has been running for 5+ days and looks like it's in some weird failed state.

Erroneous commented on 2023-07-05 20:21 (UTC)

@Carlosgrr Building this package works best when you can install the dependencies and not the have the package installed itself. To do this, I recommend either building the package on another Arch installation or building inside of a chroot.

I use the aurutils AUR helper which can build packages inside a chroot environment. I'm not familiar with yay, but if it has chroot capabilities I would look into that.