Skip to content

update gpg key to use hpe2 key, per text comment#956

Merged
umjnega merged 1 commit intoproductionfrom
hpe_repo_update
Mar 16, 2026
Merged

update gpg key to use hpe2 key, per text comment#956
umjnega merged 1 commit intoproductionfrom
hpe_repo_update

Conversation

@umjnega
Copy link
Contributor

@umjnega umjnega commented Mar 11, 2026

No description provided.

@umjnega
Copy link
Contributor Author

umjnega commented Mar 11, 2026

Apt was failing on a server and I do not think the HPE repo is needed anymore now that its a VM, but i saw the comment below in the nebula code that is probably the better change to make.

The comment:

  #`hpe1` is deprecated, but as of this writing is still used to sign HPE's Debian repos.
  # At some point in 2025 this key should stop working, at which point we can move Debian
  # to hpe2 as well. Due to an apparent bug in apt, hpe2 does not work when armored, so
  # it has been included in this repo as a dearmored binary key.
  # See also: https://downloads.linux.hpe.com/SDR/keys.html

@skorner
Copy link
Member

skorner commented Mar 11, 2026

We only considered a p->v for that server, so it is still a physical server. But this change still makes sense in general for our remaining HP servers.

@umjnega
Copy link
Contributor Author

umjnega commented Mar 11, 2026

Thats right, i forgot it was still physical. My bad. Thanks for the feed back.

Copy link
Member

@rrotter rrotter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looked into this comment on the HPE site:

fingerprint: 26C2B797 (extended through 2027)

But it is indeed the same key we already have, so no action needed on that.

If this worked everywhere I'd remove the condition rather than just setting Debian to hpe2 (and also remove hpe1 from the files dir). But this does not work on bullseye, so for now my suggested change should do it.

@rrotter
Copy link
Member

rrotter commented Mar 13, 2026

lgtm. One good last step before merging would be to re-test this on one Debian 12 host and one Debian 11 host.

@umjnega umjnega merged commit 6f29b42 into production Mar 16, 2026
7 checks passed
@umjnega umjnega deleted the hpe_repo_update branch March 17, 2026 16:45
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.

3 participants