docs: point the APT instructions at deb.snapdog.cc - #241
Open
metaneutrons wants to merge 1 commit into
Open
Conversation
The packages used to be served from this repository's `gh-pages` branch at `https://snapdogrocks.github.io/snapdog/debian`. They come from the shared archive at `deb.snapdog.cc` now, with a rolling suite and the archive's own keyring. The old location is not redirected. It sits on `github.io` without a hostname of ours, GitHub Pages offers no server-side redirect, and `apt` ignores an HTML one. It stays reachable, frozen at 0.27.4, and the section says so and gives the two lines that remove it. The documented fingerprint changes for a second reason. The old key signed directly; the archive uses a certify-only primary with one signing subkey per domain. `gpg --show-keys` prints the primary first, so that is the value to compare, and the subkey is named for anyone checking the signature itself. The command sequence was executed verbatim in a clean Debian container against the sibling archive `deb.metaneutrons.cc`, which is already publishing: keyring fetched, fingerprint read, sources file written, `apt update` with `AllowInsecureRepositories=false`, install, `--version`. Only the domain and the package names differ from what is written here; `deb.snapdog.cc` itself cannot answer yet, because it publishes for the first time with the next release.
Up to standards ✅🟢 Issues
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The packages used to be served from this repository's
gh-pagesbranch athttps://snapdogrocks.github.io/snapdog/debian. They come from the sharedarchive at
deb.snapdog.ccnow, with a rolling suite and the archive's ownkeyring.
The old location is not redirected. It sits on
github.iowithout a hostname ofours, GitHub Pages offers no server-side redirect, and
aptignores an HTML one.It stays reachable, frozen at 0.27.4, and the section says so and gives the two
lines that remove it.
The documented fingerprint changes for a second reason. The old key signed
directly; the archive uses a certify-only primary with one signing subkey per
domain.
gpg --show-keysprints the primary first, so that is the value tocompare, and the subkey is named for anyone checking the signature itself.
The command sequence was executed verbatim in a clean Debian container against
the sibling archive
deb.metaneutrons.cc, which is already publishing: keyringfetched, fingerprint read, sources file written,
apt updatewithAllowInsecureRepositories=false, install,--version. Only the domain and thepackage names differ from what is written here;
deb.snapdog.ccitself cannotanswer yet, because it publishes for the first time with the next release.