Package Details: rua 0.19.10-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: 58
Popularity: 1.56
First Submitted: 2018-10-29 14:26 (UTC)
Last Updated: 2024-01-02 23:51 (UTC)

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

Oscar commented on 2019-11-04 11:54 (UTC)

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 (UTC) (edited on 2019-11-04 16:33 (UTC) by vasya)

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 (UTC)

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 (UTC)

@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 (UTC) (edited on 2018-10-30 23:17 (UTC) by vasya)

@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 (UTC)

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

eschwartz commented on 2018-10-30 23:11 (UTC)

puts on Trusted User hat

Suddenly using rustup and installing a toolchain to the user's $HOME is not okay, moreso when the need for doing so is only if you're using your own unsupported helper which breaks this.

If users use rustup, that's their problem, and I guess they shouldn't use toolchains that install themselves to $HOME in order to build packages. This very program was supposedly supposed to prevent issues like this -- it's ironic that the only way to build this PKGBUILD in a sane manner, is to use the program you haven't built yet to do it!

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »