-
Notifications
You must be signed in to change notification settings - Fork 91
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
aur sync to just rebuild a package? #423
Comments
Can't you just rebuild it with: |
well, @rafasc was right, it works in a 2 steps process, but pretty easy. 1st, re-build, and include new package into aurutils repo, and 2nd, install with pacman... might create a 3rd party script, as suggested by @terencode , or live with those 2 steps... This can be closed then, though in my mind "aur sync" might take care of that in one step (it does the rebuild and repo inclusion, it just misses the install). Thanks ! |
@je-vv I just made this:
save it under aur-rebuild somewhere in one of your $PATH directories and chmod +x it, then try "aur rebuild grive" |
|
Hi,
At times I just need to rebuild a package, although there's no new AUR new version for it. For example, grive started to complain about "libjson-c.so.3" not being there, but that's because now "libjson-c.so.4" is there, same thing with it's other dependency on libboost...
I've used "-f" on "aur sync", but that still ignores rebuilding and adding to the repo DB the same package.
There are many manual ways to solve the issue. One is to remove the package with "pacman -R", so that there are no posterior problems with same versions but different contents on the installed DB, then removing the package from the aurutils repo DB (repo-remove), then remove the package itself from the repo (as well as its signature), and build the package again with "aur sync", so it gets into the aur utils repo, and then install it back through pacman...
Wondering if there's something missing for such cases, or if I'm the one missing something when there's something already available...
The text was updated successfully, but these errors were encountered: