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 l
Hello,
I propose to write a simple man page in order to have a clean package.
Regards,
Yoann
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 me
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 wi
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
cl
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/postrExte
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 post
6 matches
Mail list logo
