Package Details: zfs-linux 2.2.7_6.12.8.arch1.1-1

Git Clone URL: https://aur.archlinux.org/zfs-linux.git (read-only, click to copy)
Package Base: zfs-linux
Description: Kernel modules for the Zettabyte File System.
Upstream URL: https://openzfs.org/
Keywords: kernel linux openzfs zfs
Licenses: CDDL
Groups: archzfs-linux
Conflicts: spl-dkms, spl-dkms-git, spl-linux, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-linux-git, zfs-linux-rc
Provides: spl, zfs
Replaces: spl-linux
Submitter: demizer
Maintainer: lightdot
Last Packager: lightdot
Votes: 273
Popularity: 1.76
First Submitted: 2016-04-21 08:45 (UTC)
Last Updated: 2025-01-04 04:03 (UTC)

Required by (19)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 79 Next › Last »

justinkb commented on 2014-04-19 00:06 (UTC)

There are many AUR packages which work fine just pulling the latest stuff from git and doing some pkgver magic. Try looking at sickbeard-git or xbmc-git packages on AUR. Manually creating these huge patches regularly seems pretty much insane.

<deleted-account> commented on 2014-04-18 21:57 (UTC)

The PKGBUILD documentation (https://www.archlinux.org/pacman/PKGBUILD.5.html) says you can specify a commit in the fragment for git sources like so: source=('project_name::git+http://project_url#commit=4fd762f8ad') It works just fine on all of my git PKGBUILDs.

demizer commented on 2014-04-18 21:17 (UTC)

Just a little update, I have been trying to work with the arch linux packaging tools to allow me to precisely control how the git sources are pulled and it works, but there is no fine grain control beyond pinning branches it seems. That and the devtools scripts don't support the pkgver() function adequately (yet), so I am going to manually create git patches like we have been doing. I have been fighting the tools for the last two days and are basically giving up. I don't have time to work on the upstream tools, so I am going to work around them. Jesus A.

justinkb commented on 2014-04-16 22:24 (UTC)

Pretty excited for those git packages, take your time to ensure all is well :-)

demizer commented on 2014-04-16 21:29 (UTC)

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/grub Interesting. This package uses git, but it pulls from a specific tag. We will be using the master branch, but not a specific tag. Also, because we are in AUR, I think it would be better to follow the *-git naming scheme to signify that the package uses the git master branch. The grub official package is maintained by the arch devs, so that doesn't matter as much, but people pulling from AUR should know where the sources are coming from. I will also make zfs-lts packages that use the official ZOL release.

graysky commented on 2014-04-16 21:07 (UTC)

Stupid question perhaps but why rebrand the packages with the -git suffix? Grub in the official repo for example is a git snapshot I believe.

demizer commented on 2014-04-16 08:43 (UTC)

The PKGBUILDS I am working on as we speak use hardcoded variables generated by the archzfs build scripts instead of the bash regex clusterfuck that is in the current PKGBUILDS. Bash regex is horrible and hard to read. It makes me wish for python. I am hoping I will have the zfs git packages up by tomorrow. I have had to modify the PKGBUILDS and build scripts heavily.

<deleted-account> commented on 2014-04-16 08:38 (UTC)

The current PKGBUILD needs some love in the part relating to 'If LINUX_VERSION does not have a minor version, we need to add "0"', since when I manually edited the LINUX_VERSION_X64 to be "3.14.1-1", the MOD_BASENAME became "3.14.1.0-1" and build failed. Not a big deal for tinkers to manually workaround that issue, of course. (I did not look further into the string manipulation since it is not my field of experience.)

demizer commented on 2014-04-16 03:23 (UTC)

Hi everyone, I am working on supporting zfs-git and zfs-lts packages. It will be a few days before I can get everything uploaded. I am integrating kerberizer's changes and will be looking at the systemd files provided upstream to see if they will work for us. Thanks!

kerberizer commented on 2014-04-16 01:56 (UTC)

As I emphasized when publishing them, those PKGBUILDs are not intended for general use, but rather as a potential point for reference. Sticking to demizer's well-proven, stable and supported packages and PKGBUILDs is the sensible thing to do, unless you want to experiment and then also understand well the risks involved. Now, for those that really want to tinker with my PKGBUILDs, here's a critical thing which I only hinted earlier: because these PKGBUILDs install the systemd unit files provided by ZoL, you need to `systemctl disable zfs.service` and then, after the packages are installed, to `systemctl enable zfs.target`. The latter is crucial for your datasets to be mounted as expected. There are likely more elegant ways to achieve this, but I haven't yet had the time to give it more thought (any ideas are welcome, of course: probably something connected with the systemd presets). P.S. The reason why it's not (apparently) necessary to change the version for the {spl,zfs}-utils-git PKGBUILDs is because they don't have a dependency on the Linux kernel. The real problem here, however, is that each of the PKGBUILDs in their own chain of dependencies (spl-utils -> spl-modules -> zfs-utils -> zfs-modules) doesn't check the version of the package it depends upon. That's exactly one of the other problems with my PKGBUILDs that I talked about (and the reason are the Git type versions, for which there's likely an easy and elegant solution, but at least I need some time to think about it; again, ideas are very welcome).