Re: RFS: aescrypt

2011-08-08 Thread Benoît Knecht
mezgani ali wrote: > Benoît, i receive a message from upstream telling that he can not actually > modify the source code, > he said that if i want to do that for a version i have to branch from the > current code, with his complete approval. It sounds like there was a bit of miscommunication; he p

Re: RFS: aescrypt

2011-08-05 Thread mezgani ali
Benoît, i receive a message from upstream telling that he can not actually modify the source code, he said that if i want to do that for a version i have to branch from the current code, with his complete approval. I'm little confused about this, may i branch software ? and host it somewhere ? Ki

Re: RFS: aescrypt

2011-08-05 Thread mezgani ali
2011/8/5 Benoît Knecht > Bernhard R. Link wrote: > > * Benoît Knecht [110804 23:03]: > > > Bernhard R. Link wrote: > > > > * Benoît Knecht [110804 20:54]: > > > > > I've seen that, but they need to make that perfectly clear in the > > > > > license header of each file in the tarball. An email s

Re: RFS: aescrypt

2011-08-05 Thread Benoît Knecht
Bernhard R. Link wrote: > * Benoît Knecht [110804 23:03]: > > Bernhard R. Link wrote: > > > * Benoît Knecht [110804 20:54]: > > > > I've seen that, but they need to make that perfectly clear in the > > > > license header of each file in the tarball. An email sent to you and > > > > reproduced in

Re: RFS: aescrypt

2011-08-05 Thread Bernhard R. Link
* Benoît Knecht [110804 23:03]: > Bernhard R. Link wrote: > > * Benoît Knecht [110804 20:54]: > > > I've seen that, but they need to make that perfectly clear in the > > > license header of each file in the tarball. An email sent to you and > > > reproduced in the debian/copyright file is not eno

Re: RFS: aescrypt

2011-08-04 Thread Benoît Knecht
Bernhard R. Link wrote: > * Benoît Knecht [110804 20:54]: > > I've seen that, but they need to make that perfectly clear in the > > license header of each file in the tarball. An email sent to you and > > reproduced in the debian/copyright file is not enough. > > There is nothing special about th

Re: RFS: aescrypt

2011-08-04 Thread Bernhard R. Link
* Benoît Knecht [110804 20:54]: > I've seen that, but they need to make that perfectly clear in the > license header of each file in the tarball. An email sent to you and > reproduced in the debian/copyright file is not enough. There is nothing special about the source files. There is a need to h

Re: RFS: aescrypt

2011-08-04 Thread Benoît Knecht
mezgani ali wrote: > Benoît, i've received a message from upstream, telling that the application > is totally free, without any restriction for modification or redistribution. > in the fact, i insert message text in the copyright file. > > Please take a look I've seen that, but they need to make

Re: RFS: aescrypt

2011-08-04 Thread mezgani ali
Benoît, i've received a message from upstream, telling that the application is totally free, without any restriction for modification or redistribution. in the fact, i insert message text in the copyright file. Please take a look 2011/8/4 Benoît Knecht > Benoît Knecht wrote: > > mezgani ali wro

Re: RFS: aescrypt

2011-08-04 Thread Benoît Knecht
Benoît Knecht wrote: > mezgani ali wrote: > > Sorry, the upload of the package failed but, if you check the new sources > > now, you'll find that the copyright is changed and i've joined the text mail > > of new license, from upstream author. > > Upstream doesn't seem to understand that their "fre

Re: RFS: aescrypt

2011-08-04 Thread Benoît Knecht
Hi Ali, mezgani ali wrote: > Sorry, the upload of the package failed but, if you check the new sources > now, you'll find that the copyright is changed and i've joined the text mail > of new license, from upstream author. Upstream doesn't seem to understand that their "freeware" license is not fr

Re: RFS: aescrypt

2011-08-04 Thread mezgani ali
Sorry, the upload of the package failed but, if you check the new sources now, you'll find that the copyright is changed and i've joined the text mail of new license, from upstream author. On Thu, Aug 4, 2011 at 8:49 AM, Andrey Rahmatullin wrote: > On Thu, Aug 04, 2011 at 06:13:52AM +, mezga

