Quoting Vasudev Kamath (kamathvasudev@gmail.com):
> Not a wizard but yes I can definitely have look. I moved fonts-droid as
> fonts-android into Git using the same method.
>
> Considering amount of packages we have problem is that this process is
> bandwidth hungry and I'm short of bandwidth and internet speed
> :-(. Can we use debian infrastructure (may be on alioth or some where
> else) to do this conversion. Can any one suggest any other alternative?
The conversion can be done on alioth, I think.
I do it on my build machine, then I just have to scp the final result
to alioth....but I'm lucky enough to not be short on bandwidth as you
can guess.
So, for sure, for people short in it, working on alioth is
fine. Indeed, the example in http://wiki.debian.org/Alioth/Git assumes
that the work is done there (indeed on git.debian.org, so namely on vasks.d.o
> May be we can have a wiki page or something like this where we can list
> all packages and mark who is moving which package to git so that we
> avoid duplication of work. I will try to generate this page.
This will definitely be appreciated, yes.
While doing that, I also make a few changes to packages: see recent
history in fonts-arabeyes:
* Update Standards to 3.9.4 (checked)
* Bump debhelper compatibility to 9
* Drop ttf-arabeyes transitional package
* Add "Multi-Arch: foreign" field
* Use "Breaks" instead of "Conflicts". Drop "Provides" as it is no
longer needed (installations should have transitioned since wheezy
and the package has anyway no reverse dependency.
* Use xz extreme compression for deb packages
* Use git for packaging: adapt Vcs-* fields
Attachment:
signature.asc
Description: Digital signature