Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

2016-12-30 Thread Pierre-Elliott Bécue
Le mardi 27 décembre 2016 à 22:11:38+, Sean Whitton a écrit :
> Hello Pierre,
> 
> On Tue, Dec 27, 2016 at 06:04:58PM +0100, Pierre-Elliott Bécue wrote:
> > Le lundi 26 décembre 2016 à 20:38:42+, Sean Whitton a écrit :
> > > control: tag -1 +moreinfo
> > > 
> > > Dear Pierre,
> > > 
> > > Thank you for your interest in adopting this package.
> > > 
> > > Unfortunately, your work has not been properly integrated with what is
> > > already in Debian:
> > > 
> > > - you marked version 0.4.74-4 as released but it was never uploaded
> > 
> > True. Yet, it is in the team repo.
> 
> The changelog tracks the Debian archive.  You should merge the existing
> 0.4.74-4 changelog entry with your changes.

0.4.74-4 is not in the debian archive, only in the team repo. How should I
merge exactly?

> > 
> > Actually, it is included. The commit is just hidden in the history of the
> > team git repository for an unknown reason. See commit
> > 53434cf161a64ab9ac1578fec3613cce20ed451b and merge commit
> > 6fd4d560cf1f1f25a581a28a3c0a93ebd3159386. I added manually the changelog
> > that has been truncated in the merge.
> 
> Sorry, my fault, thanks for fixing up the changelog in your upload.

No worries, you're welcome. :)

> > > - your work is not pushed to the team git repository
> > 
> > I have no permission to push.
> 
> Have you asked to join the team?

I don't feel that I've done enough to get permissions, maybe my
interpretation is wrong.

-- 
PEB


signature.asc
Description: PGP signature


Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

2016-12-30 Thread Sean Whitton
Hello Pierre,

On Thu, Dec 29, 2016 at 09:20:02PM +0100, Pierre-Elliott Bécue wrote:
> Le mardi 27 décembre 2016 à 22:11:38+, Sean Whitton a écrit :
> > Hello Pierre,
> > 
> > On Tue, Dec 27, 2016 at 06:04:58PM +0100, Pierre-Elliott Bécue wrote:
> > > Le lundi 26 décembre 2016 à 20:38:42+, Sean Whitton a écrit :
> > > > control: tag -1 +moreinfo
> > > > 
> > > > Dear Pierre,
> > > > 
> > > > Thank you for your interest in adopting this package.
> > > > 
> > > > Unfortunately, your work has not been properly integrated with what is
> > > > already in Debian:
> > > > 
> > > > - you marked version 0.4.74-4 as released but it was never uploaded
> > > 
> > > True. Yet, it is in the team repo.
> > 
> > The changelog tracks the Debian archive.  You should merge the existing
> > 0.4.74-4 changelog entry with your changes.
> 
> 0.4.74-4 is not in the debian archive, only in the team repo. How should I
> merge exactly?

This is roughly what I have in mind:

pyvtk (0.5.18-1) unstable; urgency=low

  [ Jakub Wilk ]
  * Use canonical URIs for Vcs-* fields.
  * Remove obsolete Conflicts/Replaces with python2.3-pyvtk and
python2.4-pyvtk.

  [ Stefano Rivera ]
  * Convert inline patch to 3.0 (quilt) to ease git-dpm migration.

  [ Ondřej Nový ]
  * Fixed VCS URL (https)

  [ Pierre-Elliott Bécue ]
  * New maintainer (Closes: #795017).
  * New upstream release
  * Uses pybuild for building the package.
  * Cleaning debian/*

 -- Pierre-Elliott Bécue   Sat, 17 Dec 2016 00:24:15 +0200

> > > > - your work is not pushed to the team git repository
> > > 
> > > I have no permission to push.
> > 
> > Have you asked to join the team?
> 
> I don't feel that I've done enough to get permissions, maybe my
> interpretation is wrong.

I see what you mean, and every Debian team is different.

However, chances are they would prefer that you join the team and push
your git history there, as then other team members can more easily build
upon your work.

So please submit a request, explaining that you want to work on pyvtk.
If they say no, it's not a big deal!

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

2016-12-27 Thread Sean Whitton
Hello Pierre,

On Tue, Dec 27, 2016 at 06:04:58PM +0100, Pierre-Elliott Bécue wrote:
> Le lundi 26 décembre 2016 à 20:38:42+, Sean Whitton a écrit :
> > control: tag -1 +moreinfo
> > 
> > Dear Pierre,
> > 
> > Thank you for your interest in adopting this package.
> > 
> > Unfortunately, your work has not been properly integrated with what is
> > already in Debian:
> > 
> > - you marked version 0.4.74-4 as released but it was never uploaded
> 
> True. Yet, it is in the team repo.

The changelog tracks the Debian archive.  You should merge the existing
0.4.74-4 changelog entry with your changes.

> > - you haven't included the NMU 0.4.74-3.1
> 
> Actually, it is included. The commit is just hidden in the history of the
> team git repository for an unknown reason. See commit
> 53434cf161a64ab9ac1578fec3613cce20ed451b and merge commit
> 6fd4d560cf1f1f25a581a28a3c0a93ebd3159386. I added manually the changelog
> that has been truncated in the merge.

Sorry, my fault, thanks for fixing up the changelog in your upload.

> > - your work is not pushed to the team git repository
> 
> I have no permission to push.

Have you asked to join the team?

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

2016-12-27 Thread Pierre-Elliott Bécue
Le lundi 26 décembre 2016 à 20:38:42+, Sean Whitton a écrit :
> control: tag -1 +moreinfo
> 
> Dear Pierre,
> 
> Thank you for your interest in adopting this package.
> 
> Unfortunately, your work has not been properly integrated with what is
> already in Debian:
> 
> - you marked version 0.4.74-4 as released but it was never uploaded

True. Yet, it is in the team repo.

> - you haven't included the NMU 0.4.74-3.1

Actually, it is included. The commit is just hidden in the history of the
team git repository for an unknown reason. See commit
53434cf161a64ab9ac1578fec3613cce20ed451b and merge commit
6fd4d560cf1f1f25a581a28a3c0a93ebd3159386. I added manually the changelog
that has been truncated in the merge.

> - your work is not pushed to the team git repository

I have no permission to push.

-- 
PEB


signature.asc
Description: PGP signature


Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

2016-12-26 Thread Sean Whitton
control: tag -1 +moreinfo

Dear Pierre,

Thank you for your interest in adopting this package.

Unfortunately, your work has not been properly integrated with what is
already in Debian:

- you marked version 0.4.74-4 as released but it was never uploaded

- you haven't included the NMU 0.4.74-3.1

- your work is not pushed to the team git repository

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#848416: RFS: pyvtk/0.5.18-1 [ITA]

2016-12-17 Thread Pierre-Elliott Bécue
Package: sponsorship-requests
Severity: normal

Dear mentors,

This RFS is linked to an ITA. See bug #795017
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795017) for more
information regarding this package.

I am looking for a sponsor for my package "pyvtk"

 * Package name: pyvtk
   Version : 0.5.18-1
   Upstream Author : Pearu Peterson 
 * URL : https://github.com/pearu/pyvtk
 * License : BSD-3-Clause
   Section : python

It builds those binary packages:

 * python-pyvtk - Module for manipulating VTK files
 * python3-pyvtk - Module for manipulating VTK files - Python3 library

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/pyvtk

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/p/pyvtk/pyvtk_0.5.18-1.dsc

Changes since the last upload (extracted from NEWS.txt written by the author of
the library):

 * Added Python 3 support (thanks to Thomas Kluyver).
 * Maintain the package (thanks to Thomas Kluyver and David Froger).
 * Development is moved under Github.

Regards,

-- 
Pierre-Elliott Bécue