Hi, I got the following (I updated the servers with the ‘garuda-update -a’ command):
installing libtiff (4.7.0-1) breaks dependency 'libtiff=4.6.0' required by lib32-libtiff
A few days ago I had a problem with paru. I tried to compile the package (‘makepkg -si’): I got an error message, but I didn’t remove the downloaded libraries to compile the package (I’m now using paru-git).
How can I solve it?
Its fixed,
Try paru again 
, maybe the git is not fixed?
Chaotic-aur is fine
4 chaotic-aur/paru-git 2.0.3.r10.g79414b4-1 [3.41 MiB 8.38 MiB]
Feature packed AUR helper
3 chaotic-aur/pacui 1.14-1.1 [38.17 KiB 211.34 KiB]
Bash script providing advanced Pacman and Yay/Pikaur/Aurman/Pakku/Trizen/Paru/Pacaur/Pamac-cli functionality in a simple UI
2 aur/paru 2.0.3-1 [+955 ~33.47] [Veraltet: 2024-09-14] [Installiert: 2.0.3-1.2]
Feature packed AUR helper
1 chaotic-aur/paru 2.0.3-1.2 [0 B 8.26 MiB] [Installiert]
Feature packed AUR helper
paru aur is outdated
Repeat garuda-update refreshing your mirrors.
Maybe you’re using a bad one.
lib32-libtiff now depends on libtiff=4.7.0, which is exactly the update being done. See:
https://archlinux.org/packages/multilib/x86_64/lib32-libtiff/
So the error should not occur.
Same error here doing a basic garuda-update. Tried refreshing and changing mirrors to a few different ones, nothing changed.
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libjpeg-turbo (3.0.4-1) breaks dependency ‘libjpeg-turbo=3.0.3’ required by lib32-libjpeg-turbo
:: installing libtiff (4.7.0-1) breaks dependency ‘libtiff=4.6.0’ required by lib32-libtiff
These things usually end up fixing themselves but it’s there now.
Yes, just wait, because that’s a different problem.
It is not a mirror problem, it is a dependency problem.
Yes, just wait, because that’s a different problem.
Including multilib worked here. Any specific reason why I wouldn’t want it included?
lib32-libjpeg-turbo is in multilib, of course you need multilib included to get it…?
This all makes me think that the last pacman update included a pacnew file for the pacman.conf, which, if not appropriately merged but overwritten/replaced, may have removed multilib from the pacman.conf in both cases in this thread.
This should be checked and, if necessary, fixed of course.
Ok, just wait.
Off topic: we know that rolling release distributions are best updated often. I could not do the system update because I was abroad and forgot my laptop at home. I came back after five months, updated the mirrors and the system and everything worked fine! Look at the picture.
This all makes me think that the last pacman update included a pacnew file for the pacman.conf, which, if not appropriately merged but overwritten/replaced, may have removed multilib from the pacman.conf in both cases in this thread.
This sounds exactly like it. I did have a pacnew recently for pacman.conf (my fault for not looking into it more carefully, although I might not have noticed the extra # anyway).
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
