Search Criteria
Package Details: zfs-linux-headers 0.8.2_5.3.7.arch1.1-1
| Git Clone URL: | https://aur.archlinux.org/zfs-linux.git (read-only) |
|---|---|
| Package Base: | zfs-linux |
| Description: | Kernel headers for the Zettabyte File System. |
| Upstream URL: | https://zfsonlinux.org/ |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | demizer |
| Maintainer: | minextu (archzfs-bot) |
| Last Packager: | archzfs-bot |
| Votes: | 218 |
| Popularity: | 2.322661 |
| First Submitted: | 2016-04-21 08:45 |
| Last Updated: | 2019-10-18 22:13 |
Dependencies (4)
- kmod (kmod-git)
- zfs-utils=0.8.2 (zfs-utils-head-git, zfs-utils-git)
- linux=5.3.7.arch1-1 (linux-xanmod-git, linux-galliumos, linux-ryzen-amd-staging-drm-next-git, linux-ryzen-git, linux-surfacepro3-git, linux-aarch64-rock64-bin, linux-ec2, linux-pf-lts, linux-ck-reiser4, linux-linode, linux-git, linux-asus-aura, linux-bootsplash, linux-lts316, linux-clear-bin, linux-xanmod, linux-aarch64-raspberrypi-bin, linux-amd-raven, linux-slim, linux-lts414, linux-lts49, linux-lts44)
- linux-headers=5.3.7.arch1-1 (linux-lts-ck-headers, linux-xanmod-git-headers, linux-galliumos-headers, linux-ryzen-amd-staging-drm-next-git-headers, linux-ryzen-git-headers, linux-surfacepro3-git-headers, linux-aarch64-rock64-bin-headers, linux-ec2-headers, linux-pf-lts-headers, linux-ck-reiser4-headers, linux-mainline-bcachefs-lts-headers, linux-git-headers, linux-asus-aura-headers, kernel-uek-devel, linux-bootsplash-headers, linux-lts316-headers, linux-clear-headers-bin, linux-pds-headers, linux-bcachefs-git-headers, linux-xanmod-headers, linux-ck-headers, linux-gc-headers, linux-mainline-bcachefs-headers, linux-amd-raven-headers, linux-slim-headers, linux-lts414-headers, linux-lts49-headers, linux-lts44-headers) (make)
Latest Comments
1 2 3 4 5 6 ... Next › Last »
Hetsh commented on 2019-10-19 08:21
Root on encrypted ZFS can be decrypted during boot when adding "zfs load-key -a" around line 54 in the mkinitcpio hook "/usr/lib/initcpio/hooks/zfs". @minextu maybe consider as permanent patch?
minextu commented on 2019-09-21 23:09
@dawnofman It didn't break anything but it's fixed now, thanks!
dawnofman commented on 2019-08-18 23:49
dunno whether this is relevant or not but: --libexecdir=/usr/lib/zfs-${zfsver} should be: --libexecdir=/usr/lib/zfs-${_zfsver} it is not the same variable; it is being built as: --libexecdir='/usr/lib/zfs-'
chungy commented on 2019-07-24 06:41
It's likely to be part of 0.8.2, but could e5db31349484e5e859c7a942eb15b98d68ce5b4d be cherry-picked to be included in this package? It restores SIMD compatibility on the latest 4.14.x/4.19.x/5.x kernels. Debian is already including this patch in their 0.8.1 package :)
minextu commented on 2019-05-26 15:05
@andybz zfs-utils and zfs-dkms have a different maintainer and I don't have access to update.
You can use https://github.com/archzfs/zfs-dkms and https://github.com/archzfs/zfs-utils in the meantime or update using the archzfs repo (http://archzfs.com)
andybz commented on 2019-05-26 07:06
I moved from zfs-dkms to this package to get ZFS 0.8.0, but I had trouble with no package actually providing zfs-utils=0.8.0.
I ended up just bumping the pkgver on the zfs-utils package to 0.8.0 and I'm OK again but I haven't worked out yet whether there's a packaging issue here or what.
ShaunPC commented on 2019-05-05 00:18
The reason this happens with both the archzfs repo and the AUR package is because the non-dkms package is compiled against a specific version of the Linux kernel. When the Arch kenel gets updated, this package falls out of date. This is only ever the case for 1-2 days. As I understand it there is a certain amount of automation involved. Just be patient and wait for a day before trying to update again. No manual process is needed.
Ruli commented on 2019-05-05 00:17
Got it. Thanks again! It's been a while since I encountered this problem, I've somehow forgotten about it... sorry for the hassle!
dmp1ce commented on 2019-05-05 00:08
I think what described is also the case for archzfs repository. I also use archzfs and I get the same error often. I just wait until the packages get updated with working dependencies. Flagging the package as out-of-date might help the maintainers become aware of the issue.
Ruli commented on 2019-05-05 00:04
Hi @dmp1ce, thanks for your reply! Sorry, I should have clarified before that I'm using the archzfs repo. I remember in the past that I would have to manually update the dependencies, but ever since using the archzfs repo I didn't have to do this anymore. Anyway, I will do a manual update first then. Thank you once again!