-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Reinstalling AUR Packages Installed by Another AUR Helper or Installing Previously Removed AUR Package Causes Aura to Fail #833
Comments
Thanks for the report. Would you be willing to double-check if the same issue occurs when using the in-development Aura 4 beta? Here's how you'd install it:
This assumes that you have |
The problem remains:
Additionally, does the beta get built using this repo? If so, I'll just switch to using |
The |
Can you provide me that specific command you're using to build the package that's failing? I'd like to try reproducing on my end. |
|
I'm looking into it. |
I was able to build it just now with the Aura 4 beta, although I had to make some improvements regarding It was able to successfully build it within
We can see that the error is a complaint from |
I see this:
However, now I get this error when trying to install it using
I'm really not sure what's going on here, as it's several different errors and there doesn't seem to be consistency between attempts on different days. |
I saw this too during my tests. It appears that within the build process,
Then run the build command again. |
That seems to have fixed that problem, though the move error still exists. |
It used to a problem that the compression algorithm used to finalise built packages (thus producting a Can you go into |
Here's the output:
|
Given that there are two Just checking: did you manually alter the PKGBUILD in anyway, perhaps with |
I just ran the build again, and it only produces the non-debug version for me, and I can only see the one tarball copied into the cache. Let's check if your build process is somehow producing a second package file. Although I'm not sure why it would, since the PKGBUILD itself is quite straight-forward: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gradience |
I haven't modified the PKGBUILD. I just cloned the git repo, but it seems determined to make both of them:
|
What does the
Note the |
Unsure if this is a supported use case or not, so I'd like to state that I have both Aura and paru installed, as Aura is nicer to use but sometimes just doesn't work.
Using
aura-bin
from the AUR. I can install new packages just fine, however previously installed packages give an error similar to this:I have a theory that this is caused by installing a package that was already up to date when downloaded with a different AUR helper. I use paru and since it stores its package cache in a different location Aura isn't sure where to find the package, only that it is in fact downloaded. Is it possible to have Aura check if the package exists in Aura's cache, and if it doesn't then have it downloaded? I get it's extra disk usage, but having Aura just not work for those packages until they're updated can be annoying.
The text was updated successfully, but these errors were encountered: