releng

#12884 ensure up to date Rawhide GPG key is published on https://fedoraproject.org/ site
Opened by ydroneaud. Modified

Open
Close Issue

https://fedoraproject.org/security and https://fedoraproject.org/fedora.gpg need to be updated every time a new release is branched.

I've raised the issue previously in #12270 for F42. Since then I'm raising the issue directly to fedora-website:

  • for F42 - https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/307
  • for F43 - https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/339
  • for F44 - https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/377

Is is possible to automate, or at least, be a step in the branching process to ensure https://fedoraproject.org/security and https://fedoraproject.org/fedora.gpg are updated ?

CC: @darknao;

Also I could try to open a Pr and fix it for now, if it is alright?

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Metadata Update from @jnsamyak:
- Issue tagged with: medium-gain, medium-trouble, ops

I added the missing key to the website and the matching openpgpkey dns record.

Is it possible to add a step "publish new RPM key" to the schedule for future Fedora releases ?
https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html

I added the missing key to the website and the matching openpgpkey dns record.

Thanks !
Metadata

medium-gain medium-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.