Skip to content

ncdu: Update to fork (1.23.0) - #6571

Open
Omikorin wants to merge 4 commits into
msys2:masterfrom
Omikorin:ncdu-1.23.0
Open

Omikorin wants to merge 4 commits into
msys2:masterfrom
Omikorin:ncdu-1.23.0

Conversation

@Omikorin

@Omikorin Omikorin commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Hi, because of unfortunate event described here the work of Yorhel is continued under this fork.

There wasn't any big change for the original C version, but it should be better to update the sources to active fork (at least active for Zig rewrite and maintained for C).
It uses GitHub Attestations (that uses sigstore) instead of PGP, so it is impossible to add a new key.

@fallenmi fallenmi left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fork publishes an attested source artifact, but this PKGBUILD bypasses it. archive/v${pkgver}.tar.gz hashes to 086063ac09b293d2510f08af0e9e4eb52d2856f77295989e2fe4e18135c5cb18, and GitHub has no attestation for that digest. The release asset ncdu-${pkgver}-src.tar.gz hashes to 2eccb4ce6c4e08d9539155789ff7341fdbde67bd746e9f523d5d3095cd872804 and has attestations tied to refs/tags/v1.23.0 and .github/workflows/c-release.yml.

Because this change removes the PGP-verified source specifically because upstream moved to Sigstore, please point source at the attested release asset, update the checksum, and remove the now-unused validpgpkeys. That aligns the pinned bytes with upstream's published provenance. It does not make makepkg verify the attestation automatically—that remains out of band until the packaging workflow adds an explicit verification step—but the currently selected archive has no attestation to verify.

Reviewed with OpenAI Codex and Anthropic Claude assistance.

@Omikorin
Omikorin requested a review from fallenmi September 1, 2026 22:17
@Omikorin

Omikorin commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Okay, fixed.

I understood the guidelines as to add a new key without removing the old one.

@fallenmi fallenmi left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks — confirmed that the PKGBUILD now uses the attested ncdu-1.23.0-src.tar.gz release asset with its matching SHA-256, and the unused validpgpkeys entry is gone. Both checks pass on this exact head.

Reviewed with OpenAI Codex and Anthropic Claude assistance.

@lazka

lazka commented Sep 15, 2026

Copy link
Copy Markdown
Member

hm, tricky, have any other distros switched?

Currently there are no real code changes in 1.23.0, so no rush I guess.

@Omikorin

Copy link
Copy Markdown
Contributor Author

hm, tricky, have any other distros switched?

Currently there are no real code changes in 1.23.0, so no rush I guess.

I did not find any, although repology is down, so it's kinda difficult.

We can wait with this. The fork continues Yorhel's Zig reboot with some updates to the latest Zig. I found this fork by searching and I think it is the most active one.
I don't know if Zig makes problems, because each version has breaking changes right now.

The biggest problem is when and whether the source will go offline. I've read something on vndb (Yorhel's another project) that his friends will help with paying for servers.

@lazka

lazka commented Sep 15, 2026

Copy link
Copy Markdown
Member

I did not find any, although repology is down, so it's kinda difficult.

yeah, repology/repology-rs#560

@Omikorin

Copy link
Copy Markdown
Contributor Author

Anitya shows this fork
https://release-monitoring.org/project/ncdu

@iedame

iedame commented Sep 15, 2026

Copy link
Copy Markdown

Hello! Nixpkgs actually switched to the BratishkaErik fork back in July: NixOS/nixpkgs@489562d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants