Package Details: rua 0.17.18-1

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: GPL3
Submitter: vasya
Maintainer: vasya
Last Packager: vasya
Votes: 22
Popularity: 1.53
First Submitted: 2018-10-29 14:26
Last Updated: 2020-11-21 19:08

Dependencies (8)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

vasya commented on 2019-11-04 12:31

@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.

Oscar commented on 2019-11-04 12:24

@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

Morganamilo commented on 2019-11-04 12:23

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

vasya commented on 2019-11-04 12:18

@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?

Oscar commented on 2019-11-04 11:54

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)

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 -si or cargo install --force rua to re-build RUA, as per instructions here: https://github.com/vn971/rua#install-dependencies

vasya commented on 2018-10-31 00:11

I've removed all rustup invocations from the PKGBUILD. Something worth considering though is that ~/.cargo (and possibly ~/.rustup) are shared with normal $HOME anyway. I guess that's a common property of all AUR packages using cargo though.

vasya commented on 2018-10-30 23:23

@eschwartz, to address a very specific comment:

only if you're using your own unsupported helper

Said problem appears whenever rustup is used. If you haven't used it before (for this unix user), this is what you'll get.

Regarding $HOME. Would using cargo itself be safe? It does fetch dependencies and store them in ~/.cargo too... I'd really want a way around this myself...

vasya commented on 2018-10-30 23:17

@Morganamilo > Why not just depend on rust? -- That would be ideal. Unfortunately, however, the "rustup" and "rust" packages are in conflict. If the user already uses "rustup", they will have to uninstall it.

coderobe commented on 2018-10-30 23:17

Eli already echoed what i told you on IRC earlier, but for some reason you've only removed parts of it. Could you please get rid of the rest as well? Your package is not special, and this dance is not required - not to mention that your implementation of said hack isn't particularly good either. Seeing your complete lack of understanding on irc regarding this, consider this a warning...