Re: Git migration schedule
On Sat, Oct 3, 2015 at 7:52 PM, Stefano Rivera <stefanor@debian.org> wrote:
> The errors:
>
> Cannot "git-dpm init" package: adhocracy
[8<]
> Cannot "git-dpm init" package: urlgrabber
those are 98 packages
> I think these are mostly because the package has never been uploaded to
> Debian, or has a new release staged, or has patch problems.
>
>
> Then:
> liblarch has
> Orphaned tag commit: b'935216b70ff944f4fdef508a3ad9a53ede9aff93' b'refs/tags/3.0-1'
> namebench has
> Orphaned tag commit: b'06ab8961db663cfd9002288ba098cd8aa523f81b' b'refs/tags/1.1+dfsg-1'
>
> These, I don't care about.
+ other 2
> We can't merge the svn head into master on:
> alembic
> pycryptopp
> pyme
> python-concurrent.futures
> python-django
> python-eventlet
> python-pip
> python-reportlab
> python-socksipy
and other 9, for a grand total of 109 packages that cannot be
converted to git, 13.5% of DPMT (oh, what about PAPT?)
am I the only one thinking it's quite a huge number to be handled by
hand? and whose hands will be the ones converting these packages?
yours or Barry's dont seem enough and others will need training/time.
Additionally, now we are in the middle of the 3.5 transition, and so
packages will need updating rather quickly: are we sure this is the
best time to push full throttle with the migration? I'd rather wait a
little bit longer and have a more automatic migration at a calmer
moment for python modules.
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: