Hi,
We had many packages that were not uploaded for a long time. They were
migrated to Salsa, but this did not reflect in the version currently in
unstable.
Using UDD's Salsa dashboard[1] (which I improved while working on this), I
ensured that:
1/ All our packages in unstable have a Vcs field pointing to their
repository on Salsa. This mainly required doing an upload of the current
state of the Git repo of each package. I reviewed changes (the best I
could), but did not try to make any further improvement to the package,
so sometimes what I uploaded is already a bit behind in terms of
practices.
2/ All our packages use pristine-tar
3/ All our packages have Issues *disabled*, MRs enabled, Jobs enabled on
Salsa.
4/ All our packages have similar CI configuration (use
debian/salsa-ci.yml with the two includes)
[1] https://udd.debian.org/salsa/?email1=pkg-ruby-extras-maintainers%40lists.alioth.debian.org&format=html&branches=on&gitlabci=on&gbpconf=on&pipeline=on#results
Future work on related topics include:
1/ deal with the few remaining exceptions:
1.1/ larch package (removal behind discussed)
1.2/ packages maintained by the team (according to Maintainer field)
but not maintained in the ruby-team salsa group
2/ check pristine-tar branches. I ran into some cases where the state of
the pristine-tar branch did not match what was in unstable
3/ check open merge requests
4/ check debian/salsa-ci.yml. Some custom configurations (variables)
look wrong (such as disabling some jobs that don't need to be disabled)
5/ discuss whether we should change the way we configure CI. I wonder if
it would make sense to have a team-specific include, that would itself
include the salsa-ci's team ones. That would allow for centrally
changing some stuff.
6/ do some cleanup. Many packages have failing salsa-ci pipelines for
various reasons.
7/ standardize/homogenize debian/gbp.conf and debian/.gitattributes
8/ check for salsa projects in the ruby-team group that don't have
corresponding packages in instable/experimental. Investigate and maybe
archive the project.
9/ DEP-14
I will work on some of the topics above, but help is welcomed of course
Lucas
Attachment:
signature.asc
Description: PGP signature