You are not logged in.
When I want to upgrade my system I get this error message:
could not satisfy dependencies:
installing lib32-llvm-libs (10.0.0-1) breaks dependency 'lib32-llvm-libs<9.1' required by lib32-mesa-aco-git
installing llvm-libs (10.0.0-1) breaks dependency 'llvm-libs<9.1' required by mesa-aco-git
When I block the upgrade of lib32-llvm-libs and llvm-libs (hoping that it would upgrade the aco-compilers) I get this error message.
could not satisfy dependencies:
unable to satisfy dependency 'llvm-libs>=10.0.0' required by mesa-aco-git
unable to satisfy dependency 'lib32-llvm-libs>=10.0.0' required by lib32-mesa-aco-git
unable to satisfy dependency 'llvm-libs>=10.0.0' required by mesa-aco-git
unable to satisfy dependency 'llvm-libs>=10.0.0' required by mesa-aco-git
In brief, the current version of aco demands the older version of llvm-libs which blocks the upgrade of llvm-libs but the new version of aco demands llvm-libs to be upgraded. Pacman can not solve these dependencies.
How do I solve this? Can I force the upgrade via the terminal?
Removing the aco-compilers is not an easy option given that then hundreds of other programs get removed too.
Last edited by PeterJansen (2020-04-22 10:27:56)
Offline
You got some options that will work :
Best one
build mesa-aco-git in a clean chroot [1]
update mesa-aco-git
pacman -Syu
2nd best
revert from mesa-aco-git to stock mesa
pacman -Syu
build mesa-aco-git
switch from mesa to mesa-aco-git
EDIT : for lib32-mesa-aco-git you'll need to do the same.[end-of-edit]
Whichever you choose, make a note that you'll have to repeat this about twice a year, maybe more often
[1] https://wiki.archlinux.org/index.php/De … ean_chroot
If you prefer a different approach then those listed , check https://aur.archlinux.org/packages/clean-chroot-manager
Last edited by Lone_Wolf (2020-04-22 10:43:12)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Mod note: 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
You got some options that will work :
Best one
build mesa-aco-git in a clean chroot [1]
update mesa-aco-git
pacman -Syu2nd best
revert from mesa-aco-git to stock mesa
pacman -Syu
build mesa-aco-git
switch from mesa to mesa-aco-gitEDIT : for lib32-mesa-aco-git you'll need to do the same.[end-of-edit]
Whichever you choose, make a note that you'll have to repeat this about twice a year, maybe more often
[1] https://wiki.archlinux.org/index.php/De … ean_chroot
If you prefer a different approach then those listed , check https://aur.archlinux.org/packages/clean-chroot-manager
Thanks for the answer. Would anything be wrong with force-removing (-Rdd) the AUR-package (many packages would get co-removed otherwise), updating the system and then reinstalling the AUR-package?
Last edited by PeterJansen (2020-04-23 19:12:58)
Offline
Using -Rdd means your system is not in the state pacman thinks it is.
If something goes wrong[1] in the time between the force removal and the rebuild / re-install that will cause issues.
Even if nothing goes wrong, the new version might have different depends / provides then the old one.
That would result in an inconsistent system state that will cause hard to troubleshoot problems at some future point.
Whether your skills and understanding how things work on archlinux are good enough to solve such issues is your decision .
[1] a few possibilities :
- power outage
- rebuild fails due to upstream changes
- powering off / rebooting before system state is consistent again
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
You got some options that will work :
Best one
build mesa-aco-git in a clean chroot [1]
update mesa-aco-git
pacman -Syu
Would you mind explaining why this option is the best one?
Offline
The chroot is independent of the host system's state so whatever packages the host uses are ignored inside the chroot allowing you to build the packages with the updated toolchain without it being installed on the host.
You can then add the generated packages to a local repository and perform a full system upgrade satisfying all the package dependencies. This avoids switching to mesa then back to mesa-aco-git or having pacman ignore dependencies.
Offline