Re: DEP-14 migration questions
On 24/08/25 at 15:53 +0200, Lucas Nussbaum wrote:
> On 21/08/25 at 12:15 +0200, Lucas Nussbaum wrote:
> > Hi,
> >
> > There was consensus during the DebConf BOF that we should migrate to
> > DEP-14. I plan to work on that.
>
> Hi,
>
> I wrote¹ a script that uses the GitLab API to migrate a project to DEP-14.
> See https://salsa.debian.org/ruby-team/meta/-/blob/master/dep14-migrate?ref_type=heads
>
> I will start using it to migrate repositories, starting with the easier cases first.
> Reviews of the script welcomed. It will probably need some adjustments
> for the more complex cases.
So this went well, and I migrated all non-native packages to DEP-14.
The migration also included renaming most other branches (for example,
for backports, fasttrack, etc.) to the new layout, but there is still
some cleanup to on a per-package basis.
Also the script is robust and could be useful for other teams.
I took special care of the packages that track upstream branches in our
git (with upstream-tree = tag in gbp.conf). They should all be OK.
If I broke something, I have forks of all salsa projects in my own
namespace.
Remaining To-Do: adjust our defaults in gem2deb, ./setup-project, etc.
(I will work on that, but I'd like to conclude the work on
debian/salsa-ci.yml and debian/.gitattributes first)
Remaining optional To-Dos:
- for each repository with additional branches, review them and cleanup
- further homogeneize debian/gbp.conf across packages, so that packages
that try to do the same have exactly the same file.
Lucas
Reply to: