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: 60
Popularity: 0.33
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 »

vasya commented on 2020-02-07 23:17 (UTC) (edited on 2020-02-07 23:21 (UTC) by vasya)

Hi aconsolelogger, good question(s). Socks is not supported at the moment. To implement it, we need to use socks for "AUR RPC" requests and for "git" commands. Git commands seem to be proxy-able like this: https://stackoverflow.com/questions/15227130/using-a-socks-proxy-with-git-for-the-http-transport

For the HTTP part, we use raur library: https://gitlab.com/davidbittner/raur which in turn uses reqwest. Maybe we can configure a reqwest::Client that has socks proxy configured right inside it. Then we can make all the changes in RUA code only. If not, we'll have to make a PR for raur that adds socks proxy support. This library seems to be reasonably alive, so I think it's pretty doable.

Would you be willing to work on that?

For man pages: they are, unfortunately, not generated yet. I didn't find a convenient tool that would generate it re-using some information from the CLI description. There are different approaches to the man pages, but at least that's one of them. If you have any ideas, feel free to share. Otherwise, rua --help should help for now. For a .conf file - indeed there's none at the moment. I didn't want to opt in into any particular configuration format/style for now. If we can live with just a CLI parameter for now, that's fine by me. If you'd like to see proper config support pushed more, please say so, and whether you'd be willing to participate on implementing it / making design choices on that as well.

UPD: this text suggests that HTTP part can be fixed with just configuring a reqwest client: https://github.com/seanmonstar/reqwest/pull/487/files#diff-89b8ff6a281cbb06a63127aa0f05680bR104 so we probably won't need to patch raur, only to configure the proper client for it (everything can be fixed just in RUA).

aconsolelogger commented on 2020-02-07 21:46 (UTC)

Is it possible to configure rua to connect using a socks proxy? There doesn't seem to be a manpage and I couldn't find a .conf file either.

Oscar commented on 2019-11-04 16:20 (UTC) (edited on 2019-11-04 16:20 (UTC) by Oscar)

@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

vasya commented on 2019-11-04 15:25 (UTC) (edited on 2019-11-04 15:26 (UTC) by vasya)

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

Oscar commented on 2019-11-04 13:37 (UTC) (edited on 2019-11-04 13:47 (UTC) by Oscar)

@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

vasya commented on 2019-11-04 12:44 (UTC)

@Oscar: can you please give the full output of makepkg -si and pacman -Q rua?

Oscar commented on 2019-11-04 12:35 (UTC) (edited on 2019-11-04 12:36 (UTC) by Oscar)

@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

vasya commented on 2019-11-04 12:31 (UTC)

@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 (UTC) (edited on 2019-11-04 12:29 (UTC) by Oscar)

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

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

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