Pulp - fix repofiles to point to pulp #3375
Assignees
Labels
Comments
29 tasks
FrostyX
changed the title
|
Read this blog post first - https://pavel.raiskup.cz/blog/copr-and-pulp-content-hosting.html |
|
Warning: DNF4 uses the repofiles from project overview but DNF5 uses API call with all repofiles for the project |
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Aug 23, 2024
Fix fedora-copr#3375 Of course only for Copr projects that has configured to have their storage in Pulp, not all Copr projects.
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Aug 24, 2024
Fix fedora-copr#3375 Of course only for Copr projects that has configured to have their storage in Pulp, not all Copr projects. There are three possible options how to implement this. 1. The Most straightforward is to not generate repofiles ourselves and let Pulp do it. The downside is that we would have to pass additional parameters (it is possible though) such as repo priority, module hotfixes attribute, etc, and figure out how to count repo downloads 2. Generate repofiles ourselves, only point to `baseurl` in Pulp. This IMHO the best option for keeping compatibility between storage on the backend and in Pulp, so I implement this option in this PR. 3. Adding a Lighttpd redirect for `baseurl` of the Pulp-stored projects to Pulp content URL. This will be needed in the future to ensure that users don't have to re-enable Copr repositories, once those projects are migrated to Pulp. But this will be hard to implement, so we decided to do it when the time comes.
FrostyX
added a commit
to FrostyX/dnf5
that referenced
this issue
Sep 24, 2024
See fedora-copr/copr#3375 When an alternative storage (such as Pulp) for Copr is used, the pubkey.gpg is still being stored on Copr backend. Therefore we can't always construct the correct pubkey URL here in the DNF plugin.
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Sep 24, 2024
Fix fedora-copr#3375 Of course only for Copr projects that has configured to have their storage in Pulp, not all Copr projects. There are three possible options how to implement this. 1. The Most straightforward is to not generate repofiles ourselves and let Pulp do it. The downside is that we would have to pass additional parameters (it is possible though) such as repo priority, module hotfixes attribute, etc, and figure out how to count repo downloads 2. Generate repofiles ourselves, only point to `baseurl` in Pulp. This IMHO the best option for keeping compatibility between storage on the backend and in Pulp, so I implement this option in this PR. 3. Adding a Lighttpd redirect for `baseurl` of the Pulp-stored projects to Pulp content URL. This will be needed in the future to ensure that users don't have to re-enable Copr repositories, once those projects are migrated to Pulp. But this will be hard to implement, so we decided to do it when the time comes.
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Sep 24, 2024
Fix fedora-copr#3375 Of course only for Copr projects that has configured to have their storage in Pulp, not all Copr projects. There are three possible options how to implement this. 1. The Most straightforward is to not generate repofiles ourselves and let Pulp do it. The downside is that we would have to pass additional parameters (it is possible though) such as repo priority, module hotfixes attribute, etc, and figure out how to count repo downloads 2. Generate repofiles ourselves, only point to `baseurl` in Pulp. This IMHO the best option for keeping compatibility between storage on the backend and in Pulp, so I implement this option in this PR. 3. Adding a Lighttpd redirect for `baseurl` of the Pulp-stored projects to Pulp content URL. This will be needed in the future to ensure that users don't have to re-enable Copr repositories, once those projects are migrated to Pulp. But this will be hard to implement, so we decided to do it when the time comes.
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Sep 24, 2024
Fix fedora-copr#3375 Of course only for Copr projects that has configured to have their storage in Pulp, not all Copr projects. There are three possible options how to implement this. 1. The Most straightforward is to not generate repofiles ourselves and let Pulp do it. The downside is that we would have to pass additional parameters (it is possible though) such as repo priority, module hotfixes attribute, etc, and figure out how to count repo downloads 2. Generate repofiles ourselves, only point to `baseurl` in Pulp. This IMHO the best option for keeping compatibility between storage on the backend and in Pulp, so I implement this option in this PR. 3. Adding a Lighttpd redirect for `baseurl` of the Pulp-stored projects to Pulp content URL. This will be needed in the future to ensure that users don't have to re-enable Copr repositories, once those projects are migrated to Pulp. But this will be hard to implement, so we decided to do it when the time comes.
github-merge-queue bot
pushed a commit
to rpm-software-management/dnf5
that referenced
this issue
Sep 25, 2024
See fedora-copr/copr#3375 When an alternative storage (such as Pulp) for Copr is used, the pubkey.gpg is still being stored on Copr backend. Therefore we can't always construct the correct pubkey URL here in the DNF plugin.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: