Arch Linux User Repository

Never mind, I figured out how to fix it, run:

rustup upgrade

Actually I don't know anything about Rust programming lannguage, it sounds like there is a Rust package management system that I had no idea I needed to update until now. Is it possible (if that even makes sense) to add rust upgrade as a build step?

@vasya thanks for helping, I still cannot get it to build. I'm getting the same error.

error[E0658]: `match` is not allowed in a `const fn`
   --> /home/vanja/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/lib.rs:156:9
    |
156 | /         match address {
157 | |             SocketAddr::V4(_) => Domain::IPV4,
158 | |             SocketAddr::V6(_) => Domain::IPV6,
159 | |         }
    | |_________^
    |
    = note: see issue #49146 <https://github.com/rust-lang/rust/issues/49146> for more information

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `socket2`.

Any ideas?

Due to library changes in pacman (5.2.2 -> 6.0.0), rua needs to be re-built from source to work again.

If you see an error message like

rua: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory

Then please clone the repo https://aur.archlinux.org/rua.git and install the new version via makepkg -si (if you use rustup, then also rustup update)

@vanja_z, thanks for writing. This is due to a major pacman upgrade (5.2.2-4 -> 6.0.0-2) which did not keep binary compatibility and thus changed the libalpm.so file name. rua needs to change its alpm dependency to work with the new libalpm. I'll try to do that now

Hi, I can't build rua anymore since recent updates nor can I run my existing build. Runtime errors with existing build,

rua: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory

Build errors,

error[E0658]: `match` is not allowed in a `const fn`
   --> /home/vanja/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/lib.rs:156:9
    |
156 | /         match address {
157 | |             SocketAddr::V4(_) => Domain::IPV4,
158 | |             SocketAddr::V6(_) => Domain::IPV6,
159 | |         }
    | |_________^
    |
    = note: see issue #49146 <https://github.com/rust-lang/rust/issues/49146> for more information

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `socket2`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

@Subject-17 I think that's a good question though. I've created an issue to change the behavior of rua and clean build garbage automatically upon a successful build: https://github.com/vn971/rua/issues/139

Hey @Subject-17, yes, it is safe to remove ~/.cache/rua. It contains the build cache.

There's also ~/.local/share/rua that stores already built artifacts (in case you want to re-install old versions or temporarily deinstalled ones). And the settings live in ~/.config/rua. Nothing else.

Is there a flag to clear out the rua cache? Is it safe to rm from ./.cache/rua ?

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