[Peridot] clone swap 9.3 project to 9.4 #24

Closed
opened 2024-04-01 00:35:01 +00:00 by label · 5 comments
Owner

Clone swap 9.3 to 9.4 project. And if possible, provide the steps and/or ability to add/move/remove packages around during a catalog sync on the new project. We'll also need an external repository applied.

External repo: https://bootstrap9.releng.rockylinux.org/repos_stage1/9.4-BETA/9.4-BETA-bootstrap_$basearch/

Checklist:

  • Sync catalog
  • Clone swap 9.3 to 9.4
  • Ensure standard rocky linux 9 GPG key is applied to project
  • Ensure external repo is applied
  • Ensure admin privs to project, including API key
Clone swap [9.3](https://peridot.build.resf.org/6202c09e-6252-4d3a-bcd3-9c7751682970) to [9.4](https://peridot.build.resf.org/df5bcbfc-ba83-4da8-84d6-ae0168921b4d) project. And if possible, provide the steps and/or ability to add/move/remove packages around during a catalog sync on the new project. We'll also need an external repository applied. External repo: `https://bootstrap9.releng.rockylinux.org/repos_stage1/9.4-BETA/9.4-BETA-bootstrap_$basearch/` Checklist: * [X] Sync catalog * [x] Clone swap 9.3 to 9.4 * [x] Ensure standard rocky linux 9 GPG key is applied to project * [x] Ensure external repo is applied * [x] Ensure admin privs to project, including API key
label added this to the Rocky Linux 9.4 milestone 2024-04-01 00:35:01 +00:00
label added the
OS_Development
label 2024-04-01 00:35:02 +00:00
mustafa was assigned by label 2024-04-01 00:35:02 +00:00
neil was assigned by label 2024-04-01 00:35:02 +00:00
label added this to the Rocky Linux 9 project 2024-04-01 00:35:02 +00:00
Owner

If I am reading this correctly, we do not currently have the ability to clone swap and move an NEVRA between repositories, so this would need to be done as a post-processing step. I will coordinate with @mustafa on how best to accomplish this and write a SOP with the details.

If I am reading [this](https://github.com/rocky-linux/peridot/blob/cedf1d1db1bf9d804fe484f99d7d2939ce6b6679/peridot/builder/v1/workflow/clone_swap.go#L157) correctly, we do not currently have the ability to clone swap *and* move an NEVRA between repositories, so this would need to be done as a post-processing step. I will coordinate with @mustafa on how best to accomplish this and write a SOP with the details.
Author
Owner

When a new version of a package is built, it will move automatically, so we'll be fine there. My request/concern was more or less after I've taken care of building all 9.4 packages and addressing the adds/removes/moves that occurred where a package did not receive an update. And to also avoid having to pester yourself or @mustafa to do it for me, if that's even possible.

An example would be like libarchive. Some libarchive-devel packages are moving to AppStream and it doesn't have an update for 9.4.

image

When a new version of a package is built, it will move automatically, so we'll be fine there. My request/concern was more or less after I've taken care of building all 9.4 packages and addressing the adds/removes/moves that occurred where a package did not receive an update. And to also avoid having to pester yourself or @mustafa to do it for me, if that's even possible. An example would be like libarchive. Some libarchive-devel packages are moving to AppStream and it doesn't have an update for 9.4. ![image](/attachments/d7f54bf2-1781-463c-b68b-759504c7fdbe)
116 KiB
neil added the
Meeting
label 2024-04-01 20:57:29 +00:00
Owner
https://peridot.build.resf.org/df5bcbfc-ba83-4da8-84d6-ae0168921b4d/tasks/eb6989e0-e487-4c3f-800b-3aa582a1896e
Owner
POST https://peridot.build.resf.org/api/v1/projects/df5bcbfc-ba83-4da8-84d6-ae0168921b4d/cloneswap
{
  "target_project_id": "df5bcbfc-ba83-4da8-84d6-ae0168921b4d",
  "src_project_id": "6202c09e-6252-4d3a-bcd3-9c7751682970"
}

We can probably make this a peridot cli command... will think about this.

``` POST https://peridot.build.resf.org/api/v1/projects/df5bcbfc-ba83-4da8-84d6-ae0168921b4d/cloneswap { "target_project_id": "df5bcbfc-ba83-4da8-84d6-ae0168921b4d", "src_project_id": "6202c09e-6252-4d3a-bcd3-9c7751682970" } ``` We can probably make this a peridot cli command... will think about this.
Owner
  • Setup external repo
  • setup project gpg key
  • setup project authentication creds for Gitlab
  • added releng group to admin
  • made public
* Setup external repo * setup project gpg key * setup project authentication creds for Gitlab * added releng group to admin * made public
neil removed the
Meeting
label 2024-04-02 01:48:17 +00:00
neil closed this issue 2024-04-02 01:50:10 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sig_core/meta#24
No description provided.