Your message dated Tue, 13 Oct 2015 08:19:23 + (UTC)
with message-id <185683049.4291184.1444724364041.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#792144: RFS: cunit/2.1-2.dfsg-3 -- Unit Testing
Library for C [ITA]
has caused the Debian Bug report #792144,
regarding RFS: cun
On Mon, Oct 12, 2015 at 02:28:13PM +, Gianfranco Costamagna wrote:
> Hi Azat,
>
>
> last thing: can you please fix the autopkgtestsuite?
> http://debomatic-amd64.debian.net/distribution#unstable/cunit/2.1-3-dfsg-1/autopkgtest
>
> seems that it is not finding the correct header file...
>
> t
Hi Azat,
last thing: can you please fix the autopkgtestsuite?
http://debomatic-amd64.debian.net/distribution#unstable/cunit/2.1-3-dfsg-1/autopkgtest
seems that it is not finding the correct header file...
thanks a lot!
(this should be the last showstopper)
cheers,
G.
Il Lunedì 12 Ottobre 2
On Thu, Oct 01, 2015 at 02:17:29PM +, Gianfranco Costamagna wrote:
> Hi Azat,
>
>
>
> >No problem, replaced version in d/changelog and d/NEWS to
> >"2.1-3+dfsg-1".
>
>
> wonderful
> >Done using d/copyright, thanks.
>
>
> this is not really correct.
>
> I see you remove Makefiles in copy
Hi Azat,
>No problem, replaced version in d/changelog and d/NEWS to
>"2.1-3+dfsg-1".
wonderful
>Done using d/copyright, thanks.
this is not really correct.
I see you remove Makefiles in copyright, but why?
that files-excluded needs to be used for non dfsg files, not for autogenerated
stuf
On Sun, Sep 27, 2015 at 10:38:27AM +0200, Gianfranco Costamagna wrote:
> Hi,
>
> sorry for the long wait!
Hi, no problem!
> I did a deep review, and I guess I found the last "showstoppers"
>
> 1) Upstream revision seems to be "2.1-3" and you seem to have
> introduced a first dfsg revision
> so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
sorry for the long wait!
I did a deep review, and I guess I found the last "showstoppers"
1) Upstream revision seems to be "2.1-3" and you seem to have
introduced a first dfsg revision
so it becomes 2.1-3+dfsg
and then the debian revision,
On Wed, Sep 09, 2015 at 08:59:26AM +, Gianfranco Costamagna wrote:
> Hi, I'm referring to:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792144#54
Hm, I thought that I dropped autoconf from B-D, but seems that this was
in some separate branch, anyway fixed that now.
As for *.css, I t
Hi, I'm referring to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792144#54
and (sorry for that I forgot to send the mail)
to the need to mark the package as multiarch where needed
https://wiki.debian.org/Multiarch/Implementation
also, please rebase the changelog into one entry.
(I mean,
On Wed, Sep 09, 2015 at 06:26:03AM +, Gianfranco Costamagna wrote:
> (please also address issues from other emails)
I look through emails again, and couldn't find any non addressed issues,
could please duplicate it?
> http://mentors.debian.net/debian/pool/main/c/cunit/cunit_2.1-3-dfsg1.dsc
>
On Wed, Sep 09, 2015 at 06:30:27AM +, Gianfranco Costamagna wrote:
> Another issue you should address:
>
>
> I duplicate-long-description
> libcunit1-dev libcunit1 libcunit1-ncurses-dev libcunit1-ncurses libcunit1-doc
>
> (you might append something like "this is the development package" "th
Another issue you should address:
I duplicate-long-description
libcunit1-dev libcunit1 libcunit1-ncurses-dev libcunit1-ncurses libcunit1-doc
(you might append something like "this is the development package" "this is the
common
documentation" or so)
feel free to steal from python-pyqtgraph or
(please also address issues from other emails)
http://mentors.debian.net/debian/pool/main/c/cunit/cunit_2.1-3-dfsg1.dsc
quoting changelog:
+ * Bump to 2.1-3
+ * Fix versions
I see two patches dropped
and the watch file updated (diff between this version and your previous one,
not complete
On Tue, Sep 08, 2015 at 08:48:45PM +, Gianfranco Costamagna wrote:
> Hi,
>
> well something has been buried by my MUA.
>
> There is a new upstream release, can you please update it?
Okay, done.
> BTW there is a problem in versioning:
>
> -2.dfsg is bad, because it seems only Debian revisio
Hi,
well something has been buried by my MUA.
There is a new upstream release, can you please update it?
BTW there is a problem in versioning:
-2.dfsg is bad, because it seems only Debian revision, while
-2 is upstream and dfsg is Debian.
please use two "-" but I'm not sure if it works or not.
Hi again,
>Hm, so if I will replace all targets with dh_*_auto, and will add
>override_* for them when required, this will not work for rules.d since
>it will call the same again and again, no? Or do you suggesting get rid
>off that rules.d stuff?
yes, or merge them in the main rules file :)
Hi,
>Yes, you are right, dh-autoreconf is enough.
so please drop the other one :)
>Hm, according to lintian(1):
> "For binary packages, Lintian looks for overrides in a file named
> usr/share/lintian/overrides/ inside the binary package, where
> is the name of the binary package."
>
On Mon, Sep 07, 2015 at 05:50:46PM +0300, a3at.m...@gmail.com wrote:
> On Mon, Sep 07, 2015 at 01:14:45PM +, Gianfranco Costamagna wrote:
> > Hi,
> >
> > quick review:
> >
> > 1) lintian is complaining about no compat level set.
> > I don't see any problem in the compat level set, not sure
>
On Mon, Sep 7, 2015 at 2:14 PM, Craig Small wrote:
> On Mon, Sep 07, 2015 at 11:21:35AM +0300, Azat Khuzhin wrote:
>> On Sun, Jul 12, 2015 at 11:33:32AM +1000, Riley Baird wrote:
>> > d/copyright:
>> > -In the LGPL license text, you've accidentally referred to the wrong
>> > license:
>> > You sho
On Mon, Sep 07, 2015 at 01:14:45PM +, Gianfranco Costamagna wrote:
> Hi,
>
> quick review:
>
> 1) lintian is complaining about no compat level set.
> I don't see any problem in the compat level set, not sure
> if a bug in lintian or something else...
>
> 2) d/rules: please use the new dh for
On Mon, Sep 07, 2015 at 01:14:45PM +, Gianfranco Costamagna wrote:
> Hi,
>
> quick review:
>
> 1) lintian is complaining about no compat level set.
> I don't see any problem in the compat level set, not sure
> if a bug in lintian or something else...
> 2) d/rules: please use the new dh forma
Hi,
quick review:
1) lintian is complaining about no compat level set.
I don't see any problem in the compat level set, not sure
if a bug in lintian or something else...
2) d/rules: please use the new dh format, it should be trivial to convert.
3) d/control: do you really need autoconf as b-d?
On Mon, Sep 07, 2015 at 11:21:35AM +0300, Azat Khuzhin wrote:
> On Sun, Jul 12, 2015 at 11:33:32AM +1000, Riley Baird wrote:
> > d/copyright:
> > -In the LGPL license text, you've accidentally referred to the wrong
> > license:
> > You should have received a copy of the GNU General Public License
Changes since the last upload:
* New maintainer. (Closes: #763096).
* Fix pkg-config file is broken (Closes: #782366).
* Bump Standards version to 3.9.6
* Bump debhelper to version 9
* Migrate to git
* copyright: link to [L]GPL-2 instead of versionless [L]GPL
* copyright: migrate to DEP-5 (machin
On Sun, Jul 12, 2015 at 11:33:32AM +1000, Riley Baird wrote:
> > I am looking for a sponsor for my package "cunit"
>
> Hi!
>
> I'm not a DD, so I can't sponsor your package, but I had a look, and
> here are some notes:
Hi,
Thanks for you comments, by some reason I didn't see your email when you
> I am looking for a sponsor for my package "cunit"
Hi!
I'm not a DD, so I can't sponsor your package, but I had a look, and
here are some notes:
d/control:
-The link to your git repository doesn't seem to work.
d/copyright:
-In the LGPL license text, you've accidentally referred to the wrong
l
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "cunit"
Package name: cunit
Version : 2.1-2.dfsg-3
Upstream Author : Jerry St.Clair
Anil Kumar
URL : http://cunit.sourceforge.net/
License
Hi Philipp,
Philipp Benner <[EMAIL PROTECTED]>:
> This probably is a good idea as to show the ftp-masters that this has
> been checked. I added this statement to debian/copyright:
>
> "The documentation is distributed under the GNU Free Documentation
> License. It does not contain any secondary se
> > cunit (2.1-0.dfsg-2) unstable; urgency=low
> >
> > * added watch file version mangle
> > * new README.Debian-source
> > * documentation is distributed under the GNU FDL
> >
> Where this in the _change_ in this log entry?
> If you mean the change in debian/copyright, then say so, be more
Hi Phillip,
Philipp Benner Philipp Benner <[EMAIL PROTECTED]>:
> CUnit 2.1-0.dfsg-2 is now available at
> http://mentors.debian.net/debian/pool/main/c/cunit
>
> I had to change debian/copyright since the documentation
> actually is distributed under the GNU FDL.
>
> Here is the changelog:
>
> cuni
CUnit 2.1-0.dfsg-2 is now available at
http://mentors.debian.net/debian/pool/main/c/cunit
I had to change debian/copyright since the documentation
actually is distributed under the GNU FDL.
Here is the changelog:
cunit (2.1-0.dfsg-2) unstable; urgency=low
* added watch file version mangle
> Ok, good work. Uploaded.
>
> Some suggestions for your next version:
> * I think you should explain in a Readme.Debian file, what and why was
> been removed from upstream tarball.
> * Are all dh_* calls needed in debian/rules?
Ok. Thanks for uploading.
Regards
--
Philipp Benner
signature.
Hi Philipp,
Philipp Benner <[EMAIL PROTECTED]>:
> > But I think you should rename your repacked tarball by adding
> > "dfsg" to upstream version number to show the remove of (probably)
> > non free stuff.
>
> Done.
>
Ok, good work. Uploaded.
Some suggestions for your next version:
* I think you s
> But I think you should rename your repacked tarball by adding "dfsg" to
> upstream version number to show the remove of (probably) non free
> stuff.
Done.
I uploaded the new version.
Regards
--
Philipp Benner
signature.asc
Description: Digital signature
Hi Philipp,
Philipp Benner <[EMAIL PROTECTED]>:
> > But there are *.dsp files in package libcunit1-doc with:
> > "Microsoft Developer Studio Generated Build File" in it. Could they
> > be leagaly distributed?
> > Could you explain this.
>
> Not sure about it but probably not. Anyway, I added a rul
> There are also directories ".dep" in it. Are they useful?
Sorry, I misunderstood you. I added 'dh_installexamples
--exclude=.deps' to debian/rules to exlude those directories.
The new package is at mentors.debian.net:
http://mentors.debian.net/debian/pool/main/c/cunit
--
Philipp Benner
sign
Hi Erik,
> But there are *.dsp files in package libcunit1-doc with:
> "Microsoft Developer Studio Generated Build File" in it. Could they be
> leagaly distributed?
> Could you explain this.
Not sure about it but probably not. Anyway, I added a rule to
get-orig-source to remove them since they ar
Hi Philipp,
Philipp Benner Philipp Benner <[EMAIL PROTECTED]>:
> The new package has been uploaded:
> http://mentors.debian.net/debian/pool/main/c/cunit/
>
Your package builds fine.
But there are *.dsp files in package libcunit1-doc with:
"Microsoft Developer Studio Generated Build File" in it. C
On (01/10/06 11:09), Philipp Benner wrote:
> The new package has been uploaded:
> http://mentors.debian.net/debian/pool/main/c/cunit/
Hi,
Looks good to me, I believe it is ready for sponsoring.
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key
> * You need a versioned build-dep on dpkg-dev to use ${binary:Version},
> apologies for not mentioning it before.
> http://lists.debian.org/debian-mentors/2006/09/msg00228.html
Fixed.
> * You should use a "." on a line on it's own between paragraphs in the
> long description.
I
On (19/09/06 19:30), Philipp Benner wrote:
> On Tue, 19 Sep 2006 17:46:35 +0100
> James Westby <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
Can I suggest to metion that you have uploaded a new version if you do
when you reply to comments, and mention the URL as well, it makes it
clearer what is going on
On Tue, 19 Sep 2006 17:46:35 +0100
James Westby <[EMAIL PROTECTED]> wrote:
Hi,
thanks for your suggestions.
>
> * Please use ${binary:Version} and ${source:Version} in preference to
> ${Source-Version} in debian/control.
> * I would like some more "meat" in the descriptions.
> * Lose
[A question at the end for all list members...]
On (19/09/06 17:33), Philipp Benner wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "cunit".
>
> * Package name: cunit
Hi,
I can't sponsor the package, but I have a few comments.
* Please use ${binary:Version} and ${so
Dear mentors,
I am looking for a sponsor for my package "cunit".
* Package name: cunit
Version : 2.1-0-1
Upstream Author : [EMAIL PROTECTED]
* URL : http://cunit.sourceforge.net
* License : LGPL
Section : libs
It builds these binary packages:
libcuni
44 matches
Mail list logo
