paru icon indicating copy to clipboard operation
paru copied to clipboard

Paru does not offer to install missing dependencies on AUR package upgrade

Open Porkepix opened this issue 1 year ago • 2 comments

Affected Version

paru v2.0.3 - libalpm v14.0.0

Description

Have you checked previous issues? Yes

On upgrading an AUR package with missing dependencies (here specifically build dependencies), paru won't offer to install (and remove them) to build the package and will straight fail with the following message:

error: can't build foo-0.20.0-2, deps not satisfied: bar

Output

No full output as it really wouldn't be relevant here. Configuration files are very close to default, and nothing should be related to the build dependencies. I can of course quickly add anything additional you might find relevant.

fetching devel info...
error: can't build foo-0.20.0-2, deps not satisfied: bar
error: packages failed to build: foo-0.20.0-2

Porkepix avatar Apr 20 '24 14:04 Porkepix

I have the same issue. Installing the dependencies manually and then installing the required packages works

paru --version
paru v2.0.4 - libalpm v15.0.0

nabaco avatar Jan 20 '25 12:01 nabaco

I have similar issue when installing updates and getting stuck on missing patchelf when updating bambustudio-bin

andruhon avatar Jun 15 '25 13:06 andruhon

having this issue with drop-oss-app too. tried to add a new dependency that wasn't listed in the PKGBUILD before but it won't go download it

Beethoven-n avatar Aug 06 '25 20:08 Beethoven-n

yeah i'm gonna just do makepkg -src in file manager review mode and move on with my life

Beethoven-n avatar Aug 11 '25 19:08 Beethoven-n

Dependencies can't be added to manually as the dep resolution is done before download.

Though it seems the original post is about new deps to a package from upstream? Anyway there's basically no info here so closing.

Morganamilo avatar Oct 06 '25 13:10 Morganamilo

Dependencies can't be added to manually as the dep resolution is done before download.

Though it seems the original post is about new deps to a package from upstream? Anyway there's basically no info here so closing.

@Morganamilo I'm not sure what more info would you want? As I remember it, context is, an AUR package receive an update which includes a new build dependency, won't find it and fails on this instead of offering the install and optional uninstall after this.

Porkepix avatar Oct 06 '25 13:10 Porkepix