Hi Diederik!
On 27/01/2023 21:23, Diederik de Haas wrote:
I did deliberately use 'version', while I'd normally use 'release' for these
type of bugs ;-)
:)
Your suggestion is entirely sensible and it does no harm to start with
the updated version as you say. I'm not sure there's any functionality
in recent commits to help with the mass conversion you describe, but it
does no harm.
In order to adopt 'id3lib' (src:id3lib3.8.3):
1) I need to learn about Subversion, which hopefully is a bit easier *for me*
as I had used and set up a Subversion server myself ...
but that was certainly >10 YEARS ago, possibly close to 20.
2) I had rightly *guessed* there was an archive and 'muon' kindly pointed me
to it ... the 'collab-maint' archive was (ofc) ~880 MB in size.
ick. I pulled some things out of largeish svn repos for other teams and
that was an unpleasant experience.
7) Actually do the conversion
my experience was that this was not easy in itself with quite a few
repos that were broken in some way, such as tags not being on branches,
main not being continuous in strange ways. Almost every time I've tried
it out, I've ended up running the process several times to improve the
config or the options used, or the git post-processing. For a couple of
packages, I decided to just ditch the svn repo and instead create a
fresh git repo with all the historical uploads using gbp import-dscs
--debsnap.
There are some people who did some mass conversions of repos (python
team, qt team for instance) - perhaps it is worth reaching out to them
to find out how they did it and if their scripts are available. That
might give you a head start. I don't recall who did these conversions
but mailing list discussions from around the time of the move to salsa
might help there, or just asking around on IRC.
So I've now concluded that it's probably best to propose a mass-migration of
the Alioth repos which haven't been converted yet (and uploaded to salsa).
And that the Debian QA group is likely the best place to propose that.
Hopefully there are also ppl there with more current Subversion knowledge and
maybe even with converting SVN to Git.
That's a huge task! That's definitely something to discuss on the
mailing list before you get too far into it. It would be worth
considering what to do with packages that are no longer in Debian at
all, for instance.
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
