Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

PAPT migrated to Git on Salsa

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

Contents

  PAPT migrated to Git on Salsa Stefano Rivera <stefanor@debian.org> - 2018-02-24 19:20 +0100
    Re: PAPT migrated to Git on Salsa Stefano Rivera <stefanor@debian.org> - 2018-02-24 23:00 +0100
      Re: PAPT migrated to Git on Salsa "W. Martin Borgert" <debacle@debian.org> - 2018-02-25 01:00 +0100
      Re: PAPT migrated to Git on Salsa Scott Kitterman <debian@kitterman.com> - 2018-02-25 01:10 +0100
    Re: PAPT migrated to Git on Salsa Stefano Rivera <stefanor@debian.org> - 2018-02-27 21:30 +0100
    Re: PAPT migrated to Git on Salsa Ondrej Novy <novy@ondrej.org> - 2018-02-27 21:40 +0100
    Re: PAPT migrated to Git on Salsa Hilmar Preuße <hille42@web.de> - 2018-05-08 21:30 +0200

#10202 — PAPT migrated to Git on Salsa

I've finished migrating PAPT to Salsa
https://salsa.debian.org/python-team/applications

There are probably some packages in there that aren't actually team
maintained any more. We should clean them up.

There were also a couple of failures not in the log during the
migration:
1. Packages that have never been uploaded aren't really in a useful
   state, yet (e.g. alienfeed)
2. A couple of packages are going to need some manual intervention:
   dreampie, gitinspector, vdirsyncer

Pushes to the SVN repository have been disabled.

SR

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

[toc] | [next] | [standalone]

#10203

Hi debian-python (2018.02.24_20:13:14_+0200)
> 1. Packages that have never been uploaded aren't really in a useful
>    state, yet (e.g. alienfeed)

These are the packages that aren't in sid (either never uploaded or
RMed):

{'alienfeed',
 'canto',
 'emesene',
 'episoder',
 'etm-qt',
 'fusion-icon',
 'glipper',
 'gmobilemedia',
 'google-sitemapgen',
 'harvestman',
 'hotssh',
 'indywiki',
 'kabikaboo',
 'kyklop',
 'mpdris',
 'oggconvert',
 'openerp7',
 'plainbox-provider-piglit',
 'pyaimt',
 'pybackpack',
 'pyicqt',
 'pyomo',
 'pypar2',
 'screenlets',
 'series60-remote',
 'topshelf',
 'trac-batchmodify',
 'trac-git',
 'turses',
 'upnp-inspector',
 'viridian',
 'wader',
 'zine'}

Shall we kill them all?

> 2. A couple of packages are going to need some manual intervention:
>    dreampie, gitinspector, vdirsyncer

Dealt with. Turns out dreampie is in the first set too, so just never
migrated it.

SR

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

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

#10204

On 2018-02-24 23:49, Stefano Rivera wrote:
>  'trac-batchmodify',
>  'trac-git',

The functionality of those two is now part of trac itself.
We might want to keep them for LTS purposes until they are not
part of any LTS release anymore. But I don't care much...

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

#10205

On Saturday, February 24, 2018 11:49:52 PM Stefano Rivera wrote:
> Hi debian-python (2018.02.24_20:13:14_+0200)
> 
> > 1. Packages that have never been uploaded aren't really in a useful
> > 
> >    state, yet (e.g. alienfeed)
> 
> These are the packages that aren't in sid (either never uploaded or
> RMed):
...
etm-qt: This is a binary package in sid as part of etm source (which is in 
papt).  This can go.

glipper: In stable
gmobilemedia: In stable
hotssh: In stable
pyaimt: In stable
pyicqt: In stable
pyomo: In stable
pypar2: In stable
screenlets: In stable
wader: In stable

> Shall we kill them all?

...

etm-qt and the ones not in Debian or only in oldoldstable (there were some of 
those) can definitely go.  I kind of think the ones that are in stable should 
stay, but don't feel strongly about it.

Scott K

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

#10211

Hi Ondrej (2018.02.27_22:17:56_+0200)
> Any reason why you didn't add entry into d/changelog about changing Vcs-*
> fields?

Because there wasn't a reasonable entity to attribute the change to. I
didn't review them (mostly).

And it was another source of potential failure during the migration.

SR

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

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

#10212

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

Hi,

2018-02-24 19:13 GMT+01:00 Stefano Rivera <stefanor@debian.org>:

> I've finished migrating PAPT to Salsa
> https://salsa.debian.org/python-team/applications


thanks a lot for working on this.

Any reason why you didn't add entry into d/changelog about changing Vcs-*
fields?

-- 
Best regards
 Ondřej Nový

Email: novy@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

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

#10510

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

On 24.02.2018 19:13, Stefano Rivera wrote:

Hi,

> I've finished migrating PAPT to Salsa
> https://salsa.debian.org/python-team/applications
> 
> There are probably some packages in there that aren't actually team
> maintained any more. We should clean them up.
> 
In my project (rubber) I find 4 branches after migration. The first 3
are explained on [1] and [2]. What about branch "svn"? Can I assume it
to be obsolete and simply kill it?

Thanks,
  Hilmar

[1] https://wiki.debian.org/Python/GitPackaging#git_workflows
[2] https://wiki.debian.org/Python/GitPackagingPQ#Git_Branch_Names
-- 
#206401 http://counter.li.org

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web