Re: scripts for DEP-14 migration (Was: How to skip Salsa CI to avoid unnecessary CI runs)
On 27/08/25 at 11:15 +0200, Lucas Nussbaum wrote:
> Maybe what dep14-migrate does should be integrated into the salsa(1)
> tool. Currently salsa(1) does not have really have multi-steps
> processes, but could have. The reason why multi-steps processes are
> required in that context is for the branch renaming:
> 1/ to rename upstream to upstream/latest, you need to create a temporary
> branch, remove 'upstream', then create 'upstream/latest'
> (upstream/latest and upstream cannot coexist because of the common
> prefix).
> 2/ after a branch is renamed, it takes some time (30 seconds max) for
> GitLab to reflect this in API calls that list branches. So it's useful
> to just rename all branches, then wait for things to settle, then use
> the new branch schema to update debian/gbp.conf.
I worked on that and submitted a MR for salsa(1):
https://salsa.debian.org/debian/devscripts/-/merge_requests/559
If you are interested in mass-DEP14 migrations (or massive other actions
over a large package set), please consider using the content of this MR
rather than dep14-migrate.
Lucas
Reply to: