Bug#858303: RFP: cilium -- BPF & XDP for containers

[Alexander Alemayhu]

Package: wnpp
Severity: wishlist

* Package name: cilium
  Upstream Author : Authors of Cilium
* URL : https://github.com/cilium/cilium/
* License : The cilium user space components are licensed under the
Apache License, Version 2.0. The BPF code templates are licensed under the
General Public License, Version 2.0.
  Programming Lang: Go
  Description : Cilium provides fast in-kernel networking and security
policy enforcement for containers based on eBPF programs generated on the fly.
It is an experimental project aiming at enabling emerging kernel technologies
such as BPF and XDP for containers.

Information above from upstream repository.

Thanks.

-- 
Mit freundlichen Grüßen

Alexander Alemayhu

Bug#728194: enemylines7 -- first person 3d-shooter game

[Alexander Alemayhu]

Am 12.09.2014 um 16:47 schrieb Markus Koschany :
> Hi Alexander,
> 
> I just saw your reply to enemylines7's ITA bug report. Sorry for the
> delay but our mailing list is not subscribed to ITA bugs.
> 
> You can either maintain the package in SVN or Git, that's up to you.

Hei Markus,

thanks for taking the time to answer.


-- 
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/8b90987a-6de7-4fe0-8980-33ec696d8...@googlemail.com

Bug#586413: Tightvnc Debian Packages

[Alexander Alemayhu]

Hei Karun,

Below are some links you might find useful:

o Debian New Maintainers' Guide[0]
o Debian Developer Reference[1]
o Debian Developers' Corner[2]

[1]: https://www.debian.org/doc/manuals/maint-guide/
[2]:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#archive-manip
[3]: https://www.debian.org/devel/


Worth mentioning that the debian-edu package recommends tightvncserver.
Maybe the Debian Edu Developers can help with questions and sponsor your
package when it is ready.



2014-08-27 23:35 GMT+02:00 Karun Dambiec :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
> I would like to get involved more with the Debian Project, and saw
> that the Tightvnc Package
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586413) is up for
> adoption.
>
> I am interested to start learning how to maintain it, and am also
> looking for a mentor.
>
> Regards
> Karun Dambiec
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
>
> iQIcBAEBCAAGBQJT/k8UAAoJEEIHKtIz9cQsrOsP/jJ8Fc27wc42hiwZAsABsFQ4
> pEkg3vMJ6cr+R3rYJ+A7LG9WQqgHKD2Ynhjb8jVCNRzQN6fVs6AKb/kbjWWPVkQX
> vxTuU+IbE5LyWX6yUA2Uq4sQrwyFYUQTckNCvmCP5TJPOIW2qBQ/w5iogfaMMXjD
> /TCRJqI2cVloS1ovQ37TTly5ImFINp5zuJx2OxSmCdFxNUboI6DQltdQkCTOGfVP
> uHVpX5NG9oZGPpMOPi55MsFvxzkwxUooUAaqsqrE4BwsbRZdubN85ME++Ubk4mPc
> HnpLh6sCO/Oui1/65gipvIG/mSoDKfxles6F+yRRobSTLNxRU/BGDzH7Ev45mTZz
> FJNjLwg8Tp1fROmN70lThlz2y3Zyg6g8R1zlSexyyHVXvBu+Z+IUl3aa2ag/4JgT
> RDVIparbXi6eiAZoyVCjI3w2CkZxqkq4Vy2o2wCOlLSj54G52vL+dHlhQfzjlgrk
> crszqcTraWrOUyx8OFkLCj12kqE583ExpjfLQL2UjXwXXSQiHMWh68KbBJn3aVUM
> mu8S6dOO2d59jK1qJItn7epRlWzAsPpqw0KFI1GQysD9NR1/elUf1ApKyFLSIdLX
> 68bhETwRxlaewMnJkIfMjU5TIH19qwnuDBTDlgvHPOYq21YtKnya/dTsNfLfSqqM
> WFw0XalVaOf7ITDfLiTs
> =SQ6P
> -END PGP SIGNATURE-
>
>
> --
> 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/53fe4f14.7020...@karun.li
>
>


-- 
Mit freundlichen GrüßenAlexander Alemayhu

Bug#753567: ITA: gsimplecal -- lightweight GUI calendar application

[Alexander Alemayhu]

On Sun, 10 Aug 2014 18:55:27 +0200 Yoann Gauthier 
 wrote:

> According Alexander advices, I rename subject to ITA.
>
> New maintainer for gsimplecal : Yoann Gauthier.
>
> Regards,
>
> Yoann

Hei Yoann.

I think you misunderstood me. Sorry if I was not clear enough earlier.
You should retitle the bug and set yourself as owner with a message like 
the one below to cont...@bugs.debian.org:


retitle #753567 ITA: gsimplecal -- lightweight GUI calendar application
owner #753567 Yoann Gauthier 


--
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/53e7d35f.5080...@yahoo.com

Bug#753567: O: gsimplecal -- lightweight GUI calendar application

[Alexander Alemayhu]

On Friday, August 8, 2014 8:37 PM, Yoann Gauthier  
wrote:






Hello,

I am volunteer to adopt gsimplecal package. I will contact upstream in
order to have informations about new release.


-- 

You might want to set yourself as owner of the bug and retitle it to change the 
'O:' to 'ITA:'.
See wnpp[0] page for more information.


[0]: https://www.debian.org/devel/wnpp/



PS: Testing Yahoo mail, not sure how the email will look.

Bug#756446: ITP Backgammon2 - a C# implementation of Backgammon game

[Alexander Alemayhu]

On Wed, Jul 30, 2014 at 05:35:18PM +0600, Andrey Rahmatullin wrote:
> The name is bad too.
> But this is just an RFP, so...
> 

Why is the name bad?


-- 
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/20140731170441.ga27...@gmail.com

Bug#755731: ITP: yacreader -- Yet another comic reader

[Alexander Alemayhu]

Package: wnpp
Severity: wishlist
Owner: Alexander Alemayhu 

* Package name : yacreader
Version : 7.1.0
Upstream Author : Luis Ángel San Martín Rodríguez 
* URL : http://www.yacreader.com/
* License : GPLv3 or later
Description : Yet another comic reader

YACReader is a free cross-platform comic reader with support for multiple comic
files and image formats. YACReader comes with YACReaderLibrary an application
for browsing and managing your comic collections with various smooth transition
effects. YACReader is fast, easy to use and all you need to enjoy your digital
comics.


-- 
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/20140722195942.gc28...@gmail.com

Bug#723097: Fwd: Bug#723097: RFA: ocrad -- optical character recognition program

[Alexander Alemayhu]

I forgot to cc. Forwarding message.

-- Forwarded message --
From: Alexander Alemayhu 
Date: 2014-07-20 19:36 GMT+02:00
Subject: Re: Bug#723097: RFA: ocrad -- optical character recognition program
To: 723...@bugs.debian.org


On Sun, Jul 20, 2014 at 07:03:47PM +0200, Jakub Wilk wrote:
> Hi Alexander,
>
> Please note that ITA means that the package still had a maintainer, and
it's
> the maintainer who decides who will take over the package. You should have
> contacted me before making the upload.
>

Hei Jakub,

I apologize. It was a mistake not to contact you.
The package has only been uploaded to experimental.



-- 
Mit freundlichen Grüßen Alexander Alemayhu

Bug#723097: RFA: ocrad -- optical character recognition program

[Alexander Alemayhu]

On Sun, Jul 20, 2014 at 07:03:47PM +0200, Jakub Wilk wrote:
> Hi Alexander,
> 
> Please note that ITA means that the package still had a maintainer, and it's
> the maintainer who decides who will take over the package. You should have
> contacted me before making the upload.
> 

Hei Jakub,

I apologize. It was a mistake not to contact you.
The package has only been uploaded to experimental.


-- 
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/20140720173641.ga24...@gmail.com

Bug#728194: enemylines7 -- first person 3d-shooter game

[Alexander Alemayhu]

Hei Debian Games Team,

I got interested in enemylines7 and considering adoption.
Is it a requirement that packages maintained by the team
be in SVN?


-- 
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/20140720154650.gb10...@gmail.com

Bug#586418: ITA: lightspeed -- Shows how objects moving at relativistic speeds look like

[Alexander Alemayhu]

Hei,

I intend to adopt lightspeed. One of my goals is to make the package use
dpkg-source 3.0 (quilt). Could you help providing descriptions to the patches
you have made? That might make it easier to split them logically. Some of my
efforts are available at[0].

Thanks.

[0]: https://github.com/scanf/lightspeed


-- 
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/20140716161644.ga17...@gmail.com

Bug#586418: ITA: lightspeed -- Shows how objects moving at relativistic speeds look like

[Alexander Alemayhu]

On Tue, Jul 08, 2014 at 08:15:26PM +0200, Ola Lundqvist wrote:
> Hej Alexander
> 
> Looking at the package again I must admit that I can not. Also looking at
> the changelog I basically just did one real correction upload in 2006 when
> I took it over. It looks like it was A Mennucc1  that
> did all the work.
> 

Hei,

thanks for taking the time to answer. I will try to contact A Mennucc1.


-- 
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/20140708210110.ga13...@gmail.com

Bug#586418: ITA: lightspeed -- Shows how objects moving at relativistic speeds look like

[Alexander Alemayhu]

Hei Ola,

I intend to adopt lightspeed. One of my goals is to make the package use 
dpkg-source 3.0 (quilt).
Could you help providing descriptions to the patches ?


-- 
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/20140708173322.ga28...@gmail.com

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: Fwd: Processing of postr_0.13-1_amd64.changes

[Alexander Alemayhu]

-- Forwarded message --
From: Debian FTP Masters 
Date: 2014-06-24 21:06 GMT+02:00
Subject: Processing of postr_0.13-1_amd64.changes
To: alexan...@bitraf.no


postr_0.13-1_amd64.changes uploaded successfully to localhost
along with the files:
  postr_0.13-1_all.deb
  postr_0.13-1.dsc
  postr_0.13.orig.tar.xz
  postr_0.13-1.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)



-- 
Mit freundlichen Grüßen Alexander Alemayhu

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.

[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:
> >> > > &g

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[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 :
> > > > >
> > > > > > 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 :).
> > > > > > >
> > > > > > > My changelog needs a review I think, because I am not familiar
> > with
> > > > > > > changeLog conventions.
> > > > > > >
> > > > > >
> > > > > > It looks good IMO :)
> > > > > >
> > > > > > > If you have new task to delegate, I am available.
> > > > > > >
> > > > > >
> > 

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

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.

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.

> 
> 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 :
> > >
> > > > 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 :).
> > > > >
> > > > > My changelog needs a review I think, because I am not familiar with
> > > > > changeLog conventions.
> > > > >
> > > >
> > > > It looks good IMO :)
> > > >
> > > > > If you have new task to delegate, I am available.
> > > > >
> > > >
> > > > After running lintian today a new warning appears:
> > > > W: postr source: missing-license-paragraph-in-dep5-copyright gpl-3
> > > > (paragraph at line 3)
> > > >
> > > > The warning does appear on earlier commits aswell. Maybe something has
> > > > changed
> > > > in lintian, could you look into it?
> > > >
> > > > I talked with a DD and was recommended to fix the autotools warnings
> > > > reported by
> > > > lintian. He also proposed to handle the python bytecode generation in a
> > > > more
> > > > correct way. I will be looking at using dh-autoreconf to make the
> > package
> > > > free
> > > > of the autools warnings. It might take a couple of days...
> > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Yoann
> > > > >
> > > > >
> > > > > 2014-06-10 7:57 GMT+02:00 Alexander Alemayhu :
> > > > >
> > > > > > On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > >
> > > > > > Hei.
> > > > > >
> > > > > > > I fixed the desktop-entry-lacks-keywords-entry as asked.
> > > > > > > Find attached the patch. I used quilt to create my patch :
> > > > > > > 04-fix_desktop_keywords.patch and then git format to create patch
> > > > file.
> > > > > > &

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[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 :
> 
> > 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 :).
> > >
> > > My changelog needs a review I think, because I am not familiar with
> > > changeLog conventions.
> > >
> >
> > It looks good IMO :)
> >
> > > If you have new task to delegate, I am available.
> > >
> >
> > After running lintian today a new warning appears:
> > W: postr source: missing-license-paragraph-in-dep5-copyright gpl-3
> > (paragraph at line 3)
> >
> > The warning does appear on earlier commits aswell. Maybe something has
> > changed
> > in lintian, could you look into it?
> >
> > I talked with a DD and was recommended to fix the autotools warnings
> > reported by
> > lintian. He also proposed to handle the python bytecode generation in a
> > more
> > correct way. I will be looking at using dh-autoreconf to make the package
> > free
> > of the autools warnings. It might take a couple of days...
> >
> > >
> > > Regards,
> > >
> > > Yoann
> > >
> > >
> > > 2014-06-10 7:57 GMT+02:00 Alexander Alemayhu :
> > >
> > > > On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote:
> > > > > Hello,
> > > > >
> > > >
> > > > Hei.
> > > >
> > > > > I fixed the desktop-entry-lacks-keywords-entry as asked.
> > > > > Find attached the patch. I used quilt to create my patch :
> > > > > 04-fix_desktop_keywords.patch and then git format to create patch
> > file.
> > > > >
> > > >
> > > > Good. You should also update the debian/changelog to include an entry
> > which
> > > > mentions the patch. Please take a close look at the existing lines to
> > get
> > > > an
> > > > idea of what to write.
> > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > PS : have access (push request) to your repository will be easier
> > for me.
> > > > >
> > > >
> > > > Full access granted. You should now be able to push directly.
> > > >
> > > > > Yoann
> > > > >
> > > > >
> > > > > 2014-06-03 22:50 GMT+02:00 Alexander Alemayhu :
> > > > >
> > > > > > On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
> > > > > > > Hi Alexander,
> > > > > > >
> > > > > > > What are the next tasks I can do to help for the packaging ?
> > > > > > >
> > > > > >
> > > > > > You could look at the desktop-entry-lacks-keywords-entry[0]
> > lintian tag
> > > > > > and try
> > > > > > to fix it. I was planning on fixing it but wanted to prioritize the
> > > > > > autotools
> > > > > > warnings. Hopefully we can get some advice from David.
> > > > > >
> > > > > > It looks like you would need to create a debian patch file to
> > modify
> > > > > > data/postr.desktop.in.in. If you are unfamiliar with quilt, take a
> > > > look
> > > > > > at this
> > > > > > introduction[1].
> > > > > >
> > > > > > PS: Remember to fetch the latest changes, before making new
> > changes. It
> > > > > > might
> > > > > > help in avoiding merge conflicts.
> > > > > >
> > > > > > PPS: desktop-entry-lacks-keywords-entry only occurs when using
> > `lintian
> > > > > > -EvIL
> > > > > > +pedantic` 

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

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 :).
> 
> My changelog needs a review I think, because I am not familiar with
> changeLog conventions.
> 

It looks good IMO :)

> If you have new task to delegate, I am available.
> 

After running lintian today a new warning appears:
W: postr source: missing-license-paragraph-in-dep5-copyright gpl-3 (paragraph 
at line 3)

The warning does appear on earlier commits aswell. Maybe something has changed
in lintian, could you look into it? 

I talked with a DD and was recommended to fix the autotools warnings reported by
lintian. He also proposed to handle the python bytecode generation in a more
correct way. I will be looking at using dh-autoreconf to make the package free
of the autools warnings. It might take a couple of days...

> 
> Regards,
> 
> Yoann
> 
> 
> 2014-06-10 7:57 GMT+02:00 Alexander Alemayhu :
> 
> > On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote:
> > > Hello,
> > >
> >
> > Hei.
> >
> > > I fixed the desktop-entry-lacks-keywords-entry as asked.
> > > Find attached the patch. I used quilt to create my patch :
> > > 04-fix_desktop_keywords.patch and then git format to create patch file.
> > >
> >
> > Good. You should also update the debian/changelog to include an entry which
> > mentions the patch. Please take a close look at the existing lines to get
> > an
> > idea of what to write.
> >
> > >
> > > Regards,
> > >
> > > PS : have access (push request) to your repository will be easier for me.
> > >
> >
> > Full access granted. You should now be able to push directly.
> >
> > > Yoann
> > >
> > >
> > > 2014-06-03 22:50 GMT+02:00 Alexander Alemayhu :
> > >
> > > > On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
> > > > > Hi Alexander,
> > > > >
> > > > > What are the next tasks I can do to help for the packaging ?
> > > > >
> > > >
> > > > You could look at the desktop-entry-lacks-keywords-entry[0] lintian tag
> > > > and try
> > > > to fix it. I was planning on fixing it but wanted to prioritize the
> > > > autotools
> > > > warnings. Hopefully we can get some advice from David.
> > > >
> > > > It looks like you would need to create a debian patch file to modify
> > > > data/postr.desktop.in.in. If you are unfamiliar with quilt, take a
> > look
> > > > at this
> > > > introduction[1].
> > > >
> > > > PS: Remember to fetch the latest changes, before making new changes. It
> > > > might
> > > > help in avoiding merge conflicts.
> > > >
> > > > PPS: desktop-entry-lacks-keywords-entry only occurs when using `lintian
> > > > -EvIL
> > > > +pedantic` on my machine.
> > > >
> > > > [0]:
> > > > http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html
> > > > [1]:
> > > >
> > > >
> > http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
> > > >
> > > > > Regards,
> > > > >
> > > > > Yoann
> > > > >
> > > > >
> > > > > 2014-06-02 21:26 GMT+02:00 Alexander Alemayhu :
> > > > >
> > > > > > On Mon, Jun 02, 2014 at 10:30:40AM +0200, Yoann Gauthier wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > For man page license, I propose to distribute it under GNU GLP
> > (v3).
> > > > Do
> > > > > > you
> > > > > > > agree ?
> > > > > > >
> > > > > >
> > > > > > I am no license expert, but I think it is okay assuming you mean
> > GNU
> > > > GPL.
> > > > > >
> > > > > > > Okay for the maintener part, I will set the maintainer to Python
> > > > > > > Applications Packaging Team.
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Yoann
> > > > > > >
> > > > > > >
> > > > > > > 2014-06-01 18:26 GMT+02:00 Alexander Alemayhu <
> > alexan...@bi

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

On Mon, Jun 09, 2014 at 08:29:51PM +0200, Yoann Gauthier wrote:
> Hello,
> 

Hei.

> I fixed the desktop-entry-lacks-keywords-entry as asked.
> Find attached the patch. I used quilt to create my patch :
> 04-fix_desktop_keywords.patch and then git format to create patch file.
> 

Good. You should also update the debian/changelog to include an entry which
mentions the patch. Please take a close look at the existing lines to get an
idea of what to write.

> 
> Regards,
> 
> PS : have access (push request) to your repository will be easier for me.
> 

Full access granted. You should now be able to push directly.

> Yoann
> 
> 
> 2014-06-03 22:50 GMT+02:00 Alexander Alemayhu :
> 
> > On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
> > > Hi Alexander,
> > >
> > > What are the next tasks I can do to help for the packaging ?
> > >
> >
> > You could look at the desktop-entry-lacks-keywords-entry[0] lintian tag
> > and try
> > to fix it. I was planning on fixing it but wanted to prioritize the
> > autotools
> > warnings. Hopefully we can get some advice from David.
> >
> > It looks like you would need to create a debian patch file to modify
> > data/postr.desktop.in.in. If you are unfamiliar with quilt, take a look
> > at this
> > introduction[1].
> >
> > PS: Remember to fetch the latest changes, before making new changes. It
> > might
> > help in avoiding merge conflicts.
> >
> > PPS: desktop-entry-lacks-keywords-entry only occurs when using `lintian
> > -EvIL
> > +pedantic` on my machine.
> >
> > [0]:
> > http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html
> > [1]:
> >
> > http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
> >
> > > Regards,
> > >
> > > Yoann
> > >
> > >
> > > 2014-06-02 21:26 GMT+02:00 Alexander Alemayhu :
> > >
> > > > On Mon, Jun 02, 2014 at 10:30:40AM +0200, Yoann Gauthier wrote:
> > > > > Hi,
> > > > >
> > > > > For man page license, I propose to distribute it under GNU GLP (v3).
> > Do
> > > > you
> > > > > agree ?
> > > > >
> > > >
> > > > I am no license expert, but I think it is okay assuming you mean GNU
> > GPL.
> > > >
> > > > > Okay for the maintener part, I will set the maintainer to Python
> > > > > Applications Packaging Team.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Yoann
> > > > >
> > > > >
> > > > > 2014-06-01 18:26 GMT+02:00 Alexander Alemayhu :
> > > > >
> > > > > > On Sun, Jun 01, 2014 at 03:50:27PM +0200, Yoann Gauthier wrote:
> > > > > > > Le 31 mai 2014 20:00, "Alexander Alemayhu" 
> > a
> > > > > > écrit :
> > > > > > > >
> > > > > > > > On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote:
> > > > > > > > > Hello,
> > > > > > > > >
> > > > > > > >
> > > > > > > > Hei,
> > > > > > > >
> > > > > > > > > I wrote the man page (attachment). I have no access to the
> > > > repository
> > > > > > > > > today, I will upload the page to repository tomorrow.
> > > > > > > > >
> > > > > > > >
> > > > > > > > Nice. I decided to use github as the Vcs-* since collab-maint
> > > > seems to
> > > > > > be
> > > > > > > for
> > > > > > > > people packing together with DDs. Maybe we should ask for
> > access
> > > > and
> > > > > > push
> > > > > > > our
> > > > > > > > changes there?
> > > > > > >
> > > > > > > I don't understand Vcs, what is it ?
> > > > > >
> > > > > > A akronym for Version Control System[0].
> > > > > >
> > > > > > > > I think you have a typo 'MAINTENERS' should be 'MAINTAINERS'.
> > It
> > > > could
> > > > > > be
> > > > > > > a
> > > > > > > > good idea to ask for others 

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

On Tue, Jun 03, 2014 at 11:45:27AM +0200, Yoann Gauthier wrote:
> Hi Alexander,
> 
> What are the next tasks I can do to help for the packaging ?
> 

You could look at the desktop-entry-lacks-keywords-entry[0] lintian tag and try
to fix it. I was planning on fixing it but wanted to prioritize the autotools
warnings. Hopefully we can get some advice from David.

It looks like you would need to create a debian patch file to modify
data/postr.desktop.in.in. If you are unfamiliar with quilt, take a look at this
introduction[1].

PS: Remember to fetch the latest changes, before making new changes. It might
help in avoiding merge conflicts.

PPS: desktop-entry-lacks-keywords-entry only occurs when using `lintian -EvIL
+pedantic` on my machine.

[0]: http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html
[1]:
http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/

> Regards,
> 
> Yoann
> 
> 
> 2014-06-02 21:26 GMT+02:00 Alexander Alemayhu :
> 
> > On Mon, Jun 02, 2014 at 10:30:40AM +0200, Yoann Gauthier wrote:
> > > Hi,
> > >
> > > For man page license, I propose to distribute it under GNU GLP (v3). Do
> > you
> > > agree ?
> > >
> >
> > I am no license expert, but I think it is okay assuming you mean GNU GPL.
> >
> > > Okay for the maintener part, I will set the maintainer to Python
> > > Applications Packaging Team.
> > >
> > > Regards,
> > >
> > > Yoann
> > >
> > >
> > > 2014-06-01 18:26 GMT+02:00 Alexander Alemayhu :
> > >
> > > > On Sun, Jun 01, 2014 at 03:50:27PM +0200, Yoann Gauthier wrote:
> > > > > Le 31 mai 2014 20:00, "Alexander Alemayhu"  a
> > > > écrit :
> > > > > >
> > > > > > On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > >
> > > > > > Hei,
> > > > > >
> > > > > > > I wrote the man page (attachment). I have no access to the
> > repository
> > > > > > > today, I will upload the page to repository tomorrow.
> > > > > > >
> > > > > >
> > > > > > Nice. I decided to use github as the Vcs-* since collab-maint
> > seems to
> > > > be
> > > > > for
> > > > > > people packing together with DDs. Maybe we should ask for access
> > and
> > > > push
> > > > > our
> > > > > > changes there?
> > > > >
> > > > > I don't understand Vcs, what is it ?
> > > >
> > > > A akronym for Version Control System[0].
> > > >
> > > > > > I think you have a typo 'MAINTENERS' should be 'MAINTAINERS'. It
> > could
> > > > be
> > > > > a
> > > > > > good idea to ask for others to review the man page. Which license
> > do
> > > > you
> > > > > want
> > > > > > to distribute the man page with? we have to mention the license in
> > > > > > debian/copyright.
> > > > >
> > > > > Agree for the typo, this evening I will read again the man page and
> > add
> > > > > more information maybe. Okay for the license, i will think.
> > > > > >
> > > >
> > > > In order to stay consistent with the debian/control file we should set
> > the
> > > > maintainer to Python Applications Packaging Team
> > > > 
> > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Yoann
> > > > > > >
> > > >
> > > > [0]: http://en.wikipedia.org/wiki/Version_control
> > > >
> > > > > > >
> > > > > > > 2014-05-30 12:36 GMT+02:00 Yoann Gauthier <
> > yoann.gauthi...@gmail.com
> > > > >:
> > > > > > >
> > > > > > > > Hi Alexander,
> > > > > > > >
> > > > > > > > Yes, I am going to write the man page. It will be finished
> > today or
> > > > > > > > tomorrow.
> > > > > > > > Okay for the RFS.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > >
> > > > > > > > Yoann
> > > > > > >

Bug#711833: Sponsoring upload?

[Alexander Alemayhu]

Hei David,

could you review the package and maybe even sponsor an upload?

Running `lintian -EvIL +pedantic` returns the following messages:

N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-RJWroH1zF3 ...
N: Unpacking packages in group postr/0.13-1
N: 
N: Processing changes file postr (version 0.13-1, arch source all) ...
N: 
N: Processing source package postr (version 0.13-1, arch source) ...
W: postr source: outdated-autotools-helper-file config.guess 2012-02-10
W: postr source: outdated-autotools-helper-file config.sub 2012-02-10
W: postr source: ancient-standards-version 3.8.4 (current is 3.9.5)
P: postr source: debian-watch-may-check-gpg-signature
N: 
N: Processing binary package postr (version 0.13-1, arch all) ...
I: postr: desktop-entry-lacks-keywords-entry 
usr/share/applications/postr.desktop

I am not sure how to fix the autotools warnings. Should we try to fix them or 
forward
them upstream?

Is it okay if we update the debian/copyright file to include Yoann and me in
the copyright after mentioning you and Ross? Yoann wrote a manpage which we are
adding in debian/ and the license he choose is GPL-3+, should we change the
current License field on the debian/ directory to GPL-3+ or just add a single
entry for the manpage?


-- 
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/20140602210221.ga10...@gmail.com

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

On Mon, Jun 02, 2014 at 10:30:40AM +0200, Yoann Gauthier wrote:
> Hi,
> 
> For man page license, I propose to distribute it under GNU GLP (v3). Do you
> agree ?
> 

I am no license expert, but I think it is okay assuming you mean GNU GPL.

> Okay for the maintener part, I will set the maintainer to Python
> Applications Packaging Team.
> 
> Regards,
> 
> Yoann
> 
> 
> 2014-06-01 18:26 GMT+02:00 Alexander Alemayhu :
> 
> > On Sun, Jun 01, 2014 at 03:50:27PM +0200, Yoann Gauthier wrote:
> > > Le 31 mai 2014 20:00, "Alexander Alemayhu"  a
> > écrit :
> > > >
> > > > On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote:
> > > > > Hello,
> > > > >
> > > >
> > > > Hei,
> > > >
> > > > > I wrote the man page (attachment). I have no access to the repository
> > > > > today, I will upload the page to repository tomorrow.
> > > > >
> > > >
> > > > Nice. I decided to use github as the Vcs-* since collab-maint seems to
> > be
> > > for
> > > > people packing together with DDs. Maybe we should ask for access and
> > push
> > > our
> > > > changes there?
> > >
> > > I don't understand Vcs, what is it ?
> >
> > A akronym for Version Control System[0].
> >
> > > > I think you have a typo 'MAINTENERS' should be 'MAINTAINERS'. It could
> > be
> > > a
> > > > good idea to ask for others to review the man page. Which license do
> > you
> > > want
> > > > to distribute the man page with? we have to mention the license in
> > > > debian/copyright.
> > >
> > > Agree for the typo, this evening I will read again the man page and add
> > > more information maybe. Okay for the license, i will think.
> > > >
> >
> > In order to stay consistent with the debian/control file we should set the
> > maintainer to Python Applications Packaging Team
> > 
> >
> > > > > Regards,
> > > > >
> > > > > Yoann
> > > > >
> >
> > [0]: http://en.wikipedia.org/wiki/Version_control
> >
> > > > >
> > > > > 2014-05-30 12:36 GMT+02:00 Yoann Gauthier  > >:
> > > > >
> > > > > > Hi Alexander,
> > > > > >
> > > > > > Yes, I am going to write the man page. It will be finished today or
> > > > > > tomorrow.
> > > > > > Okay for the RFS.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Yoann
> > > > > >
> > > > > >
> > > > > > 2014-05-30 10:43 GMT+02:00 Alexander Alemayhu  > >:
> > > > > >
> > > > > > Hei Yoann,
> > > > > >>
> > > > > >> below is a message I recived after reuploading to
> > mentors.debian.net.
> > > > > >> The warnings I mentioned earlier are visible in the package page.
> > > > > >> Are you going to write a man page? I would like to send a RFS
> > after
> > > fixing
> > > > > >> some more of the warnings to the PAPT list.
> > > > > >>
> > > > > >> - Forwarded message from "mentors.debian.net" <
> > > > > >> supp...@mentors.debian.net> -
> > > > > >>
> > > > > >> Date: Wed, 28 May 2014 21:33:31 + (UTC)
> > > > > >> From: "mentors.debian.net" 
> > > > > >> To: alexan...@bitraf.no
> > > > > >> Subject: postr uploaded to mentors.debian.net
> > > > > >>
> > > > > >> Hi.
> > > > > >>
> > > > > >> Your upload of the package 'postr' to mentors.debian.net was
> > > > > >> successful. Others can now see it. The URL of your package is:
> > > > > >> http://mentors.debian.net/package/postr
> > > > > >>
> > > > > >> The respective dsc file can be found at:
> > > > > >>
> > http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc
> > > > > >>
> > > > > >> If you do not yet have a sponsor for your package you may want to
> > go
> > > to
> > > > > >> http://mentors.debian.net/sponsors/rfs-howto/postr
> > > > > >> and set the "Seeking a sponsor" option to highlight your package
> > on
> > > the
> > > > > >> welcome page.
> > > > > >>
> > > > > >> You can also send an RFS (request for sponsorship) to the
> > > debian-mentors
> > > > > >> mailing list. Your package page will give your suggestions on how
> > to
> > > > > >> send that mail.
> > > > > >>
> > > > > >> Good luck in finding a sponsor!
> > > > > >>
> > > > > >> Thanks,
> > > > > >>
> > > > > >> --
> > > > > >> mentors.debian.net
> > > > > >>
> > > > > >> - End forwarded message -
> > > > > >>
> > > > > >
> > > > > >
> > > >
> > > >
> >


-- 
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/20140602192616.ga10...@gmail.com

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

On Sun, Jun 01, 2014 at 03:50:27PM +0200, Yoann Gauthier wrote:
> Le 31 mai 2014 20:00, "Alexander Alemayhu"  a écrit :
> >
> > On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote:
> > > Hello,
> > >
> >
> > Hei,
> >
> > > I wrote the man page (attachment). I have no access to the repository
> > > today, I will upload the page to repository tomorrow.
> > >
> >
> > Nice. I decided to use github as the Vcs-* since collab-maint seems to be
> for
> > people packing together with DDs. Maybe we should ask for access and push
> our
> > changes there?
> 
> I don't understand Vcs, what is it ?

A akronym for Version Control System[0].

> > I think you have a typo 'MAINTENERS' should be 'MAINTAINERS'. It could be
> a
> > good idea to ask for others to review the man page. Which license do you
> want
> > to distribute the man page with? we have to mention the license in
> > debian/copyright.
> 
> Agree for the typo, this evening I will read again the man page and add
> more information maybe. Okay for the license, i will think.
> >

In order to stay consistent with the debian/control file we should set the
maintainer to Python Applications Packaging Team
 

> > > Regards,
> > >
> > > Yoann
> > >

[0]: http://en.wikipedia.org/wiki/Version_control

> > >
> > > 2014-05-30 12:36 GMT+02:00 Yoann Gauthier :
> > >
> > > > Hi Alexander,
> > > >
> > > > Yes, I am going to write the man page. It will be finished today or
> > > > tomorrow.
> > > > Okay for the RFS.
> > > >
> > > > Regards,
> > > >
> > > > Yoann
> > > >
> > > >
> > > > 2014-05-30 10:43 GMT+02:00 Alexander Alemayhu :
> > > >
> > > > Hei Yoann,
> > > >>
> > > >> below is a message I recived after reuploading to mentors.debian.net.
> > > >> The warnings I mentioned earlier are visible in the package page.
> > > >> Are you going to write a man page? I would like to send a RFS after
> fixing
> > > >> some more of the warnings to the PAPT list.
> > > >>
> > > >> - Forwarded message from "mentors.debian.net" <
> > > >> supp...@mentors.debian.net> -
> > > >>
> > > >> Date: Wed, 28 May 2014 21:33:31 + (UTC)
> > > >> From: "mentors.debian.net" 
> > > >> To: alexan...@bitraf.no
> > > >> Subject: postr uploaded to mentors.debian.net
> > > >>
> > > >> Hi.
> > > >>
> > > >> Your upload of the package 'postr' to mentors.debian.net was
> > > >> successful. Others can now see it. The URL of your package is:
> > > >> http://mentors.debian.net/package/postr
> > > >>
> > > >> The respective dsc file can be found at:
> > > >> http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc
> > > >>
> > > >> If you do not yet have a sponsor for your package you may want to go
> to
> > > >> http://mentors.debian.net/sponsors/rfs-howto/postr
> > > >> and set the "Seeking a sponsor" option to highlight your package on
> the
> > > >> welcome page.
> > > >>
> > > >> You can also send an RFS (request for sponsorship) to the
> debian-mentors
> > > >> mailing list. Your package page will give your suggestions on how to
> > > >> send that mail.
> > > >>
> > > >> Good luck in finding a sponsor!
> > > >>
> > > >> Thanks,
> > > >>
> > > >> --
> > > >> mentors.debian.net
> > > >>
> > > >> - End forwarded message -
> > > >>
> > > >
> > > >
> >
> >


-- 
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/20140601162618.ga11...@gmail.com

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

On Sat, May 31, 2014 at 03:29:16PM +0200, Yoann Gauthier wrote:
> Hello,
> 

Hei,

> I wrote the man page (attachment). I have no access to the repository
> today, I will upload the page to repository tomorrow.
> 

Nice. I decided to use github as the Vcs-* since collab-maint seems to be for
people packing together with DDs. Maybe we should ask for access and push our
changes there? 

I think you have a typo 'MAINTENERS' should be 'MAINTAINERS'. It could be a
good idea to ask for others to review the man page. Which license do you want
to distribute the man page with? we have to mention the license in
debian/copyright.


> Regards,
> 
> Yoann
> 
> 
> 2014-05-30 12:36 GMT+02:00 Yoann Gauthier :
> 
> > Hi Alexander,
> >
> > Yes, I am going to write the man page. It will be finished today or
> > tomorrow.
> > Okay for the RFS.
> >
> > Regards,
> >
> > Yoann
> >
> >
> > 2014-05-30 10:43 GMT+02:00 Alexander Alemayhu :
> >
> > Hei Yoann,
> >>
> >> below is a message I recived after reuploading to mentors.debian.net.
> >> The warnings I mentioned earlier are visible in the package page.
> >> Are you going to write a man page? I would like to send a RFS after fixing
> >> some more of the warnings to the PAPT list.
> >>
> >> - Forwarded message from "mentors.debian.net" <
> >> supp...@mentors.debian.net> -
> >>
> >> Date: Wed, 28 May 2014 21:33:31 + (UTC)
> >> From: "mentors.debian.net" 
> >> To: alexan...@bitraf.no
> >> Subject: postr uploaded to mentors.debian.net
> >>
> >> Hi.
> >>
> >> Your upload of the package 'postr' to mentors.debian.net was
> >> successful. Others can now see it. The URL of your package is:
> >> http://mentors.debian.net/package/postr
> >>
> >> The respective dsc file can be found at:
> >> http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc
> >>
> >> If you do not yet have a sponsor for your package you may want to go to
> >> http://mentors.debian.net/sponsors/rfs-howto/postr
> >> and set the "Seeking a sponsor" option to highlight your package on the
> >> welcome page.
> >>
> >> You can also send an RFS (request for sponsorship) to the debian-mentors
> >> mailing list. Your package page will give your suggestions on how to
> >> send that mail.
> >>
> >> Good luck in finding a sponsor!
> >>
> >> Thanks,
> >>
> >> --
> >> mentors.debian.net
> >>
> >> - End forwarded message -
> >>
> >
> >


-- 
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/20140531180014.ga10...@gmail.com

Bug#711833: [supp...@mentors.debian.net: postr uploaded to mentors.debian.net]

[Alexander Alemayhu]

Hei Yoann,

below is a message I recived after reuploading to mentors.debian.net.
The warnings I mentioned earlier are visible in the package page.
Are you going to write a man page? I would like to send a RFS after fixing
some more of the warnings to the PAPT list.

- Forwarded message from "mentors.debian.net"  
-

Date: Wed, 28 May 2014 21:33:31 + (UTC)
From: "mentors.debian.net" 
To: alexan...@bitraf.no
Subject: postr uploaded to mentors.debian.net

Hi.

Your upload of the package 'postr' to mentors.debian.net was
successful. Others can now see it. The URL of your package is:
http://mentors.debian.net/package/postr

The respective dsc file can be found at:
http://mentors.debian.net/debian/pool/main/p/postr/postr_0.13-1.dsc

If you do not yet have a sponsor for your package you may want to go to
http://mentors.debian.net/sponsors/rfs-howto/postr
and set the "Seeking a sponsor" option to highlight your package on the
welcome page.

You can also send an RFS (request for sponsorship) to the debian-mentors
mailing list. Your package page will give your suggestions on how to
send that mail.

Good luck in finding a sponsor!

Thanks,

-- 
mentors.debian.net

- End forwarded message -


-- 
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/20140530084347.ga54...@gmail.com

Bug#711833: Preparing new package upload

[Alexander Alemayhu]

On Tue, May 27, 2014 at 09:24:20AM +0200, Yoann Gauthier wrote:
> Hello,
> 
> I propose to write a simple man page  in order to have a clean package.
> 
> Regards,
> 
> Yoann
> 

If you want to write one good :)

After uploading to mentors I recieved some other warnings. I will be looking
at them later. I am currently using a different machine and do not have
the warnings here, but will add them in a later email.

> 
> 2014-05-26 20:35 GMT+02:00 Alexander Alemayhu :
> 
> > Hei,
> >
> > I fixed all the errors reported by lintian, sorry for not giving notice
> > that I
> > was working on them. As far as I can see the remaining message from
> > lintian is:
> >
> > W: postr: binary-without-manpage usr/bin/postr
> >
> > I have not written a manpage before so the warning is not that important
> > to me.
> >
> > I will publish the package soon, after cleaning up the changelog. I have
> > set
> > PAPT as the maintainer and both of us as uploaders.
> >


-- 
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/20140527102131.ga18...@gmail.com

Bug#711833: Preparing new package upload

[Alexander Alemayhu]

Hei,

I fixed all the errors reported by lintian, sorry for not giving notice that I
was working on them. As far as I can see the remaining message from lintian is:

W: postr: binary-without-manpage usr/bin/postr

I have not written a manpage before so the warning is not that important to me.

I will publish the package soon, after cleaning up the changelog. I have set 
PAPT as the maintainer and both of us as uploaders.


-- 
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/20140526183543.ga29...@gmail.com

Bug#711833: Preparing new package upload

[Alexander Alemayhu]

