Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Packages won't update if they have strict version dependency #46
Right now I have 2 outdated AUR packages:
When I update (
Possibly relates to #36
This is a tricky problem for which I don't have a fix yet, because
A workaround would be to use the
I will investigate the problem more carefully in the next days and, maybe, come up with a solution. Thanks for reporting.
added a commit
Dec 30, 2017
Essentially this showcases another limitation of relying on
This is completely insane, and both packages should be installed together. They're a split package, does trizen not notice this and try to rebuild the same package twice?
You don't need either one to build the other, so why are you trying to install them separately?
Also if I were a trizen user, this would teach me better -- I can put up with an AUR helper being unable to install an edge case PKGBUILD, but I cannot tolerate my AUR helper breaking my installation by overriding pacman's dependency parsing.
referenced this issue
Jun 26, 2018
@trizen Is there any news on this?
Looks like this is trizen's fault for not supporting split packages, to which this hack was used, and that can apparently mess with pacman's database.
Since split packages are rare, wouldn't it be better to revert the hack and rather not support split packages at all until they are properly implemented?
I'd prefer not being able to build some packages rather than have my whole package database break, and it would remove trizen from the problematic list on the Arch wiki - https://wiki.archlinux.org/index.php/AUR_helpers#Discontinued_or_problematic