Package Details: proto 0.53.0-1

Git Clone URL: https://aur.archlinux.org/proto.git (read-only, click to copy)
Package Base: proto
Description: Pluggable multi-language version manager
Upstream URL: https://github.com/moonrepo/proto
Keywords: bun deno nodejs version-manager
Licenses: MIT
Submitter: phnx47
Maintainer: phnx47
Last Packager: phnx47
Votes: 4
Popularity: 0.000467
First Submitted: 2023-05-05 16:50 (UTC)
Last Updated: 2025-09-19 02:00 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

snowman78 commented on 2025-07-22 19:38 (UTC)

Thank you for your work! The issue was that my rustup thought stable was 1.86.0. In my ignorance I thought this was something that would be updated along other stuff, seeming as rustup was installed via something else, probably either proto or moon (or both). After I did rustup update, stable changed to 1.88.0, so appears to be no issues now.

phnx47 commented on 2025-07-22 15:44 (UTC)

@snowman78 I see, you're referring to makedepends, not a runtime dependency. This PKGBUILD depends on cargo (rust or rustup). Currently, the latest rust version published in extra is 1.88.0, so everything should be fine. I've tested it in a clean chroot. If you still encounter issues, please try updating your rust version before building.

snowman78 commented on 2025-07-22 15:34 (UTC)

I ran yay --editmenu -S aur/proto, edited PKGBUILD to have 1.88 rather than stable, and this got proto to build properly for me (I'm on EndeavourOS if that matters anything). I can understand if you don't want to depend on a specific version, but the last update of proto added minimumsversions (that is where the 1.88.0 comes from).

snowman78 commented on 2025-07-22 15:22 (UTC) (edited on 2025-07-22 15:23 (UTC) by snowman78)

Hmm, no Rust expert myself, but I don't think that is the correct fix (or the only fix). rustup stable provides 1.86

The latest update 0.51.4-1 gives me these errors:

==> Making package: proto 0.51.4-1 (Tue Jul 22 17:19:57 2025) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Removing existing $pkgdir/ directory... ==> Starting build()... error: rustc 1.86.0 is not supported by the following packages: proto_cli@0.51.4 requires rustc 1.88.0 proto_cli@0.51.4 requires rustc 1.88.0 proto_core@0.51.5 requires rustc 1.88.0 warpgate@0.26.1 requires rustc 1.88.0

==> ERROR: A failure occurred in build(). Aborting... -> error making: proto-exit status 4

phnx47 commented on 2025-07-22 12:17 (UTC)

@snowman78 Thank you! I've checked and found that proto uses rustup to install rust, so I've added rustup as an optional dependency.

snowman78 commented on 2025-07-21 20:46 (UTC)

The latest proto version requires rust 1.88 (at least via warpgate dependency).

phnx47 commented on 2024-06-08 05:34 (UTC)

proto::shim::missing_binary error fixed in v0.36.1.

usagiga commented on 2024-05-30 12:45 (UTC)

@phnx47 Thank you for your investigation and your kindness. For now, I'll resolve my problem by this solution.

By the way, I'm wondering if this is a bug or if there're some reasons for this change. I'll keep an eye on the issue.

phnx47 commented on 2024-05-30 09:49 (UTC) (edited on 2024-05-30 17:31 (UTC) by phnx47)

Raised issue in the upstream proto#490

As temporary solution you can create a symlink

ln -s /usr/bin/proto-shim ~/.proto/bin/proto-shim

or

ln -s /usr/bin/proto-shim ${PROTO_HOME}/bin/proto-shim

or export PROTO_LOOKUP_DIR

export PROTO_LOOKUP_DIR=/usr/bin

phnx47 commented on 2024-05-28 15:48 (UTC)

@usagiga Oh, yes, something seems changed, I will investigate it.

1 2 Next › Last »