I see someone already mentioned that libunwind gets linked by default if present. Unless you want to add it as a package dependency, I think it'd be a good idea to disable it unconditionally by passing --without-libunwind to configure. (I got bitten by this adding this package to an iso.) Thanks for maintaining.
Search Criteria
Package Details: zfs-utils 2.2.6-2
Package Actions
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: | 62 |
Popularity: | 2.50 |
First Submitted: | 2018-10-28 22:49 (UTC) |
Last Updated: | 2024-09-27 08:08 (UTC) |
Dependencies (1)
Required by (37)
- dataleech
- docker-zfs-plugin
- goblocks (optional)
- growlight (optional)
- grub-libzfs
- httm (optional)
- httm-bin (optional)
- httm-git (optional)
- kpmcore-git (optional)
- pivy (make)
- pivy (optional)
- prepare-lastboot
- python-pylibzfs
- systemd-zpool-scrub
- targetd (optional)
- targetd-git (optional)
- zfs-dkms
- zfs-dkms-staging-git
- zfs-linux
- Show 18 more...
Sources (6)
mikezackles commented on 2024-10-01 01:42 (UTC)
fryfrog commented on 2024-09-27 15:46 (UTC)
Thanks a bunch! :)
kstolp commented on 2024-09-27 08:09 (UTC)
The zfsencryptssh hook has been added.
krnlpk commented on 2024-09-25 12:09 (UTC)
I also second adding the zfsencryptssh hook to this package. Both the -git and -rc zfs-utils
packages on AUR include it and it would be awesome for all those of us that are migrating away from the now defunct archzfs repo.
fryfrog commented on 2024-08-23 04:42 (UTC) (edited on 2024-08-23 04:46 (UTC) by fryfrog)
Thanks for considering it, I'm not super familiar w/ initcpio itself nor the early boot process w/ zfs parts for zfs root and zfs root encryption. I'll see what I can learn and figure out, I can see how that hook fixes the small problem I was having w/ the passwd file related to netconf tinyssh, but there's more in there that I don't understand yet.
kstolp commented on 2024-08-23 04:29 (UTC)
@fryfrog, Yes, I don't see any issue with incorporating something like this in. It will be about a week until I can take a proper look into it though. However, if you would like something sooner, I wouldn't be opposed to a PR (via email or comment here).
fryfrog commented on 2024-08-22 05:39 (UTC)
Could something like https://github.com/archzfs/archzfs/blob/master/src/zfs-utils/zfs-utils.initcpio.zfsencryptssh.install be incorporated in this? I just migrated from archzfs/zfs-utils to aur/zfs-utils and this was the only real headache in my zfs encrypted root w/ unlock via ssh setup. This hook creates an /etc/passwd
in the initcpio img which allows it to work. Looks like it does other stuff, but I don't quite grok what.
kstolp commented on 2024-08-08 03:31 (UTC) (edited on 2024-08-08 03:31 (UTC) by kstolp)
@ed209, Right. When building, it will use libunwind if present. (PR #16140) It looks like this is more relevant for people doing development/debugging and probably not for the majority of users of this package. However, if more people chime in and want this, I'll gladly add it.
ed209 commented on 2024-08-07 07:59 (UTC)
I use makepkg
to build packages without a build chroot and 88686213c3 uses libunwind
when it is installed, which is the case on my system. Perhaps add libunwind
as a dependency for zfs-utils
?
kstolp commented on 2024-08-07 07:24 (UTC)
@ed209, Can you share how you came to that conclusion? I haven't added any direct dependencies to this package.
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...