openresty / openresty/openresty.org
apt keyring changed with Debian 12
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 293
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
I recently updates to Debian 12. This message appears while doing an apt update:
W: http://openresty.org/package/debian/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
There referenced man 8 apt-key suggests:
wget -O - https://openresty.org/package/pubkey.gpg | sudo tee /etc/apt/trusted.gpg.d/openresty.asc
I can very that this is working. 🟢
The reference is here: https://github.com/openresty/openresty.org/blob/master/v2/en/linux-packages.md?plain=1#L259
I don't know how far back this change to apt happened, so I would suggest a split for the Debian section in For Debian <= 11 and For Debian 12 or above (just as with ubuntu).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open v2/en/linux-packages.md around line 259 and read the current Debian package instructions alongside the Ubuntu section. Update the Debian documentation to distinguish Debian <= 11 from Debian 12 or above, using the keyring command described in the issue. Done means the Debian 12 warning is addressed while the older Debian instructions remain covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, linux
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100