On Mon, May 26, 2014 at 10:48:39AM +0200, Yoann Gauthier wrote:
> Hello Alexander,
> 
> I read your mails. I agree with you for fixing the error of the lintian
> inspection.
> 
> Do you have a strategy to divide the taks ?

Not really. If any of the messages seem interesting just dig in and look
closer. Would be nice to inform eachother what we are working on, to avoid
duplicate work.

Please cc the bug when contacting me, there is no reason to have our dialog
private.

> 
> Regards,
> 
> Yoann
> 
> 
> 2014-05-25 23:35 GMT+02:00 Alexander Alemayhu :
> 
> > Hei Yoann
> >
> > I currently have a working repository[0] which builds a .deb package with
> > postr 0.13 via git-buildpackage. Running `lintian postr_0.13-1_all.deb` on
> > the package gives me the following output:
> >
> > W: postr: file-in-unusual-dir usr/postrExtension.py
> > W: postr: file-in-unusual-dir usr/postrExtension.pyc
> > E: postr: package-installs-python-bytecode usr/postrExtension.pyc
> > W: postr: file-in-unusual-dir usr/postrExtension.pyo
> > E: postr: package-installs-python-bytecode usr/postrExtension.pyo
> > W: postr: binary-without-manpage usr/bin/postr
> >
> > We should fix the errors and try to fix the warnings aswell.
> >
> > [0]: https://github.com/scanf/postr
> >


-- 
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/20140526091827.ga...@gmail.com

Bug#711833: Preparing new package upload

[Alexander Alemayhu]

Hei Yoann

I currently have a working repository[0] which builds a .deb package with
postr 0.13 via git-buildpackage. Running `lintian postr_0.13-1_all.deb` on
the package gives me the following output:

W: postr: file-in-unusual-dir usr/postrExtension.py
W: postr: file-in-unusual-dir usr/postrExtension.pyc
E: postr: package-installs-python-bytecode usr/postrExtension.pyc
W: postr: file-in-unusual-dir usr/postrExtension.pyo
E: postr: package-installs-python-bytecode usr/postrExtension.pyo
W: postr: binary-without-manpage usr/bin/postr

We should fix the errors and try to fix the warnings aswell.

[0]: https://github.com/scanf/postr


-- 
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/20140525213554.ga2...@gmail.com

Bug#711833: Preparing new package upload

[Alexander Alemayhu]

Hei Yoann,

there is a newer upstream release of postr[0]. Before we upload a new postr
package, we should try to reproduce the existing bugs, import new upstream
version, try again to reproduce the exsiting bugs and try to fix any remaining
bugs.

Here[1] is the list with the bugs reported on postr. If you have not already
clone this repository[2].

[0]: https://download.gnome.org/sources/postr/0.13/
[1]: https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=postr
[2]: git://git.debian.org/git/collab-maint/postr.git


-- 
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/20140522095259.ga12...@gmail.com

Bug#711833: Request to join python-apps

[Alexander Alemayhu]

On Mon, May 19, 2014 at 05:10:11PM -0700, Vincent Cheng wrote:
> Hi Alexander,
> 
> On Mon, May 19, 2014 at 12:05 PM, Alexander Alemayhu
>  wrote:
> > Hei,
> >
> > I was on the #debian-python IRC channel on irc.efnet.org earlier. I want to
> 
> irc.efnet.org? Don't you mean OFTC (or its alias irc.debian.org)?
> 

Yes. I meant OFTC.

> > join the python-apps team and have already sent a request in the web 
> > interface
> > on alioth. My intention is to adopt postr[0] within the team and maintain it
> > together with Yoann Gauthier. Is there any official process to adopting a
> > package within a team after joining?
> >
> > [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711833
> 
> If you intend to join the PAPT, please create an account on Alioth [1]
> and join the team there in order to get commit access to our svn
> repos; more info at [2]. I suggest uploading the package to
> mentors.debian.net (definitely read [3] first) as well to make it
> easier to review your package.
> 

I already have an account on Alioth and a request to join has been sent. My
username is ccscanf-guest. I am still waiting for the PAPT administrators to
approve my request.

Thanks.

> Regards,
> Vincent
> 
> [1] https://alioth.debian.org/
> [2] https://wiki.debian.org/Teams/PythonAppsPackagingTeam
> [3] http://mentors.debian.net/intro-maintainers


-- 
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/20140520075356.ga89...@gmail.com

Bug#711833: Request to join python-apps

[Alexander Alemayhu]

Hei,

I was on the #debian-python IRC channel on irc.efnet.org earlier. I want to
join the python-apps team and have already sent a request in the web interface
on alioth. My intention is to adopt postr[0] within the team and maintain it
together with Yoann Gauthier. Is there any official process to adopting a
package within a team after joining?

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711833


-- 
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/20140519190548.ga2...@gmail.com

Bug#712937: New maintainer for the Olive package

[Alexander Alemayhu]

Hei Hugo,

I have a lot of spare time and would like to adopt olive. I think olive is
interesting enough to keep it in debian. Have you had a look at #700057? I
haven't attempted to reproduce it yet, maybe something for you to look at to
get to know the package.

Below are some links I found very useful.

o Debian New Maintainers' Guide[0]
o Debian Developer Reference[1]
o Debian Developers' Corner[2]

[1]: https://www.debian.org/doc/manuals/maint-guide/
[2]: 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#archive-manip
[3]: https://www.debian.org/devel/


signature.asc
Description: Digital signature

Bug#710908: #710908

[Alexander Alemayhu]

Hi,

I would like to adopt azureus. I was also in #debian-java to ask for
tips/advice. Do you still plan on adopting azureus? I would like to help
keep it in Debian.

-- 
Mit freundlichen Grüßen Alexander Alemayhu

Bug#711833: #711833

[Alexander Alemayhu]

Hi,

I also discovered the postr package and would like to adopt it. Do you
still plan on adopting postr? If yes is there anyway I can help you?

-- 
Mit freundlichen Grüßen Alexander Alemayhu