Skip to content

Bump latest_version to 3.0.4 (fixes stale download link) - #8

Open
Itachi-0xAI wants to merge 1 commit into
pkgconf:masterfrom
Itachi-0xAI:fix-outdated-download-link
Open

Bump latest_version to 3.0.4 (fixes stale download link)#8
Itachi-0xAI wants to merge 1 commit into
pkgconf:masterfrom
Itachi-0xAI:fix-outdated-download-link

Conversation

@Itachi-0xAI

Copy link
Copy Markdown

What's wrong

_config.yml has latest_version: 1.1.0. That value feeds the
download button on the homepage (_layouts/index.html), which builds
its link as:

https://distfiles.dereferenced.org/pkgconf/pkgconf-{{ site.latest_version }}.tar.xz

So the "Download (.tar.xz)" button on pkgconf.org currently points to
a release from 2016, not the current one.

The fix

Bump latest_version to 3.0.4, matching the latest GitHub release
tag (pkgconf-3.0.4). I confirmed the tarball actually exists at that
path before opening this:

$ curl -sI https://distfiles.dereferenced.org/pkgconf/pkgconf-3.0.4.tar.xz
HTTP/2 200

Scope note

This closes the "download link is outdated" part of #232. The same
issue also reports an HTTPS certificate mismatch on pkgconf.org (the
cert only covers *.github.com/*.github.io, not the custom
domain) — I checked and that's still happening too, but it's a GitHub
Pages custom-domain/HTTPS configuration issue, not something a
content change in this repo can fix. Leaving that for a repo owner
with access to the Pages settings / DNS.

Refs #232.

_config.yml still had latest_version: 1.1.0, a release from 2016.
The homepage's download button builds its URL straight from this
value (see _layouts/index.html), so anyone clicking "Download" on
pkgconf.org has been getting a nearly decade-old tarball instead of
the current release.

Verified https://distfiles.dereferenced.org/pkgconf/pkgconf-3.0.4.tar.xz
exists and matches the latest GitHub release tag (pkgconf-3.0.4).

Reported in pkgconf/pkgconf#232, which also flags an HTTPS
certificate mismatch on pkgconf.org (cert only covers *.github.com).
That part isn't fixable from this repo's content — it needs a GitHub
Pages custom-domain/HTTPS setting change by a repo owner — so this PR
only addresses the stale version number.
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.

1 participant