Package Details: zfs-utils 2.2.7-1

Git Clone URL: https://aur.archlinux.org/zfs-utils.git (read-only, click to copy)
Package Base: zfs-utils
Description: Userspace utilities for the Zettabyte File System.
Upstream URL: https://zfsonlinux.org/
Licenses: CDDL
Submitter: eschwartz
Maintainer: kstolp
Last Packager: kstolp
Votes: 69
Popularity: 3.66
First Submitted: 2018-10-28 22:49 (UTC)
Last Updated: 2024-12-13 11:25 (UTC)

Pinned Comments

eschwartz commented on 2020-12-27 22:43 (UTC)

@Win8Error,

This package doesn't support people who have failed to read the wiki page https://wiki.archlinux.org/index.php/Makepkg, or cannot interpret error messages.

eschwartz commented on 2019-10-16 03:49 (UTC)

aarch64 is not an officially supported architecture for this PKGBUILD, since I don't exactly test it on such architectures. It failing to work is therefore not very surprising.

I guess you can do any necessary followup in that upstream bug report, hopefully upstream can get it into a state of "working out of the box" so that makepkg --ignorearch works. But I'm not investing any of my own time in this...

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 Next › Last »

dlp commented on 2020-06-19 18:59 (UTC)

Can the arch be changed to any to match the zfs-dkms package?

eschwartz commented on 2020-05-27 17:39 (UTC)

I independently figured that out and filed https://bugs.archlinux.org/task/66762 as I'm not sure whether systemd should be in clean chroot builds, but it used to be and that assumption has actually changed now.

It has ramifications for more than just the availability of the systemctl utility -- it also affects the passwd database.

So systemd needs to either be added as a makedepends, or re-added to base-devel. Since you were the one who added systemd to base-devel a few years ago, maybe you have an opinion or two to share on that bug report? :)

seblu commented on 2020-05-27 17:29 (UTC) (edited on 2020-05-27 17:30 (UTC) by seblu)

I have the same issue than @PedroHLC when building with extra-x86_64-build on my aurbot builder.

There is some hints in the build log:

checking for systemd support... no

Calling systemctl in the PKGBUILD produce the following error:

==> Starting build()...
/startdir/PKGBUILD: line 38: systemctl: command not found
==> ERROR: A failure occurred in build().

systemctl is packaged inside systemd. So you need to add systemd as a makedepends.

What about moving it on community? ;)

PedroHLC commented on 2020-05-22 00:07 (UTC)

@eschwartz Sorry, you were right, compared two BUILDINFO, at some point my containers removed systemd and stayed just with systemd-libs.

eschwartz commented on 2020-05-21 23:59 (UTC)

Well, if systemctl --version succeeds in your container environment I'm at a loss for words as to how zfs's --enable-systemd=check default could incorrectly analyze systemd as not being there:

https://github.com/openzfs/zfs/blob/fb822260b19921985a5312f7306b0ee0e30eb3b0/config/user-systemd.m4#L28-L31

As always, I have built this package and zfs-dkms using extra-x86_64-build, entered the build container using arch-nspawn, installed linux/linux-headers, and ensured that dkms install correctly builds the modules for the default kernel. Then I uploaded the resulting packages to https://wiki.archlinux.org/index.php/Unofficial_user_repositories#eschwartz

So I'm quite positive this can correctly work. You cannot argue with experimental results, and I have experimented, it did correctly work, and the results are freely available for download, right there; you may inspect the .BUILDINFO from those package tarballs and see how I've built it, with what installed packages, what makepkg.conf options, and what $PWD, try to reproduce it using makerepropkg (part of devtools) and so on.

If I had a better understanding of how your build differs from my build, then perhaps we could determine why your build failed with such disastrous results and ended up missing parts.

PedroHLC commented on 2020-05-21 23:40 (UTC) 

systemd 245 (245.5-2-arch)
+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid

I actually build from a clean systemd-nspawn container with just base-devel installed. Pretty much how I've been building ZFS since 2018 on my repository...

eschwartz commented on 2020-05-21 23:23 (UTC)

It should autodetect systemd support and install both.

It does, in fact, autodetect systemd support and install both. On my machine.

Does systemctl --version not succeed in your environment? It is part of base-devel, so this really should work...

PedroHLC commented on 2020-05-21 23:18 (UTC)

@eschwartz Not sure if it's something that changed with 0.8.4, but building this (without the rm *modules-load.d line) doesn't install a zfs-mount.service anymore...

PedroHLC commented on 2020-05-21 21:18 (UTC)

With the latest PKGBUILD

rm: cannot remove '/home/main-builder/pkgwork/pkg/zfs-utils/usr/lib/modules-load.d': No such file or directory

RandomChars commented on 2020-05-21 10:50 (UTC)

this version no longer compiles, please update the package

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 Next › Last »