RFS: siege (updated package) - after initial mentor comments

2009-03-25 Thread Tristan Greaves

Dear mentors,

I am looking for a sponsor for the new version 2.67-1
of my package siege.

It builds these binary packages:
siege  - Http regression testing and benchmarking utility

The package appears to be lintian clean.

The upload would fix these bugs: 521029, 521034

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/s/siege
- Source repository: deb-src http://mentors.debian.net/debian unstable main contrib 
non-free

- dget http://mentors.debian.net/debian/pool/main/s/siege/siege_2.67-1.dsc


Many thanks for the advice given so far.  I have worked through the lintian 
warnings
and sorted those out.  I have also taken the time to update the source to be 
based
on the latest available upstream.

However, there is a problem, and I seek your advice.

I have commented out one quilt patch for now.  It was a minor issue, but I 
would not
want this package being uploaded until it is in there, to avoid regression 
problems.

The patch in question modifies Makefile.in.  This in turn forces the usual auto*
stuff to happen.

The problems are:

1.	For some reason, the latest upstream version of this package is using automake-1.6 
(as opposed to 1.9 as it did previously).  Is this version still

available as it didn't come up when I did a quick search...

2.  When the autobuild stuff happens, naturally all the related files are 
now
considered modified.  Therefore lintian complains before it isn't done directly 
by
one of the quilt patches.

Any suggestions most welcome.

Kind regards,

Tris.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: RFS: siege (updated package) - after initial mentor comments

2009-03-25 Thread Jonathan Wiltshire
On Wed, Mar 25, 2009 at 03:32:01PM +, Tristan Greaves wrote:
 1.For some reason, the latest upstream version of this package is using 
 automake-1.6 (as opposed to 1.9 as it did previously).  Is this version 
 still
 available as it didn't come up when I did a quick search...

Looks like you can choose from 1.4, 1.7, 1.8 or 1.9.
I don't understand why a newer upstream is using an older automake though?

 2.When the autobuild stuff happens, naturally all the related files are 
 now
 considered modified.  Therefore lintian complains before it isn't done 
 directly by
 one of the quilt patches.

Files that were deleted during build don't show up in the diff.gz, so: rm the
modified files in your clean target, and lintian won't complain (to make
sure double builds work, you might have to copy things back from auto*
in your configure target).

-- 
Jonathan Wiltshire

PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3  A903 CA6B EA3E DB80 0B52


signature.asc
Description: Digital signature


Re: RFS: siege (updated package) - after initial mentor comments

2009-03-25 Thread Tristan Greaves

Jonathan Wiltshire wrote:

On Wed, Mar 25, 2009 at 03:32:01PM +, Tristan Greaves wrote:
1.	For some reason, the latest upstream version of this package is using 
automake-1.6 (as opposed to 1.9 as it did previously).  Is this version 
still

available as it didn't come up when I did a quick search...


Looks like you can choose from 1.4, 1.7, 1.8 or 1.9.
I don't understand why a newer upstream is using an older automake though?


I double-checked just to be sure, but the original source is definitely that
way.


2.  When the autobuild stuff happens, naturally all the related files are 
now
considered modified.  Therefore lintian complains before it isn't done directly 
by
one of the quilt patches.


Files that were deleted during build don't show up in the diff.gz, so: rm the
modified files in your clean target, and lintian won't complain (to make
sure double builds work, you might have to copy things back from auto*
in your configure target).


Okay.  For now, I've worked around this issue as the patch in question does not
really apply now that I've adjusted the rules anyway.

I've uploaded a fresh copy.

Is this all set to be uploaded now?  If so, what happens next?

Many thanks,

Tris.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org