-
-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
paru fails at dependency / conflict resolution of split packages depending on different package bases #1173
Comments
A similar thing also happens with zfs-dkms and zfs-utils. Paru attempts to upgrade each of them one at a time instead of rebuilding both and installing them at the same time. Because they depend on specific versions of each other, the install fails. I have to use |
The |
I just tried to build it and it worked. I'm not sure what has changed since this issue was opened, if the pkgbuilds are laid out differently now or something. Or was installing it always fine but upgrading is where the issues are? Paru has had some bug fixes to the dep resolver so that could be it too. Though normally with stuff like this you can just build in a chroot and sidestep the whole thing. |
Installing is fine but upgrading fails. Using
|
@drrlvn do you have cachyOS or other sources or do you build from AUR ?? |
I don’t have cachyOS, I only build |
@drrlvn did it work now ?? Maybe just the version in the AUR repo was not up-to-date |
I've tested this. This does not work because paru will install aur packages one at a time. --batchinstall doesn't fix it because it uses a naive check and flushes the install queue as soon as it detects a package it can't install. Instead of looking ahead and realising both could be installed together. This is something that will probably we fixed an overall of the dep solving so there's no immediate fix. However if you're using local repos and chroots it works fine. |
Affected Version
Description
I'm trying to get paru installing a pretty huge split package consisting of two AUR pkgbase repos with several split packages.
PKGBASE 1 :
aur/flutter
PKGBASE 2 :
aur/flutter-artifacts-google-bin
The package is constructed in the following way :
aur/flutter
base contains all components built from sourceaur/flutter-artifacts-google-bin
base contains a PKGBUILD fetching required artifacts for Flutter from Google CI - this package provides all artifacts required by split sub packages of the flutter base as split packages. E.g. :flutter-engine-android
required byflutter-traget-android
. Whereas the engine is provided by another pkg base than the target package.flutter-target-android=3.19.5
depends onflutter-engine-android=3.19.5
. I guess it's obvious that makes sense.conflicts
section enforcing to first unsinstall all previous versions before trying to upgrade to the next version.flutter-common
in the new version - which conflicts with all other installed packages of the group.I understand that this is a pretty complex case of dependency resolution. But the AUR upstream definitely provides all required dependency and conflict declarations mandatory in order to perform an upgrade of the package. Still paru doesn't reach at upgrading it.
The easiest way to fix this dependency resolution would be simply allowing the user to confirm the removal proposed by pacman.
The more clean way of fixing this behavior would be making paru first build and package all split packages and then installing all of them at once.
Output
paru build / install output
The text was updated successfully, but these errors were encountered: