Bug#711833: Preparing for RFS

[Yoann Gauthier]

Okay, no problem for the decision. Thanks for the details, because I had
understood the contrary.

Agree for the git repository [0]. If you agree, I can solve easy bugs. I
propose to assign bugs for each one.

Regards,

Yoann


2014-06-25 10:19 GMT+02:00 Alexander Alemayhu :

> On Wed, Jun 25, 2014 at 09:54:43AM +0200, Yoann Gauthier wrote:
> > Okay, I read the whole transcript and I understood the change from Git to
> > SVN.
> >
>
> This bug is closed. Not sure if you understood, but I decided not to
> change to
> SVN. Sorry for not including you in the decision and thanks for the work
> you
> have done in the package.
>
> > Just send me the repository adress. Thanks.
> >
>
> The package has been accepted into unstable and pere sponsored the upload.
> The
> current repository for the package is[0]. pere was kindly enough to push
> our
> changes there. I plan to look closer at the existing bug reports and try
> to fix
> them.
>
> [0]: git://git.debian.org/git/collab-maint/postr.git
>
> PS: Now that I am the maintainer. I am stopping ccing David about #711833.
>
> > Regards,
> >
> > Yoann
> >
> >
>

Bug#711833: Preparing for RFS

[Alexander Alemayhu]

On Wed, Jun 25, 2014 at 09:54:43AM +0200, Yoann Gauthier wrote:
> Okay, I read the whole transcript and I understood the change from Git to
> SVN.
> 

This bug is closed. Not sure if you understood, but I decided not to change to
SVN. Sorry for not including you in the decision and thanks for the work you
have done in the package.

> Just send me the repository adress. Thanks.
> 

The package has been accepted into unstable and pere sponsored the upload. The
current repository for the package is[0]. pere was kindly enough to push our
changes there. I plan to look closer at the existing bug reports and try to fix
them.

[0]: git://git.debian.org/git/collab-maint/postr.git

PS: Now that I am the maintainer. I am stopping ccing David about #711833.

> Regards,
> 
> Yoann
> 
> 


-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140625081913.ga85...@gmail.com

Bug#711833: Preparing for RFS

[Yoann Gauthier]

Okay, I read the whole transcript and I understood the change from Git to
SVN.

Just send me the repository adress. Thanks.

Regards,

Yoann


2014-06-24 20:50 GMT+02:00 Alexander Alemayhu :

> Hei Yoann,
>
> after sending the previous mail. I talked to pere and asked if he could
> look at
> the package.  The package looked good according to him. pere encouraged me
> to
> talk about postr on #debian-python.  Which I did and pere offered to
> sponsor the
> package, but the PAPT team did not seem to accept packages maintained in
> git
> currently. So I decided to change the maintainer instead of going back to
> the
> past and using SVN.  Below is a transcript from IRC to get the context:
>
> 17:13 < pere> ccscanf: hi.  what is the status of the postr package you
> are working on?
> 17:14 < ccscanf> I think it is ready for a sponsor.
> 17:18 < ScottK> barry: Here's another problem of that kind I ran across
> recently: https://github.com/bro/pysubnettree/pull/3/files
> 17:18 < ScottK> If I hadn't actually be regenerating the files during the
> build, I probably wouldn't have noticed.
> 17:20 < ccscanf> If anyone here can try the package, that would be nice.
> http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc
> 17:22 < pere> ccscanf: did you ask the python team for git repo hosting?
> 17:23 < paultag> hahaha
> 17:23 < paultag> no git for python team :)
> 17:23 < paultag> svn :)
> 17:23 < pere> aha.
> 17:23 < pere> I guess that is cleared, then. :)
> 17:24 < pere> ccscanf: I guess I'll push your github repo to the
> collab-maint repo, then?
> 17:25 < pere> ccscanf: btw, refresh my memory.  what is the status of the
> current postr maintainer David Paleino?
> 17:26 < ccscanf> pere: No. I have cc-ed David on most of my postr email,
> but he has not replied any.
> 17:26 < pere> ok.
> 17:26 < ScottK> FTR, it's no git without some work being done that no one
> seems to want to do.
> 17:26 < ccscanf> pere: Pushing to collab-maint would be nice. Thanks.
> 17:27 < paultag> ScottK: olasd did it
> 17:27 < paultag> ScottK: but no one commented or anything, I don't think
> 17:27 < paultag> git-buildpackage + mergeWithUpstream
> 17:27 < paultag> which is how I keep repos anyway
> 17:27 < ScottK> Really.
> 17:27 < paultag> so no
> 17:27 < paultag> Really!
> 17:27 < ScottK> I don't think that was all that was needed.
> 17:28 < ScottK> There was also the issue of how to make changes across a
> stack of repos or do partial branches of one large one.
> 17:28 < ScottK> p1otr: What was the list of stuff before we thought git
> was OK?
> 17:30 < pere> ccscanf: git pushed.
> 17:31 < pere> should
> http://anonscm.debian.org/gitweb/?p=collab-maint/postr.git or your github
> repo be the packaging repo?
> 17:32 < ccscanf> I think it is better to revert back to collab-maint for
> the Vcs-* fields.
> 17:33 < p1otr> ScottK:
> https://lists.debian.org/debian-python/2013/02/msg00123.html
> 17:34 < paultag> olasd: where's the set of git packages?
> 17:34 < paultag> if the consensus is try it out and get mindshare, I'll
> just start updating stuff in git.
> 17:35 < ccscanf> pere: I can make the change and push to the github repo.
> 17:35 < ScottK> p1otr: Thanks.
> 17:36 < ansgar> paultag: The last time Git was mentioned it ended in a
> flamefest. And the time before too...
> 17:36 < paultag> I love svn-buildpackage's workflow
> 17:36 < paultag> I hate git-buildpackage's default workflow
> 17:36 < ScottK> For git, I like git-dpm.
> 17:36 < paultag> I love git-buildpackage emulating svn-buildpackage's
> workflow
> 17:36 < paultag> so that's what i'll use.
> 17:37 < ansgar> paultag: What are the workflows? I use neither of them.
> 17:37 < paultag> git-buildpackage has this stupid idea upstream source
> should be in the repo
> 17:37 < paultag> svn-buildpackage just tracks debian, and merges that with
> pristine upstream
> 17:38 < ansgar> paultag: I just use git-sbuild which doesn't care if
> upstream source is present or not :>
> 17:38 < ccscanf> pere: git pushed.
> 17:39 < paultag> :)
> 17:49 < pere> ccscanf: time to upload?
> 17:50 < ccscanf> pere: If anyone is willing to sponsor, yes.
> 17:51 < barry> yeah, i've had better luck with git-dpm than
> git-buildpackage
> 17:51 < pere> perhaps someone from the python app team would like to do it?
> 17:52 < ScottK> If it's in Git, (ATM) it's not a team issue.
> 17:52 < pere> if no-one volunteer quickly, I'll upload it myself. :)
> 17:52 < pere> ScottK: what do you mean?  what is "a team issue"?
> 17:52 < ScottK> Team packages aren't in git.
> 17:53 < pere> is that a statement meaning packages in git are unwanted as
> team packages, or a statement meaning that so far no team maintained
> packages have been in git?
> 17:54 < ScottK> It's a statement that the team only has one repo.  For now
> that's in svn.  If we move to git, we'll (as described in the mail p1otr
> linked) move everything.
> 17:54 < ScottK> We don't want a split.
> 17:57 < pere> ccscanf: this confuses me, given tha

Bug#711833: Preparing for RFS

[Alexander Alemayhu]

Hei Yoann,

after sending the previous mail. I talked to pere and asked if he could look at
the package.  The package looked good according to him. pere encouraged me to
talk about postr on #debian-python.  Which I did and pere offered to sponsor the
package, but the PAPT team did not seem to accept packages maintained in git
currently. So I decided to change the maintainer instead of going back to the
past and using SVN.  Below is a transcript from IRC to get the context:

17:13 < pere> ccscanf: hi.  what is the status of the postr package you are 
working on?
17:14 < ccscanf> I think it is ready for a sponsor.
17:18 < ScottK> barry: Here's another problem of that kind I ran across 
recently: https://github.com/bro/pysubnettree/pull/3/files
17:18 < ScottK> If I hadn't actually be regenerating the files during the 
build, I probably wouldn't have noticed.
17:20 < ccscanf> If anyone here can try the package, that would be nice. 
http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc
17:22 < pere> ccscanf: did you ask the python team for git repo hosting?
17:23 < paultag> hahaha
17:23 < paultag> no git for python team :)
17:23 < paultag> svn :)
17:23 < pere> aha.
17:23 < pere> I guess that is cleared, then. :)
17:24 < pere> ccscanf: I guess I'll push your github repo to the collab-maint 
repo, then?
17:25 < pere> ccscanf: btw, refresh my memory.  what is the status of the 
current postr maintainer David Paleino?
17:26 < ccscanf> pere: No. I have cc-ed David on most of my postr email, but he 
has not replied any.
17:26 < pere> ok.
17:26 < ScottK> FTR, it's no git without some work being done that no one seems 
to want to do.
17:26 < ccscanf> pere: Pushing to collab-maint would be nice. Thanks.
17:27 < paultag> ScottK: olasd did it
17:27 < paultag> ScottK: but no one commented or anything, I don't think
17:27 < paultag> git-buildpackage + mergeWithUpstream
17:27 < paultag> which is how I keep repos anyway
17:27 < ScottK> Really.
17:27 < paultag> so no
17:27 < paultag> Really!
17:27 < ScottK> I don't think that was all that was needed.
17:28 < ScottK> There was also the issue of how to make changes across a stack 
of repos or do partial branches of one large one.
17:28 < ScottK> p1otr: What was the list of stuff before we thought git was OK?
17:30 < pere> ccscanf: git pushed.
17:31 < pere> should http://anonscm.debian.org/gitweb/?p=collab-maint/postr.git 
or your github repo be the packaging repo?
17:32 < ccscanf> I think it is better to revert back to collab-maint for the 
Vcs-* fields.
17:33 < p1otr> ScottK: 
https://lists.debian.org/debian-python/2013/02/msg00123.html
17:34 < paultag> olasd: where's the set of git packages?
17:34 < paultag> if the consensus is try it out and get mindshare, I'll just 
start updating stuff in git.
17:35 < ccscanf> pere: I can make the change and push to the github repo.
17:35 < ScottK> p1otr: Thanks.
17:36 < ansgar> paultag: The last time Git was mentioned it ended in a 
flamefest. And the time before too...
17:36 < paultag> I love svn-buildpackage's workflow
17:36 < paultag> I hate git-buildpackage's default workflow
17:36 < ScottK> For git, I like git-dpm.
17:36 < paultag> I love git-buildpackage emulating svn-buildpackage's workflow
17:36 < paultag> so that's what i'll use.
17:37 < ansgar> paultag: What are the workflows? I use neither of them.
17:37 < paultag> git-buildpackage has this stupid idea upstream source should 
be in the repo
17:37 < paultag> svn-buildpackage just tracks debian, and merges that with 
pristine upstream
17:38 < ansgar> paultag: I just use git-sbuild which doesn't care if upstream 
source is present or not :>
17:38 < ccscanf> pere: git pushed.
17:39 < paultag> :)
17:49 < pere> ccscanf: time to upload?
17:50 < ccscanf> pere: If anyone is willing to sponsor, yes.
17:51 < barry> yeah, i've had better luck with git-dpm than git-buildpackage
17:51 < pere> perhaps someone from the python app team would like to do it?
17:52 < ScottK> If it's in Git, (ATM) it's not a team issue.
17:52 < pere> if no-one volunteer quickly, I'll upload it myself. :)
17:52 < pere> ScottK: what do you mean?  what is "a team issue"?
17:52 < ScottK> Team packages aren't in git.
17:53 < pere> is that a statement meaning packages in git are unwanted as team 
packages, or a statement meaning that so far no team maintained packages have 
been in git?
17:54 < ScottK> It's a statement that the team only has one repo.  For now 
that's in svn.  If we move to git, we'll (as described in the mail p1otr 
linked) move everything.
17:54 < ScottK> We don't want a split.
17:57 < pere> ccscanf: this confuses me, given that the team is listed as the 
maintainer for postr in git.
17:58 < ccscanf> ScottK: How is that related? postr is a application not a 
module?
18:00 < pere> ccscanf: did you discuss postr on the team mailing list?
18:02 < ccscanf> pere: I mentioned it 
https://lists.debian.org/debian-python/2014/05/msg00125.html
18:03 < ScottK> pere: I think that's an error then.

Bug#711833: Preparing for RFS

[Alexander Alemayhu]

Hei Yoann,

I have fixed the autotools issues and tested them. It looks okay, we currently
only have one lintian tag left 'debian-watch-may-check-gpg-signature', but I
am not sure if / how we can fix it. 

We now use dh-python for the package, I followed this guide[0], since
python-support is obsolete. I have uploaded a new version to mentors. Should we
file a RFS bug report, or wait for a response from Germán Póo-Caamaño?

[0]: https://wiki.debian.org/Python/TransitionToDHPython2


-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140624165456.ga19...@gmail.com

Bug#711833: Preparing for RFS.

[Yoann Gauthier]

Hi,

Alexander and I, we are the new debian maintainer for postr package.

We have few questions for you :

- Concerning bug #585269
, have you
already fixed this in your vcs then we could just wait for a release which
should close that bug.
- When are you planning to make a new release ?

Thanks,

Regards,

Yoann Gauthier


2014-06-18 18:27 GMT+02:00 Alexander Alemayhu :

> On Wed, Jun 18, 2014 at 05:24:08PM +0200, Yoann Gauthier wrote:
> > Hello,
>
> Hei,
>
> >
> > I will contact Germán Póo-Caamaño tonight.
> >
>
> Good. Could you also ask when they are planning to make a new release?
> It would be nice to add a newer release, since the current release[0] has
> not
> updated the UI version name, but the change has been done in the vcs[1].
>
> [0]: https://download.gnome.org/sources/postr/0.13/
> [1]:
> https://git.gnome.org/browse/postr/commit/?id=ff74d96d0bbba657330c30f7a305aee2d743579e
>

Bug#711833: Preparing for RFS.

[Alexander Alemayhu]

On Wed, Jun 18, 2014 at 05:24:08PM +0200, Yoann Gauthier wrote:
> Hello,

Hei,

> 
> I will contact Germán Póo-Caamaño tonight.
> 

Good. Could you also ask when they are planning to make a new release?
It would be nice to add a newer release, since the current release[0] has not
updated the UI version name, but the change has been done in the vcs[1].

[0]: https://download.gnome.org/sources/postr/0.13/
[1]: 
https://git.gnome.org/browse/postr/commit/?id=ff74d96d0bbba657330c30f7a305aee2d743579e


-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140618162710.ga57...@gmail.com

Bug#711833: Preparing for RFS.

[Alexander Alemayhu]

On Mon, Jun 16, 2014 at 09:30:47AM +0200, Yoann Gauthier wrote:
> Hi,
> 

Hei,

> I will take care of bug #585269.
>  For that, I
> modify directly python source code or by patching ?
> 

I suggest contacting upstream. If upstream has already fixed this in their vcs
then we could just wait for a release which should close that bug. You could
proably fix it yourself with a patch, but that patch might just be unecessary
maintaince for us.


-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140616095057.ga36...@gmail.com

Bug#711833: Preparing for RFS.

[Alexander Alemayhu]

On Thu, Jun 12, 2014 at 09:14:09PM +0200, Yoann Gauthier wrote:
> Hello,
> 

Hei,

> I fixed lintian missing license error. I modified debian/copyright and
> debian/changelog, and pushed my modifications to postr repository.
> 
> New task ?

I have also fixed the autotools issues, but waiting to push until I have tested
my changes on several machines. Have you looked at the bugs[0] and seen if they 
are
resolved in the current version? Please keep in mind that some bugs are meant
for upstream and it might be hard to distinguish feature request and bug report.

PS: #637605 is probably already fixed.

[0]: https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=postr

> 
> Regards,
> 
> Yoann
> 
> 
> 2014-06-12 10:46 GMT+02:00 Yoann Gauthier :
> 
> > Thanks for your answer :).
> >
> > Regards,
> >
> > Yoann
> >
> >
> > 2014-06-12 10:25 GMT+02:00 Alexander Alemayhu :
> >
> > On Thu, Jun 12, 2014 at 09:16:28AM +0200, Yoann Gauthier wrote:
> >> > Hello,
> >> >
> >> > On Thu, Jun 12, 2014 at 12:22:25AM +0200, Yoann Gauthier wrote:
> >> > > > Hei,
> >> > > >
> >> > >
> >> > > Hei,
> >> > >
> >> > > > I created the new patch to fix license error reported by lintian.
> >> With
> >> > > this
> >> > > > new patch, I have an error during package-building : (sorry, it's in
> >> > > french)
> >> > > >
> >> > > > dpkg-source: info: construction de postr à partir de
> >> > > > ./postr_0.13.orig.tar.gz
> >> > > > patching file debian/copyright
> >> > > > Reversed (or previously applied) patch detected!  Skipping patch.
> >> > > > 1 out of 1 hunk ignored
> >> > > > dpkg-source: info: les décalages (« fuzz ») ne sont pas autorisés
> >> lors de
> >> > > > l'application des correctifs
> >> > > > dpkg-source: info: si le correctif
> >> > > > « 05-fix_missing_license_paragraph.patch » est correctement
> >> appliqué par
> >> > > > quilt, utiliser « quilt refresh » pour le mettre à jour
> >> > > > dpkg-source: erreur: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0
> >> -E -b
> >> > > -B
> >> > > > .pc/05-fix_missing_license_paragraph.patch/ --reject-file=- <
> >> > > >
> >> postr.orig.oMZtof/debian/patches/05-fix_missing_license_paragraph.patch a
> >> > > > produit une erreur de sortie de type 1
> >> > > >
> >> > > >
> >> > >
> >> > > Taking a quick look at your changes it looks like you have fuzz in the
> >> > > patches
> >> > > and according to dpkg fuzz is not allowed. Try updating the patch
> >> file.
> >> > >
> >> >
> >> > Okay I will fix the patch this evening by begin from scratch.
> >> > Otherwise, what is the rule for create a patch vs modify directly a
> >> file ?
> >> >
> >>
> >> Why are you using a patch file to update the debian/copyright? Remember
> >> you changed debian/changelog without a patch file. I think you can
> >> just modify it. patches are meant for the upstream source and the files in
> >> debian/ are not upstream but debian specific. Try not using a patch file
> >> for this. Good question.
> >>
> >> >
> >> > >
> >> > > Please do not push changes which are obviosly broken to the
> >> repository! It
> >> > > is
> >> > > much better if you do things locally and only push when you see it
> >> works as
> >> > > expected.
> >> > >
> >> >
> >> > Sorry for the repository, I removed my new patches from repository this
> >> > morning. The repository is clean (previous version before my commits).
> >> >
> >> >
> >> > >
> >> > > >
> >> > > > I don't understand why ? Do you have an idea ?
> >> > > >
> >> > > > Regards,
> >> > > >
> >> > > > Yoann
> >> > > >
> >> > > >
> >> > > > 2014-06-11 14:55 GMT+02:00 Alexander Alemayhu  >> >:
> >> > > >
> >> > > > > On Wed, Jun 11, 2014 at 01:56:59PM +0200, Yoann Gauthier wrote:
> >> > > > > > Hello,
> >> > > > > >
> >> > > > >
> >> > > > > Hei,
> >> > > > >
> >> > > > > > Okay, I will fix missing-license-paragraph-in-dep5-copyright
> >> gpl-3
> >> > > during
> >> > > > > > this week.
> >> > > > > >
> >> > > > > > To generate debian package you use : git-buildpackage ? And
> >> what is
> >> > > the
> >> > > > > > complete lintian command ?
> >> > > > > >
> >> > > > >
> >> > > > > Yes. git-buildpackage makes it easy to build a package. It also
> >> has
> >> > > some
> >> > > > > nice
> >> > > > > features like re-creating the upstream tarballs and much more. For
> >> > > lintian
> >> > > > > i run 'lintian -EvIL +pedantic'. I am not sure how
> >> mentors.debian.net
> >> > > does
> >> > > > > it.
> >> > > > >
> >> > > > > > Thanks,
> >> > > > > >
> >> > > > > > Yoann
> >> > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > 2014-06-10 23:04 GMT+02:00 Alexander Alemayhu <
> >> alexan...@bitraf.no>:
> >> > > > > >
> >> > > > > > > On Tue, Jun 10, 2014 at 09:15:49PM +0200, Yoann Gauthier
> >> wrote:
> >> > > > > > > > Hello,
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > > Hei,
> >> > > > > > >
> >> > > > > > > > I updated the changelog file as asked. Thanks for the push
> >> > > access,
> >> > > > > it's
> >> > > > > > > > easier for me to make changes now :).
> >>