Hi Stuart! On Friday, 27 January 2023 04:40:47 CET Stuart Prescott wrote: > On 27/01/2023 09:17, Diederik de Haas wrote: > > Package: svn-all-fast-export > > Version: 1.0.18+git20200501-1 > > Severity: wishlist > > > > It would be great if the latest version could be packaged for Debian. > > I recently had the need to retrieve a repo from the alioth archive and > > convert it to git. And this sounds like a great tool for that where > > upstream has even worked on the code in the last couple of years ;-) > > > > Anything that could make that task easier would be appreciated and a > > newer version of svn-all-fast-export may just help. > > Upstream doesn't often make releases and so the "new upstream" > notification from the watch file is only about new commits being made to > the upstream repo, not a new version being available.
I did deliberately use 'version', while I'd normally use 'release' for these type of bugs ;-) > Most of the recent upstream activity has been about CI on GitHub and not > actual changes to the package. Yep, I did see that. But I did see there were also non-GH-CI related commits. I filed the bug for 2 reasons: - I think it's generally good to have the latest release/version in for the next Stable release (and I assumed it wouldn't be too difficult in this case). - What I described in the initial report and will expand on below ... > Is there anything in the recent commits that would help you? I hadn't > seen anything to justify updating the package but if there's something > specific, please say and we can do it. TL;DR: I lack the knowledge to determine that, so I don't *know*. If you determine there isn't anything useful, feel free to close this bug. I'll (very) likely try to make the issue(s) I ran into wider and send a mail about it to the debian-qa ML, but (the long version is) ... 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. 3) I did know about (TurtoiseSVN and) kdesvn and I found out (yesterday) that I could indeed see the repo, which hopefully will help a bit 4) Then the big thing: I want/need to convert it to git and I (highly) prefer if I can restore as much of its history as possible. But I don't know which tools are available and which are in a decent enough shape, hence why I used 'recent commits' as a criteria. I generally think using CI is a good thing, but also concluded that the recent GH CI commits were irrelevant for my purpose. But I completely lack the knowledge to evaluate the commits that were done before those. They may be irrelevant, but the issue is: I don't *know*. 5) I already learned I should (try to) create some mapping file to translate svn committers into git committers. And that I need to learn about the configuration file I should give to svn-all-fast-export as it (apparently) needs more info to make the conversion to git. 6) I should probably do the same for other svn-to-git-conversion-tools precisely as I don't know how good one tools is, which IIUC also depends on how SVN was used ... 7) Actually do the conversion 8) Upload it to salsa, which should be easy. 9) Oh wait, yeah, I almost forgot: the goal was to potentially adopt a package, so actually do something with the package ;-P And all that to potentially adopt 1 package! And everyone who thinks about adopting a package which was previously stored on Alioth, will have to go through that too. And I have previous knowledge about SVN, a reasonably fast internet connection which is (AFAIK) also unmetered/unlimited, which not everyone has. Any sane person would've long bailed out, likely already at step 1;-) 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. But it would still be useful if the potential tools for that are in the best shape possible, so having the latest commit(s) of svn-all-fast-export packaged *may* be useful. But as said before: I lack the knowledge to determine that. Regards, Diederik
signature.asc
Description: This is a digitally signed message part.
