salt: [BUG] 2023 GPG key name does not follow Debian standards

Description

The GPG key for the 3006.0 release is now named: SALT-PROJECT-GPG-PUBKEY-2023

Expected behavior As per https://wiki.debian.org/DebianRepository/UseThirdParty it should be called salt-archive-keyring, as it was previously.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 5
  • Comments: 27 (26 by maintainers)

Most upvoted comments

You still really should do all the SHOULDs. It makes it easier for everyone.

While the distinction between hashes mentioned is understandable, it is not simply an issue with expectations around best or most preferred practices, but rather one around templating and automation.

  • How will we determine the filepath to the key automatically when a release in the year 2024 happens?
  • How will we determine the filepath to the key for a release that was released prior to 2024?

Example: If I need to install 3006 in 2024, how do I, in code, determine to use the key SALT-PROJECT-GPG-PUBKEY-2023.gpg? If I also need to install a version released in 2024, how do I determine the key’s name?

The fact is this is a platform for simplifying, templating, and automating execution and this introduces a blocker.

I would just like to add that I’ve been having a bunch of issues getting things to work right again after this change due to certain keys being in some places, but not others, and having to make sure I’m using the right one.

I don’t understand why doing this change in this way was so necessary.