Hi Steffen, On Fri, Dec 01, 2017 at 02:06:52PM +0100, Steffen Möller wrote: > > as you know we need to be prepared that when Alioth is moved to some new > > system SVN will not be available any more. So I was busy to migrate > > close to all our packages from SVN to Git. > > That was a tremendous effort.
Yes. :-P > Many thanks, Andreas. I am confident > the gitlab environment when it eventually comes will attract many > new contributions. I am confident this was worth it. I also think that using Git exlusively is an enhancement and that the fact that we are now forced to do the step is a positive thing. > > Close to all means we have > > the follwing remainings: > > > > r-cran-rlumshiny (Git repository created but I'd like to upload the > > latest version and some new dependencies are just > > missing) > > mgltools > This is on me. :-) > > My motivation for the latter is quite low due to the following reasons: > > > > * RC-buggy (#855494 :-() > This should have been addressed with that one upload of mine that apparently > had been lost before when the bug was addressed by upstream about two years > ago. But the program does not yet start. :-( > > * Inclear situation what is latest upstream > > ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855494#40 ) > Indeed. I even removed the Id "Sargis Dallakyan <sar...@scripps.edu>" from the Uploaders field since the address bounces. I have no idea whether we get continuous support from upstream (which does not seem to be the case considering that the download page keeps on pointing to a version which they claim outdated. :-( :-( :-( > > * I never liked the split of one upstream source into lots of SVN > > checkouts in different source packages. Those who are working on > > that set of packages need to do stupid repeated work for no good > > reason and I really regret that I added myself as Uploader which > > seems to be a good reason for other Uploaders to leave with this > > kind of boring work they introduced in the first place > Well. It is not _that_ easy since in general our ftpmasters like to have > this all separated. Erm, why? There is a *single* download tarball. Since when asks ftpmaster for separating its content? > > * My motivation is generally lower to work on non-free packages > > Well. Yes. Does this mean you volunteer to do the remaining SVN -> Git migrations and even more importantly fix bug #855494? If this bug is not fixed in a timely manner I'd vote for removal of the packages. (BTW, I also migrated some removed packages to keep the packaging history in case the packaging effort might be continued in the future - no idea whether you intent to do this.) Kind regards Andreas. PS: If the package should be kept we might ask upstream whether they might consider a free license to motivate others maintaining obviously orphaned software ... > > > > I would really love if somebody else would volunteer to take over these > > packages to migrate them from SVN to Git. The fact that somebody is > > willing to spent the time to work on the packages would be a proof that > > there is some real interest and we should not drop them at all. The > > migration process is described here > > > > https://debian-med.alioth.debian.org/docs/policy.html#subversion-to-git > > > > You need to patch the onvert_svn_2_git and replace > > > > export SVN_URL=svn://svn.debian.org/svn/debian-med/trunk/packages/ > > > > by > > > > export > > SVN_URL=svn://svn.debian.org/svn/debian-med/trunk/packages/mgltools > > > > since the packages are in a subdirectory. > > > > What else do I intend to migrate? > > > > We have several unfinished packaging stuff and I intend to check each > > single one whether it might make sense to move it to Git. Our tasks > > pages are displaying this information and I'd love to keep it but a > > general review makes probably sense. So we should be left with a > > basically empty SVN after the cleanup. Every hint about software which > > is worth moving to Git or simply can be removed from SVN would be > > welcome. > > > > BTW, since we now have removed nearly all existing packages I intend to > > remove the remaining dirs containing the README.status files to help > > keeping a better overview. Every interested developer should know how > > to find the new VCS location even without those README.status files. > > > > Kind regards > > > > Andreas. > > > -- http://fam-tille.de
