You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version
Pulpcore version:
3.19
Pulp plugins installed and their versions:
pulp-deb 2.18.0
pulp-file 1.10.2
Describe the bug
There is no way to associate multiple gpgkeys with a single repository. Which is necessary when trying to mirror archive.ubuntu.com, which publishes different gpgkeys for different distributions (focal vs bionic)
To Reproduce
Create a remote, that mirrors "http://ca.archive.ubuntu.com/ubuntu" with distributions: "focal bionic"
supply the gpgkey field with the value for bionic.
Get error about no release file for focal, becasue the gpgkey is different.
Expected behavior
Support mulitple gpgkeys so that both distributions can sync
It appears based on work around recommend to me by the community that it is possible to sync a upstream repository signed with mulitple keys. You need to insert into the gpgkey field either a concatenated set of gpg keys or export mulitple keys into a single key.
If this is confirmed by someone else, then I would suggest this ticket become a request for documentation updates, since the docs do not make it clear that this (multiple gpg in the gpgkey field) is possible
Version
Pulpcore version:
3.19
Pulp plugins installed and their versions:
pulp-deb 2.18.0
pulp-file 1.10.2
Describe the bug
There is no way to associate multiple gpgkeys with a single repository. Which is necessary when trying to mirror archive.ubuntu.com, which publishes different gpgkeys for different distributions (focal vs bionic)
To Reproduce
Create a remote, that mirrors "http://ca.archive.ubuntu.com/ubuntu" with distributions: "focal bionic"
supply the gpgkey field with the value for bionic.
Get error about no release file for focal, becasue the gpgkey is different.
Expected behavior
Support mulitple gpgkeys so that both distributions can sync
Additional context
Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.
The text was updated successfully, but these errors were encountered: