Bug #26401
Remove Foreman GPG key from foreman-release-client
Status:
Closed
Priority:
Normal
Assignee:
Category:
RPMs
Target version:
Difficulty:
Triaged:
Yes
Team Backlog:
Fixed in Releases:
Found in Releases:
Description
This file doesn't belong there since the packages are not signed. It also creates a conflict when upgrading because that file belongs to foreman-release.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot 3 months ago
Updated by - Assignee set to Ewoud Kohl van Wijngaarden
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-packaging/pull/3534 added
#2
Updated by Ewoud Kohl van Wijngaarden 3 months ago
Updated by - Related to Bug #26278: Incorrect GPG key for Foreman client RPM repository added
#3
Updated by Ewoud Kohl van Wijngaarden 3 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman-packaging|e6f243525cff7c7131e2b1458a8f25c46fcfb7ca.
#4
Updated by Tomer Brisker 24 days ago
Updated by - Fixed in Releases 1.20.3, 1.21.4, 1.22.0 added
Fixes #26401 - Remove GPG key from f-release-client
This file belongs to foreman-release and can create conflicts on
upgrade.