coreutils 0.6.0 fails to install - directory structure changed in release tarball

[BartVanBerkel]

coreutils 0.6.0 fails to install - directory structure changed in release tarball

Environment

• OS: macOS (aarch64-apple-darwin)
• mise version: 2026.2.3 macos-arm64 (2026-02-04)
• coreutils version: 0.6.0

Steps to reproduce

mise install coreutils@0.6.0
coreutils date +%q
# => zsh: command not found: coreutils

mise install coreutils@0.5.0
coreutils date +%q
# => 1 (works)

Root cause

The uutils/coreutils project changed the directory structure inside release tarballs in PR #10217:

Version	Directory inside tarball
0.5.0	coreutils-0.5.0-aarch64-apple-darwin/
0.6.0	coreutils-aarch64-apple-darwin/

The version number was removed from the directory name. The plugin appears to expect the versioned directory structure.

Expected behavior

The plugin should handle both the old versioned directory structure and the new unversioned structure.

[my4ng]

Duplicate of #10675

[BartVanBerkel]

Then it needs to be released.

[oech3]

No . They were manually renamed.

[BartVanBerkel]

@oech3 @my4ng still mise doesn't like it. Even after clearing the cache.

> ls -al ~/.local/share/mise/installs/coreutils/0.4.0                                      
total 0
drwxr-xr-x@ 3 bartvanberkel  staff   96 Feb  5 10:21 .
drwxr-xr-x@ 8 bartvanberkel  staff  256 Feb  5 10:21 ..
drwxr-xr-x@ 6 bartvanberkel  staff  192 Feb  5 10:21 coreutils-0.4.0-aarch64-apple-darwin

> ls -al ~/.local/share/mise/installs/coreutils/0.6.0 
total 0
drwxr-xr-x@ 3 bartvanberkel  staff   96 Feb  5 10:18 .
drwxr-xr-x@ 8 bartvanberkel  staff  256 Feb  5 10:21 ..
drwxr-xr-x@ 6 bartvanberkel  staff  192 Feb  5 10:18 coreutils-aarch64-apple-darwin

[oech3]

@sylvestre Should we keep version string to the toplevel dir name of tarball too?

[BartVanBerkel]

Feel free to reopen the issue, I'll stay at 0.5.0 for the time being.

[oech3]

Does mise install coreutils@latest-commit work?

[BartVanBerkel]

@oech3 no that doesn't work

> mise install coreutils@latest-commit
coreutils@latest-commit    install                                                                                                                                                                                        
mise ERROR Failed to install aqua:uutils/coreutils@latest-commit: no asset found: coreutils-latest-commit-x86_64-apple-darwin.tar.gz, coreutils-latest-commit-universal-apple-darwin.tar.gz
Available assets:
coreutils-aarch64-apple-darwin.tar.gz
coreutils-aarch64-pc-windows-msvc.zip
coreutils-aarch64-unknown-linux-gnu.tar.gz
coreutils-aarch64-unknown-linux-musl.tar.gz
coreutils-arm-unknown-linux-gnueabihf.tar.gz
coreutils-i686-pc-windows-msvc.zip
coreutils-i686-unknown-linux-gnu.tar.gz
coreutils-i686-unknown-linux-musl.tar.gz
coreutils-riscv64gc-unknown-linux-musl.tar.gz
coreutils-x86_64-apple-darwin.tar.gz
coreutils-x86_64-pc-windows-gnu.zip
coreutils-x86_64-pc-windows-msvc.zip
coreutils-x86_64-unknown-linux-gnu.tar.gz
coreutils-x86_64-unknown-linux-musl.tar.gz
coreutils-x86_64-unknown-redox.tar.gz
docs.tar.zst
individual-x86_64-unknown-linux-gnu.tar.zst: HTTP status client error (404 Not Found) for url (https://api.github.com/repos/uutils/coreutils/releases/tags/vlatest-commit)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

[oech3]

I don't use mise, but you might able to register latest-commit to https://github.com/jdx/mise as a workaround.

[my4ng]

Would it be better to publish a new release? I suspect this won’t be the last time this problem arises

[BartVanBerkel]

Or we should raise a issue in the https://github.com/aquaproj/aqua-registry/issues repo.

https://raw.githubusercontent.com/aquaproj/aqua-registry/main/pkgs/uutils/coreutils/registry.yaml

I'll raise a bug there

[BartVanBerkel]

Raised the bug
aquaproj/aqua-registry#48179
Not sure if it is the way to go, because the tarball directory structured has been restored in PR #10676. It would make more sense to me to recreate the tarballs and upload these. Or create a new release like 0.6.1
just my 2ct ;-)

[BartVanBerkel]

it has been fixed in aquaproj/aqua-registry#48182
let's close this one.