[Blends-commit] svn to git

[Andreas Tille]

[cc to the list in case somebody else might wonder as well about my
 recent activities]

Hi,

On Thu, Oct 25, 2012 at 07:17:56PM +0900, Charles Plessy wrote:
> Le Thu, Oct 25, 2012 at 09:33:53AM -0000, tille at users.alioth.debian.org a écrit :
> > Author: tille
> > Date: Thu Oct 25 09:33:52 2012
> > New Revision: 3620
> > 
> > URL: http://svn.debian.org/wsvn/blends/?sc=1&rev=3620
> > Log:
> > Reconstructed d/control for 0.7
> 
> are you doing tediously something that can be automated ?

No. :-)

> I have experience with conversion following the instructions
> on the Debian wiki.  Please let me know if you want some help.
> 
> http://wiki.debian.org/Alioth/Git#Convert_a_SVN_Alioth_repository_to_Git

Thanks for the offer to help.  My plan was to get things in SVN which
should have been there but were not for ... well, lets say unexperienced
beginners failures back then.  The files I had commited recently
(debian/control files) were never commited to SVN because I considered
them autogenerated and thus uninteresting.  At some point in time I was
pointed out by Debian Edu people they are not and I agreed.  I'm now
trying to fix previous error for the only reason that I would like to
create more detailed statistics about Debian Med development.  I have
choosen this point in time to have a useful Git archive right from the
beginning.

Explanation for what statistics I'm hunting for:  3d barplot using

   x - time
   y - task
   z - number of packages in task y at time x

I wrote a script (blends/trunk/team_analysis_tools/count-dependencies.py)
that fetches these data and I will enhance it to also parse Git in the
future - but it just needs some data commited to Vcs and I was filling
the gaps I introduced myself back than.  Not very clean - but I do not
see any harm this could create.

BTW, these commits will end now - I will create a single data file
with the statistics of the older metapackages which have a different
structure anyway.

Regarding the migration itself:  I think I will not start migrating any
source package from project/<BLEND> to Git before Wheezy is released.
The rationale is that I plan to recreate the metapackages based on the
actual status of the package pool (perhaps mid November) and I do not
want to fiddle around with more changes than needed - so leaving the Vcs
fields as they are seems reasonable to me.  I will drop some note at the
old location anyway - so the fact that Wheeze will ship with Vcs fields
that might become outdated soonish should be no real problem IMHO.

Kind regards

      Andreas.

-- 
http://fam-tille.de