You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given some package p which is a split package for building (at least) q
Given p (and therefore q) has an AUR dependency x
Given the user invokes aurget -Sy --deps q
What happens
Aurget attempts to download the PKGBUILD for q to resolve dependencies
This PKGBUILD does not exist (only the PKGBUILD for p does)
Aurget considers a missing PKGBUILD as "no dependencies" and continues with the build
The build will fail when makepkg can't satisfy x (because it's in the AUR)
What should happen
Aurget should download p's PKGBUILD and use it to resolve dependencies
Aurget should find x and add it as a dependency target
Building should succeed
Proposed fixes
I wonder if not finding the PKGBUILD should blow up
We probably need to hit the AUR API to know that we need p's PKGBUILD to resolve dependencies for q
Workaround
In general, manually resolve the dependencies:
aurget -Sy --deps --asdep x
aurget -Sy --deps q
Note that
aurget -Sy --deps x q
Will also work, but x will be installed explicitly and therefore would not be removed automatically with pacman -Rsn q, or be show in pacman -Qdt output when/if q were uninstalled.
The text was updated successfully, but these errors were encountered:
(See #39 for example case)
Scenario
p
which is a split package for building (at least)q
p
(and thereforeq
) has an AUR dependencyx
aurget -Sy --deps q
What happens
PKGBUILD
forq
to resolve dependenciesPKGBUILD
does not exist (only thePKGBUILD
forp
does)PKGBUILD
as "no dependencies" and continues with the buildmakepkg
can't satisfyx
(because it's in the AUR)What should happen
p
'sPKGBUILD
and use it to resolve dependenciesx
and add it as a dependency targetProposed fixes
PKGBUILD
should blow upp
'sPKGBUILD
to resolve dependencies forq
Workaround
In general, manually resolve the dependencies:
Note that
Will also work, but
x
will be installed explicitly and therefore would not be removed automatically withpacman -Rsn q
, or be show inpacman -Qdt
output when/ifq
were uninstalled.The text was updated successfully, but these errors were encountered: