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+0000, 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+0000, 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 <becue@crans.org> 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
Attachment:
signature.asc
Description: PGP signature