You are not logged in.
Hello there
This morning I wanted to keep my system update (as I do every day)
And this morning I've this :
yaourt -Syua
:: Synchronisation des bases de données de paquets...
core est à jour
extra est à jour
community est à jour
archlinuxfr est à jour
error: failed to prepare transaction (could not satisfy dependencies)
:: Début de la mise à jour complète du système...
résolution des dépendances...
recherche des conflits entre paquets...
erreur: la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: spl-linux: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
:: spl-linux-headers: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
:: zfs-linux: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
:: zfs-linux-headers: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
I think that's because ZFS & SPL are not ready to use a new kernel version
I also try with pacman:
sudo pacman -Syu
:: Synchronisation des bases de données de paquets...
core est à jour
extra est à jour
community est à jour
archlinuxfr est à jour
:: Début de la mise à jour complète du système...
résolution des dépendances...
recherche des conflits entre paquets...
erreur: la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: spl-linux: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
:: spl-linux-headers: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
:: zfs-linux: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
:: zfs-linux-headers: installer linux (4.13.4-1) casse la dépendance «linux=4.13.3-1»
Here it is my pacman -Qdt command :
"
sudo pacman -Qdt
asciidoc 8.6.9-3
cabextract 1.6-1
cpio 2.12-3
fontforge 20170731-1
libuser 0.62-1
linux-headers 4.13.3-1
newt-syrup 0.2.0-1
python2-dbus 1.2.4-2
python2-ipy 0.83-1
rarian 0.8.1-6
spl-linux-headers 0.7.2.4.13.3.1-1
urlgrabber 3.10.1-2
xmlto 0.0.28-2"
You can see taht y system is almost up to date
Uname -a :
Linux Ford 4.13.3-1-ARCH #1 SMP PREEMPT Thu Sep 21 20:33:16 CEST 2017 x86_64 GNU/Linux
Can you help me to deal with this issue ?
Should I wait for zfs & spl update ?
Thanks
Offline
Those packages don't come from any official repository, so complain to wherever you installed them from
Offline
Probably the zfs packages are tied to a specified kernel version triplet. The kernel was updated the third-party packages not. Hence the problem. Solution: wait for the zfs packages to be updated.
Offline
Those packages don't come from any official repository, so complain to wherever you installed them from
Probably the zfs packages are tied to a specified kernel version triplet. The kernel was updated the third-party packages not. Hence the problem. Solution: wait for the zfs packages to be updated.
^ This.
This has also been clearly stated on the Arch Wiki in a big red box
Warning: Unless you use the dkms versions of these packages, the ZFS and SPL kernel modules are tied to a specific kernel version. It would not be possible to apply any kernel updates until updated packages are uploaded to AUR or the archzfs repository.
Offline
Hello all
Thanks a lot for that answer. I just have a last question. Do you think that I can blacklist those package to do an upgrade of my system ? I mean, It seems that I need to continue to update my system even if I can't do it for ZFS an spl package.
Is it a good solution ? I don't think so beacause, I don't know if ZFS will continue to work if I update the system. What do you think ?
Thanks
Offline
I think you're making life unnecessarilly difficult for yourself trying to use an out-of-tree filesystem that requires you to know what you're doing, when you clearly don't. Blacklisting packages is rarely a good idea. If the zfs patches don't work for bleeding-edge kernels, see if there's an LTS patchset.
Mod note: not a Pacman issue, moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
That being said, the kernel packages are basically the one thing it is almost completely safe to blacklist.
I say almost, because you won't have much luck running older kernels simply because they don't support features newer software requires; good luck running some ancient 2.x kernel or something. But it would take a while for that to happen, and blacklisting for a few days or even a month or two is perfectly okay.
I do agree that one should not be using experimental out-of-tree kernel modules for their root filesystem when errors like this cause confusion.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline