| Git Clone URL: | https://aur.archlinux.org/rua.git (read-only, click to copy) |
|---|---|
| Package Base: | rua |
| Description: | AUR helper in Rust providing control, review, patch application and safe build options |
| Upstream URL: | https://github.com/vn971/rua |
| Keywords: | aur rust |
| Licenses: | |
| Submitter: | vasya |
| Maintainer: | vasya |
| Last Packager: | vasya |
| Votes: | 10 |
| Popularity: | 3.04 |
| First Submitted: | 2018-10-29 14:26 |
| Last Updated: | 2019-12-11 21:30 |
@vasya: I didn't have untracked directories either, but i now uninstalled it (pacman -Rs rua), cloning it into a new folder and executing makepkg -si from there. That solved it, though I'm not sure which one of those steps did ^^
Anyways, thank (both of) you for your help
@Oscar: (with the latest edit). I think the directory is still not clean. Otherwise, why would it, for example, write Removing existing $pkgdir/ directory... ? Also, I see no logs of actual compilation. Guessing by the timestamps, it didn't happen. Can you try cleaning with git clean -fd instead of git clean -xfq? The -d option forces to remove untracked files, too.
@vasya: of course, are there better places than here to post this than here or is this the correct place?
git clean -xfq && makepkg -si (edited to change command and output to clean first & prettified output)
==> Making package: rua 0.14.19-1 (Mon 04 Nov 2019 14:38:25 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading rua-0.14.19.tar.gz...
==> Validating source files with sha256sums...
==> Extracting sources...
-> Extracting rua-0.14.19.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Finished release [optimized] target(s) in 0.11s
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Stripping unneeded symbols from binaries and libraries...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "rua"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: rua 0.14.19-1 (Mon 04 Nov 2019 14:39:09 CET)
==> Installing package rua with pacman -U...
loading packages...
warning: rua-0.14.19-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) rua-0.14.19-1
Total Installed Size: 6.10 MiB
Net Upgrade Size: 0.00 MiB
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
reinstalling rua...
ldconfig: File /usr/lib/libgeocode-glib.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgeoclue-2.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgeoclue-2.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgeocode-glib.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgeocode-glib.so is empty, not checked.
ldconfig: File /usr/lib/libgeoclue-2.so is empty, not checked.
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
pacman -Q rua
rua 0.14.19-1
which rua or which -a rua
/usr/bin/rua
@Oscar: can you please give the full output of makepkg -si and pacman -Q rua?
@vasya: which -a rua returns the same as which rua
The full error is:
rua upgrade
rua: error while loading shared libraries: libalpm.so.11: cannot open shared object file: No such file or directory
@Morganamilo, ah indeed you're right, an older version would simply fail to build. It's probably an issue with PATH indeed. It can be checked with which -a rua.
@vasya: It is 0.14.19 and it's the same as the given PKGBUILD. Likewise I'm on the same commit as https://aur.archlinux.org/rua.git (3f1206) and on the master branch
@Morganamilo: The only time I ever used cargo install (manually) was to try to update rua as it didn't work through makepkg; it failed telling me that I do not have a default toolchain configured.
which rua gives me /usr/bin/rua
Linking is done at compile time. Even if you were trying to build an older version of rua you'd never get the error that libalpm.so.11 does not exist. Instead linking will just fail outright.
My guess is you've used cargo install and now have an old version in PATH, and even though you've installed the new version via makepkg, the old version is still taking priority.
which rua
@Oscar: that's very weird. What version is actually written in the PKGBUILD? It should be 0.14.19, as seen here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=rua Is it also in your local PKGBUILD?
I've updated the repository and re-installed it using git clean -xfq && git pull && makepkg -si, but it still tells me that libalpm.so.11 does not exist. Is there something I'm missing? (I am on the newest commit of rua and have just upgraded all pacman packages)
Pinned Comments
vasya commented on 2019-10-25 08:21
Those who upgraded pacman in the last days will notice that RUA becomes broken. This is caused by a change in pacman-s underlying library, "libalpm".
You need to install RUA version 0.14.16 or newer to make it work with newest pacman. You can use
makepkg -siorcargo install --force ruato re-build RUA, as per instructions here: https://github.com/vn971/rua#install-dependencies