Open rhysm94 opened 1 week ago
have you verified this isn't an issue with ubi?
have you verified this isn't an issue with ubi?
Hey, thanks for replying!
Sorry, I should have done, but I hadn't initially checked. I did look at it afterwards, and this ubi
command seems to install things correctly.
./ubi --verbose -p krzysztofzablocki/Sourcery -t 2.0.1 -e sourcery
When I run ./sourcery --version
I get back 2.0.1
as expected.
I've just updated my .mise.toml
file to include this instead and things now seem to work:
"ubi:krzysztofzablocki/Sourcery" = { version = "2.0.1", exe = "sourcery" }
I'm not really sure what I've tried differently here, maybe I accidentally put quotes around things before? Either way, that seems to work! Sorry again!
Just for future reference, is there a way to define an exe
name to look for with a mise use
command?
Describe the bug I'm trying to install Sourcery using the Ubi backend instead of the asdf plugin, as this means pulling it directly from the source, avoiding potential supply chain attacks.
When attempting to install Sourcery at a specific version using
mise use ubi:krzysztofzablocki/Sourcery@2.0.1
, I then try to use Sourcery like so:mise x -- sourcery --version
to check it's installed, and I get the error:To Reproduce
Run
mise use ubi:krzysztofzablocki/Sourcery@2.0.1
in a project, and attempt to use any Sourcery commands.Expected behavior I expected that using the Ubi tool, I would be able to install Sourcery locally, directly from the source repository instead of via an asdf plugin. I expected that I'd be able to run commands like
mise x -- sourcery --version
to get back2.0.1
as the result after installing it.mise doctor
outputAdditional context I've also tried this with SwiftFormat and had the same result.
I've opened the
~/.local/share/mise/installs
directory and found one calledubi-krzysztofzablocki-sourcery
. This has one actual directory called2.0.1
inside it, which contains a directory calledbin
which is completely empty. When using `mise use tuist@This is the full output from running the initial command with
MISE_VERBOSE=1
: