Groups > linux.debian.maint.python > #7421 > unrolled thread

Git migration schedule

Started by	Barry Warsaw <barry@debian.org>
First post	2015-10-02 16:30 +0200
Last post	2015-10-22 10:30 +0200
Articles	20 on this page of 79 — 20 participants

Back to article view | Back to linux.debian.maint.python

  Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-02 16:30 +0200
    Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-02 22:50 +0200
      Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-02 23:10 +0200
      Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 11:50 +0200
        Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-03 12:50 +0200
          Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-03 16:30 +0200
            Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-03 17:00 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-03 20:10 +0200
          Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 21:00 +0200
            Re: Git migration schedule Daniele Tricoli <eriol@mornie.org> - 2015-10-03 21:50 +0200
              Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 22:30 +0200
            Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-04 21:10 +0200
              Re: Git migration schedule Julien Puydt <julien.puydt@laposte.net> - 2015-10-04 21:30 +0200
              Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-04 21:40 +0200
                Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-04 23:10 +0200
                  Re: Git migration schedule IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-05 12:10 +0200
                    Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-05 22:40 +0200
                      Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 23:30 +0200
                        Re: Git migration schedule IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2015-10-06 09:40 +0200
                Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 18:00 +0200
              Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-04 23:10 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:50 +0200
                Re: Git migration schedule Scott Kitterman <debian@kitterman.com> - 2015-10-05 18:30 +0200
                Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-06 02:40 +0200
                  Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-08 17:10 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 18:00 +0200
                Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 22:40 +0200
                Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-05 22:40 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:40 +0200
              Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:30 +0200
                Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 01:10 +0200
                  Re: Git migration schedule Ben Finney <ben+debian@benfinney.id.au> - 2015-10-10 03:20 +0200
                    Re: Git migration schedule Mattia Rizzolo <mattia@mapreri.org> - 2015-10-10 03:50 +0200
                    Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 04:40 +0200
                    Re: Git migration schedule Barry Warsaw <barry@python.org> - 2015-10-10 21:10 +0200
                      Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-11 10:30 +0200
                        Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-18 03:00 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:50 +0200
            Re: Git migration schedule Daniel Stender <debian@danielstender.com> - 2015-10-05 21:00 +0200
            Re: Git migration schedule Barry Warsaw <barry@python.org> - 2015-10-06 01:20 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-06 01:30 +0200
    Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-08 17:10 +0200
      Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-09 02:00 +0200
        Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:00 +0200
          Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:40 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-10 01:00 +0200
              Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-11 02:30 +0200
                Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-12 09:10 +0200
                Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-12 21:40 +0200
      Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:10 +0200
        Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-09 16:50 +0200
          Re: Git migration schedule Arthur de Jong <adejong@debian.org> - 2015-10-09 18:50 +0200
            Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-09 19:40 +0200
              Re: Git migration schedule Arthur de Jong <adejong@debian.org> - 2015-10-09 21:30 +0200
        Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:30 +0200
          Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-11 10:30 +0200
      Re: Git migration schedule pushback permissions/DEP-3 workflow Daniel Stender <debian@danielstender.com> - 2015-10-12 20:20 +0200
        Re: Git migration schedule pushback permissions/DEP-3 workflow Daniele Tricoli <eriol@mornie.org> - 2015-10-12 20:30 +0200
    Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:20 +0200
      Re: Git migration schedule IOhannes m zmölnig <zmoelnig@umlaeute.mur.at> - 2015-10-10 21:40 +0200
    Re: Git migration schedule Jean-Michel Vourgère <nirgal@debian.org> - 2015-10-18 22:10 +0200
      Re: Git migration schedule Piotr Ożarowski <piotr@debian.org> - 2015-10-18 23:10 +0200
      Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-19 19:20 +0200
        Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-19 23:40 +0200
          Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-21 10:00 +0200
        Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-19 23:40 +0200
          Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-20 16:10 +0200
            Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-21 09:40 +0200
              Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-21 16:50 +0200
                Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-21 23:40 +0200
                  Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-22 00:10 +0200
                    Re: Git migration schedule Sandro Tosi <sandro.tosi@gmail.com> - 2015-10-22 00:30 +0200
                      Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-22 09:20 +0200
                        Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-23 01:50 +0200
                      Re: Git migration schedule Julien Puydt <julien.puydt@laposte.net> - 2015-10-22 10:00 +0200
                        Re: Git migration schedule Piotr Ożarowski <piotr@debian.org> - 2015-10-22 10:10 +0200
                        pristine-tar (was: Git migration schedule) "W. Martin Borgert" <debacle@debian.org> - 2015-10-22 13:10 +0200
                          Re: pristine-tar (was: Git migration schedule) Barry Warsaw <barry@debian.org> - 2015-10-23 01:50 +0200
                      Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-22 10:30 +0200

Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →

#7449

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-04 23:10 +0200
Message-ID	<qfYHE-3u3-31@gated-at.bofh.it>
In reply to	#7445

Hi Sandro (2015.10.04_21:03:29_+0200)
> and other 9, for a grand total of 109 packages that cannot be
> converted to git, 13.5% of DPMT (oh, what about PAPT?)

They're all converted. There are just some remaining steps to do by
hand, to reconcile the SVN history with upstream history, and convert
patches to dpm.

> 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?

The maintainers. They'll have to learn dpm soon enough, anyway. Or a
team volunteer army. 10 people x 10 each, should be quick enough.

> 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.

Further automation is a *lot* more work. I don't think it's worth it.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#7461

From	Barry Warsaw <barry@debian.org>
Date	2015-10-05 17:50 +0200
Message-ID	<qggbw-3c7-5@gated-at.bofh.it>
In reply to	#7445

On Oct 04, 2015, at 08:03 PM, Sandro Tosi wrote:

>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.

I'm happy to pitch in if a maintainer needs help doing so.  I'd like to at
least capture the manual steps needed on the GitPackaging page.  I'm not sure
if there is enough commonality to make that worthwhile, but there might be.

>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.

Waiting longer isn't an option IMHO.  It's helping to add to the dysfunction
of the team.  I will also offer to help if the 3.5 transition gets stuck
because of the git conversion.

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

#7465

From	Scott Kitterman <debian@kitterman.com>
Date	2015-10-05 18:30 +0200
Message-ID	<qggOd-4bm-13@gated-at.bofh.it>
In reply to	#7461

On Monday, October 05, 2015 11:49:01 AM Barry Warsaw wrote:
> On Oct 04, 2015, at 08:03 PM, Sandro Tosi wrote:
> >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.
> 
> I'm happy to pitch in if a maintainer needs help doing so.  I'd like to at
> least capture the manual steps needed on the GitPackaging page.  I'm not
> sure if there is enough commonality to make that worthwhile, but there
> might be.
> >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.
> 
> Waiting longer isn't an option IMHO.  It's helping to add to the dysfunction
> of the team.  I will also offer to help if the 3.5 transition gets stuck
> because of the git conversion.

The first phase of the transition is almost done (92% or so), so I don't think 
that it's a valid reason to hold things up.  In fact, from a transition 
perspective, ~now is good so it can all be settled out before we want to make 
python3.5 default.

Scott K

[toc] | [prev] | [next] | [standalone]

#7488

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-06 02:40 +0200
Message-ID	<qgosq-6Pu-7@gated-at.bofh.it>
In reply to	#7461

[Multipart message — attachments visible in raw view] — view raw

On Tue, 6 Oct 2015 at 02:49 Barry Warsaw <barry@debian.org> wrote:

> Waiting longer isn't an option IMHO.  It's helping to add to the
> dysfunction
> of the team.  I will also offer to help if the 3.5 transition gets stuck
> because of the git conversion.
>

Hurry up and break my packages :-)

Do the Vcs-* headers in debian/control get updated automatically or do
these need to be updated manually? Looks like it gets updated
automatically. Good.

Maybe after the migration, add a check to lintian to check for obsolete
Vcs-*? Might ensure no accidents happen, e.g. with somebody building and
uploading from old subversion by mistake.

Thinking it might be good to have a list somewhere of packages that should
get manually checked (and where this hasn't happened yet) after the
migration is complete. Otherwise we might all assume somebody else has
checked a package, and it gets forgotten.

I guess I should look at my packages. They tend to be relatively simple,
don't expect any problems.

Just one problem(?) I do see, some of the commits corresponding to patches
have the following committer:

Stefano Rivera <stefano@rivera.za.net>

e.g.

https://anonscm.debian.org/cgit/python-modules/svn-migration/django-tables.git/commit/?id=17afaee37dc0be9d40ba5bdd1af8f254ef42a46a

from:

https://anonscm.debian.org/cgit/python-modules/svn-migration/django-tables.git/

This looks like a mistake to me, Stefano didn't contribute these changes.
Suspect it might be a default used because there was no author information
in the original debian/patches/* file.

[toc] | [prev] | [next] | [standalone]

#7562

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-08 17:10 +0200
Message-ID	<qhkZs-76Q-25@gated-at.bofh.it>
In reply to	#7488

Hi Brian (2015.10.06_02:29:35_+0200)
> Thinking it might be good to have a list somewhere of packages that should
> get manually checked (and where this hasn't happened yet) after the
> migration is complete. Otherwise we might all assume somebody else has
> checked a package, and it gets forgotten.

Yeah, I'd like us to quickly sprint through them, too.

> Just one problem(?) I do see, some of the commits corresponding to patches
> have the following committer:
> 
> Stefano Rivera <stefano@rivera.za.net>
...
> Suspect it might be a default used because there was no author information
> in the original debian/patches/* file.

Good catch. I think I fixed that in a652cb2

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#7463

From	Barry Warsaw <barry@debian.org>
Date	2015-10-05 18:00 +0200
Message-ID	<qgglc-3nE-9@gated-at.bofh.it>
In reply to	#7445

On Oct 04, 2015, at 08:03 PM, Sandro Tosi wrote:

>and other 9, for a grand total of 109 packages that cannot be
>converted to git, 13.5% of DPMT (oh, what about PAPT?)

I've wondered about PAPT too.  I don't touch those nearly as often, but
eventually yes, they should come under the same vcs regime, IMHO.

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

#7470

From	Barry Warsaw <barry@debian.org>
Date	2015-10-05 22:40 +0200
Message-ID	<qgkIa-1ks-9@gated-at.bofh.it>
In reply to	#7463

On Oct 05, 2015, at 10:32 PM, Stefano Rivera wrote:

>Hi Barry (2015.10.05_17:51:41_+0200)
>> >and other 9, for a grand total of 109 packages that cannot be
>> >converted to git, 13.5% of DPMT (oh, what about PAPT?)
>> 
>> I've wondered about PAPT too.  I don't touch those nearly as often, but
>> eventually yes, they should come under the same vcs regime, IMHO.
>
>One step at a time. The same scripts should work, with minimal tweaks :)

Oh for sure!  There's no deadline on "eventually" :)

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

#7471

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-05 22:40 +0200
Message-ID	<qgkIa-1ks-11@gated-at.bofh.it>
In reply to	#7463

Hi Barry (2015.10.05_17:51:41_+0200)
> >and other 9, for a grand total of 109 packages that cannot be
> >converted to git, 13.5% of DPMT (oh, what about PAPT?)
> 
> I've wondered about PAPT too.  I don't touch those nearly as often, but
> eventually yes, they should come under the same vcs regime, IMHO.

One step at a time. The same scripts should work, with minimal tweaks :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#7460

From	Barry Warsaw <barry@debian.org>
Date	2015-10-05 17:40 +0200
Message-ID	<qgg1R-30J-37@gated-at.bofh.it>
In reply to	#7441

On Oct 03, 2015, at 08:52 PM, Stefano Rivera wrote:

>No significant failures, but I wanted to setup an mr config, which I've done
>now:
>https://anonscm.debian.org/cgit/python-modules/svn-migration/python-modules.git/
>The pkg-perl team has fancier tools, but they require more bookkeeping, so I
>mostly cribbed from the pkg-ruby-extras team.

Is there some documentation on how to use these scripts, or set up mr?  Or
would that be obvious for anybody who's used mr before?

Can you add something about mr to https://wiki.debian.org/Python/GitPackaging
?

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

#7580

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-09 10:30 +0200
Message-ID	<qhBdV-54V-33@gated-at.bofh.it>
In reply to	#7460

Hi Barry (2015.10.05_17:36:05_+0200)
> Is there some documentation on how to use these scripts, or set up mr?  Or
> would that be obvious for anybody who's used mr before?

Fairly obvious. It's pretty simple.

> Can you add something about mr to https://wiki.debian.org/Python/GitPackaging

Here: https://wiki.debian.org/Python/GitPackaging#Where_do_the_team.27s_git_branches_live.3F

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#7590

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-10 01:10 +0200
Message-ID	<qhOXv-81U-1@gated-at.bofh.it>
In reply to	#7580

[Multipart message — attachments visible in raw view] — view raw

On Fri, 9 Oct 2015 at 19:26 Stefano Rivera <stefanor@debian.org> wrote:

>
> Here:
> https://wiki.debian.org/Python/GitPackaging#Where_do_the_team.27s_git_branches_live.3F
>
>
I seem to have problems with this because my username on my local box is
"brian" however my username on git.debian.org is "bam". There doesn't
appear to be an easy way of overriding it.

I seem to recall git supports rewriting URLs, maybe this is the way to go
here? Lets see if I can find that blog post aimed at Debian developers
again...

[toc] | [prev] | [next] | [standalone]

#7591

From	Ben Finney <ben+debian@benfinney.id.au>
Date	2015-10-10 03:20 +0200
Message-ID	<qhQZk-2sY-13@gated-at.bofh.it>
In reply to	#7590

Brian May <brian@microcomaustralia.com.au> writes:

> On Fri, 9 Oct 2015 at 19:26 Stefano Rivera <stefanor@debian.org> wrote:
>
> >
> > Here:
> > https://wiki.debian.org/Python/GitPackaging#Where_do_the_team.27s_git_branches_live.3F
>
> I seem to have problems with this because my username on my local box is
> "brian" however my username on git.debian.org is "bam". There doesn't
> appear to be an easy way of overriding it.

You need to specify which username to connect to over SSH. I have
updated the Wiki page above to clarify this.

Now that you already have the remote configured, you can re-configure it
with:

    $ git remote set-url origin git+ssh://USERNAME@git.debian.org/git/python-modules/tools/python-modules.git

where “origin” is the name of the remote, and “USERNAME” is your Alioth
username.

-- 
 \         “When we pray to God we must be seeking nothing — nothing.” |
  `\                                                —Francis of Assisi |
_o__)                                                                  |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#7592

From	Mattia Rizzolo <mattia@mapreri.org>
Date	2015-10-10 03:50 +0200
Message-ID	<qhRsm-309-3@gated-at.bofh.it>
In reply to	#7591

[Multipart message — attachments visible in raw view] — view raw

On Sat, Oct 10, 2015 at 12:18:20PM +1100, Ben Finney wrote:
> Brian May <brian@microcomaustralia.com.au> writes:
> 
> > On Fri, 9 Oct 2015 at 19:26 Stefano Rivera <stefanor@debian.org> wrote:
> >
> > >
> > > Here:
> > > https://wiki.debian.org/Python/GitPackaging#Where_do_the_team.27s_git_branches_live.3F
> >
> > I seem to have problems with this because my username on my local box is
> > "brian" however my username on git.debian.org is "bam". There doesn't
> > appear to be an easy way of overriding it.
> 
> You need to specify which username to connect to over SSH. I have
> updated the Wiki page above to clarify this.
> 
> Now that you already have the remote configured, you can re-configure it
> with:
> 
>     $ git remote set-url origin git+ssh://USERNAME@git.debian.org/git/python-modules/tools/python-modules.git
> 
> where “origin” is the name of the remote, and “USERNAME” is your Alioth
> username.

You can also add a snipped like mine to ~/.ssh/config:

Host alioth svn.debian.org git.debian.org bzr.debian.org hg.debian.org darcs.debian.org arch.debian.org anonscm.debian.org
    HostName alioth.debian.org
    User mapreri-guest


so you avoid fiddling with every git remote.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[toc] | [prev] | [next] | [standalone]

#7593

From	Brian May <brian@microcomaustralia.com.au>
Date	2015-10-10 04:40 +0200
Message-ID	<qhSeJ-4gR-3@gated-at.bofh.it>
In reply to	#7591

[Multipart message — attachments visible in raw view] — view raw

On Sat, 10 Oct 2015 at 12:18 Ben Finney <ben+debian@benfinney.id.au> wrote:

> Now that you already have the remote configured, you can re-configure it
> with:
>
>     $ git remote set-url origin git+ssh://
> USERNAME@git.debian.org/git/python-modules/tools/python-modules.git
>
> where “origin” is the name of the remote, and “USERNAME” is your Alioth
> username.
>

Insufficient.   .mrconfig in the repository contains a reference to the URL
without the username.

I tried updating the repository in .mrconfig.  Curiously, a quick-update
reverted the URL back to the original value, and then deleted all the
repositories from file. Which seems just a little bit weird. Maybe when I
get to know mr better I will be able to understand just what happened.

I didn't even think of doing it via ssh configuration, as per Mattia's
suggestion. I think that might be a better option.

[toc] | [prev] | [next] | [standalone]

#7601

From	Barry Warsaw <barry@python.org>
Date	2015-10-10 21:10 +0200
Message-ID	<qi7GP-1wO-27@gated-at.bofh.it>
In reply to	#7591

[Multipart message — attachments visible in raw view] — view raw

On Oct 10, 2015, at 12:18 PM, Ben Finney wrote:

>You need to specify which username to connect to over SSH. I have
>updated the Wiki page above to clarify this.

Hmm, I'm not sure about this recommendation.  I don't include my user name in
the url, and I'm pretty sure Mattia's suggestion to set this in your
~/.ssh/config is the right one.

I don't want to wiki-churn so what do you think about backing out this change
and suggesting the ssh config instead?

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

#7610

From	Stefano Rivera <stefanor@debian.org>
Date	2015-10-11 10:30 +0200
Message-ID	<qikaZ-2Me-1@gated-at.bofh.it>
In reply to	#7601

Hi Barry (2015.10.10_21:02:00_+0200)
> I don't want to wiki-churn so what do you think about backing out this change
> and suggesting the ssh config instead?

I'd suggest ssh config too. +1.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#7681

From	Sandro Tosi <morph@debian.org>
Date	2015-10-18 03:00 +0200
Message-ID	<qkKum-5Ta-1@gated-at.bofh.it>
In reply to	#7610

On Sun, Oct 11, 2015 at 9:26 AM, Stefano Rivera <stefanor@debian.org> wrote:
> Hi Barry (2015.10.10_21:02:00_+0200)
>> I don't want to wiki-churn so what do you think about backing out this change
>> and suggesting the ssh config instead?
>
> I'd suggest ssh config too. +1.

+1 on .ssh/config, I'm gonna change it now

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

[toc] | [prev] | [next] | [standalone]

#7462

From	Barry Warsaw <barry@debian.org>
Date	2015-10-05 17:50 +0200
Message-ID	<qggbw-3c7-23@gated-at.bofh.it>
In reply to	#7441

On Oct 03, 2015, at 08:52 PM, Stefano Rivera wrote:

>So, here is a migration at r34461:
>https://anonscm.debian.org/cgit/python-modules/svn-migration/
>
>The errors:

Some of these may already be in git, and hopefully git-dpm so don't actually
need a conversion.  If it's in git but not git-dpm, it's fairly easy to
bootstrap, though perhaps with less history, but fully functional going
forward.

I've not done a full review of this list, but the ones I know about are (sorry
Piotr ;):

>Cannot "git-dpm init" package: pycurl
>Cannot "git-dpm init" package: python-pip

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

#7469

From	Daniel Stender <debian@danielstender.com>
Date	2015-10-05 21:00 +0200
Message-ID	<qgj9o-7qa-13@gated-at.bofh.it>
In reply to	#7441

Hi,

these old SVN repos could be spared and removed:

On 03.10.2015 20:52, Stefano Rivera wrote:
> The errors:
> 
> Cannot "git-dpm init" package: gamera

is already in: git://anonscm.debian.org/python-modules/packages/gamera.git

> Cannot "git-dpm init" package: nltk

old/obsolete packaging, the initial Debian package was uploaded for Debian Science

> Cannot "git-dpm init" package: svg.path

got into: http://anonscm.debian.org/cgit/python-modules/packages/python-svg.path.git
before the initial upload

and

> Cannot "git-dpm init" package: pyuca

... is currently in NEW. I'll convert that manually.

Cheers,
DS

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/

[toc] | [prev] | [next] | [standalone]

#7485

From	Barry Warsaw <barry@python.org>
Date	2015-10-06 01:20 +0200
Message-ID	<qgnd0-57y-11@gated-at.bofh.it>
In reply to	#7441

[Multipart message — attachments visible in raw view] — view raw

On Oct 03, 2015, at 08:52 PM, Stefano Rivera wrote:

>So, here is a migration at r34461:
>https://anonscm.debian.org/cgit/python-modules/svn-migration/

I did an update (not uploaded) of webob from this migration and it worked
perfectly.  But it's a simple package without patches.  I'll try a few more.

Cheers,
-Barry

[toc] | [prev] | [next] | [standalone]

Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →

csiph-web

Git migration schedule

Contents

#7449

#7461

#7465

#7488

#7562

#7463

#7470

#7471

#7460

#7580

#7590

#7591

#7592

#7593

#7601

#7610

#7681

#7462

#7469

#7485