Skip to content

zutty: update to 0.16.0#58427

Closed
NyaaaWhatsUpDoc wants to merge 1 commit intovoid-linux:masterfrom
NyaaaWhatsUpDoc:zutty-update
Closed

zutty: update to 0.16.0#58427
NyaaaWhatsUpDoc wants to merge 1 commit intovoid-linux:masterfrom
NyaaaWhatsUpDoc:zutty-update

Conversation

@NyaaaWhatsUpDoc
Copy link
Copy Markdown
Contributor

Also updates the distfiles location to the new as linked on https://github.com/tomscii/zutty

Testing the changes

  • I tested the changes in this PR: briefly

Local build testing

  • I built this PR locally for my native architecture, x86-64

Comment thread srcpkgs/zutty/template Outdated
homepage="https://tomscii.sig7.se/zutty"
distfiles="https://github.com/tomscii/zutty/archive/refs/tags/${version}.tar.gz"
checksum=6de17d6b7a3fe6991df30ba1ca7d6a08e605369cf92247deeb19758379b5af2f
distfiles="https://git.hq.sig7.se/zutty.git/snapshot/${_commit}.tar.gz"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Use the upstream tag rather than a commit hash; then drop the _commit variable altogether.

Suggested change
distfiles="https://git.hq.sig7.se/zutty.git/snapshot/${_commit}.tar.gz"
distfiles="https://git.hq.sig7.se/zutty.git/snapshot/${version}.tar.gz"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

thanks, have done so :)

Copy link
Copy Markdown
Contributor Author

@NyaaaWhatsUpDoc NyaaaWhatsUpDoc Jan 8, 2026

Choose a reason for hiding this comment

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

hmm it seems their new repository hosting must have the github worker IP subnets banned. i can fetch the file fine from my personal machine, but my personal build setup (accessing from a hetzner ip) also gets timed out in a similar manner to the github workers.

@ahesford
Copy link
Copy Markdown
Member

ahesford commented Jan 8, 2026

Let's see if the CI problem resolves in a future update; otherwise, we can just skip checks in CI.

@ahesford
Copy link
Copy Markdown
Member

ahesford commented Jan 8, 2026

Well, the upstream source isn't responding to our builders, either. See build log. Broken in 4ed70d8.

Please contact upstream to resolve the issue and, when we can reliably fetch in CI, we can try unbreaking the package.

MtFBella109 pushed a commit to MtFBella109/void-packages that referenced this pull request Jan 15, 2026
Closes: void-linux#58427 [via git-merge-pr]
hristoast pushed a commit to hristoast/void-packages that referenced this pull request Jan 18, 2026
Closes: void-linux#58427 [via git-merge-pr]
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.

2 participants