Re: RFS: aescrypt

2011-08-04 Thread Andrey Rahmatullin
On Thu, Aug 04, 2011 at 06:13:52AM +, mezgani ali wrote: > My motivation for maintaining this package is: [fill in]. Huh? > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/a/aescrypt > - Source repository: deb-src http://mentors.debian.net/de

Re: RFS: aescrypt

2011-08-03 Thread mezgani ali
Please find here the new version of the package: Dear mentors, I am looking for a sponsor for my package "aescrypt". * Package name: aescrypt Version : 3.05-1 Upstream Author :Glenn Washburn Paul E. Jones Mauro Gilardi * URL

Re: RFS: aescrypt

2011-08-03 Thread Andrey Rahmatullin
On Wed, Aug 03, 2011 at 04:16:23PM +, mezgani ali wrote: > * License : gpl3 No, it's GPL2+ for aes.c and sha256.c and non-free "freeware" license (not explicitly allowing modification) for other files. -- WBR, wRAR signature.asc Description: Digital signature

RFS: aescrypt

2011-08-03 Thread mezgani ali
Dear mentors, I am looking for a sponsor for my package "aescrypt". * Package name: aescrypt Version : 3.05-1 Upstream Author :Glenn Washburn Paul E. Jones Mauro Gilardi * URL : http://www.aescrypt.com/ * License : gpl3

Re: RFS: aescrypt

2011-01-16 Thread mezgani ali
Please take a look to my new packages ;) It seems to be Ok Regards, On Mon, Jan 17, 2011 at 1:36 AM, Fernando Lemos wrote: > 2011/1/16 mezgani ali : > > > > What about README.Debian and README.source can i keep them empty and in > the > > case when the tools comes with a > > readme.txt file ? >

Re: RFS: aescrypt

2011-01-16 Thread Fernando Lemos
2011/1/16 mezgani ali : > > What about README.Debian and README.source can i keep them empty and in the > case when the tools comes with a > readme.txt file ? [snip] Please make sure you read this (read it all if you haven't yet): http://www.debian.org/doc/maint-guide/ The things you are asking

Re: RFS: aescrypt

2011-01-16 Thread mezgani ali
What about README.Debian and README.source can i keep them empty and in the case when the tools comes with a readme.txt file ? 2011/1/17 Fernando Mercês > Ali, > > I'm not a mentor, but I believe that your questions can be answered by > entire reading this article: > http://people.debian.org/~c

Re: RFS: aescrypt

2011-01-16 Thread Fernando Mercês
Ali, I'm not a mentor, but I believe that your questions can be answered by entire reading this article: http://people.debian.org/~codehelp/ Best regards, @Fernando Mercês Linux Registered User #432779 www.mentebinaria.com.br http://linuxreversing.org http://so

Re: RFS: aescrypt

2011-01-16 Thread mezgani ali
Hi Jonathan, I thank you first for your suggestions, well i fixed most of them and here i have some questions On Mon, Jan 17, 2011 at 12:05 AM, Jonathan Wiltshire wrote: > Hi, > > I'm not in a position to sponsor your package, but I started reviewing it > and found several problems: > > On Sun,

Re: RFS: aescrypt

2011-01-16 Thread Jonathan Wiltshire
Hi, I'm not in a position to sponsor your package, but I started reviewing it and found several problems: On Sun, Jan 16, 2011 at 09:08:28PM +, mezgani ali wrote: > I am looking for a sponsor for my package "aescrypt". > > * Package name: aescrypt > Version : 3.05-1 > Upstrea

RFS: aescrypt

2011-01-16 Thread mezgani ali
Dear mentors, I am looking for a sponsor for my package "aescrypt". * Package name: aescrypt Version : 3.05-1 Upstream Author : Glenn Washburn , Paul E. Jones , Mauro Gilardi * URL : http://www.aescrypt.com/ * License : gpl Section : utils It b