[Peridot] clone swap 9.3 project to 9.4 #24
Labels
No Milestone
No project
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sig_core/meta#24
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
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.
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.
https://peridot.build.resf.org/df5bcbfc-ba83-4da8-84d6-ae0168921b4d/tasks/eb6989e0-e487-4c3f-800b-3aa582a1896e
We can probably make this a peridot cli command... will think about this.