Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deb Mirror, multiple gpgkeys #530

Open
jgrammen-agilitypr opened this issue May 30, 2022 · 1 comment
Open

Deb Mirror, multiple gpgkeys #530

jgrammen-agilitypr opened this issue May 30, 2022 · 1 comment
Labels
.doc CHANGES/<issue_number>.doc

Comments

@jgrammen-agilitypr
Copy link

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.

@jgrammen-agilitypr
Copy link
Author

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

@quba42 quba42 added .doc CHANGES/<issue_number>.doc and removed Triage-Needed labels Jun 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.doc CHANGES/<issue_number>.doc
Projects
None yet
Development

No branches or pull requests

2 participants