I'm new on manjaro (arch based linux). So I may be wrong.
But to me, it looks like that "provides zfs" in zfs-dkms doesn't work.
I have zfs running, so I'm sure that zfs-dkms works as expected.
But when I try to install i.e. zfs-auto-snapshot-git, which depends on zfs it doesn't recognise "zfs" and try's to install linux...-zfs.
Then when I remove depends('zfs') or change is to depends('zfs-dkms') in PKGBUILD of zfs-auto-snapshot-git everything went fine.
When I do a "pacman -R zfs" I get "not found" too.
Search Criteria
Package Details: zfs-dkms 2.3.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
---|---|
Package Base: | zfs-dkms |
Description: | Kernel modules for the Zettabyte File System. |
Upstream URL: | https://zfsonlinux.org/ |
Licenses: | CDDL |
Provides: | SPL-MODULE, zfs, ZFS-MODULE |
Submitter: | isiachi |
Maintainer: | kstolp |
Last Packager: | kstolp |
Votes: | 186 |
Popularity: | 1.55 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-03-11 07:23 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 53 54 55 56 57 58 59 60 61 62 63 64 Next › Last »
fow0ryl commented on 2017-03-10 19:23 (UTC)
isiachi commented on 2017-02-20 20:47 (UTC)
@thunderforce
Thanks for the help!
I have already explained that is a aur helper related problem in this comment:
isiachi commented on 2016-09-20 19:45
thunderforce commented on 2017-02-20 07:55 (UTC)
@RubenKelevra, not sure why you're trying to install this package, but while trying to use VirtualBox and a google search I ended up here. This fixed the DKMS hook for me:
wget https://archive.archlinux.org/packages/l/linux-headers/linux-headers-4.9.8-1-x86_64.pkg.tar.xz
sudo pacman -U linux-headers-4.9.8-1-x86_64.pkg.tar.xz
..
:: Running post-transaction hooks...
(1/2) Install DKMS modules
==> dkms install vboxhost/5.1.14_OSE -k 4.9.8-1-ARCH
(2/2) Arming ConditionNeedsUpdate...
..
hope it's helpful
RubenKelevra commented on 2017-02-14 02:58 (UTC)
Still issues with a simple update because this PKGBUILD depends on a given version:
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: zfs-dkms: installing spl-dkms (0.6.5.9-1) breaks dependency 'spl-dkms=0.6.5.8'
RubenKelevra commented on 2017-02-12 14:55 (UTC)
Friday is now two days gone, so where's the update, mate?
RubenKelevra commented on 2017-02-08 22:33 (UTC)
Still no update? Why does it take 5 days for a simple subversion update, which only needs a checksum-push?
isiachi commented on 2017-02-07 00:23 (UTC)
There will be an update in friday.
ShaunPC commented on 2017-02-06 14:57 (UTC)
@scott32 zfs-dkms has not implemented dependency hooks or has implemented them incorrectly as dkms itself has the capability yet zfs will try to build before spl.
scott32 commented on 2017-02-06 13:46 (UTC)
@ShaunPC: "On investigation it appears that dkms already has a module dependency check implemented" ... when I look into /usr/share/libalpm/hooks/70-dkms-install.hook and /usr/lib/dkms/alpm-hook, I don't see any dependency, or module build ordering checks there. What did you mean?
fermatslast commented on 2017-02-06 02:37 (UTC)
To use with a 4.9 kernel, edit the PKGBUILD for both spl-dkms and zfs-dkms, change pkgver to 0.6.5.9
Pinned Comments
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)