Re: Quilt 3.0 format and .pc direcotry

2014-01-04 Thread Andreas Tille
On Fri, Jan 03, 2014 at 05:06:53PM +0100, Dariusz Dwornikowski wrote: I am not yet keeping the package in git, so I am using plain debuild and .pc lands in source package. I will just delete it prior to debuilding. There is no need to delete it but if you do you need to quilt pop -a before

Re: Problem with unusual upstream source directory

2014-01-04 Thread Dariusz Dwornikowski
@Gabriele thank you. When I add -i to debuild will Debian build servers do the same ? @Paul good idea but I'll contact upstream, however they are not so responsive. On 4 January 2014 06:52, Paul Wise p...@debian.org wrote: On Sat, Jan 4, 2014 at 12:18 AM, Dariusz Dwornikowski wrote: So I

Bug#734094: marked as done (RFS: tinyows/1.1.0-3 [ITP])

2014-01-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 Jan 2014 16:28:09 + with message-id e1vzu53-0002x2...@quantz.debian.org and subject line closing RFS: tinyows/1.1.0-3 [ITP] has caused the Debian Bug report #734094, regarding RFS: tinyows/1.1.0-3 [ITP] to be marked as done. This means that you claim that the

Bug#734191: RFS: libgeo-proj4-perl/1.04-1

2014-01-04 Thread Bas Couwenberg
Package: sponsorship-requests Severity: normal Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package libgeo-proj4-perl Package name: libgeo-proj4-perl Version : 1.04-1 Upstream

Re: Bug#733987: RFS: dbab/1.0.1 [ITP] - dnsmasq-based ad-blocking using pixelserv

2014-01-04 Thread T o n g
On Thu, 02 Jan 2014 16:20:57 -0500, Tong Sun wrote: Package: sponsorship-requests Severity: normal Dear mentors, I am packing The Best Ad Blocking Method[1] into a Debian package and am looking for a sponsor for my package dbab, which starts with reviewing it first. [1]

Re: Please help me fix these build problems

2014-01-04 Thread T o n g
Thanks. On Fri, 03 Jan 2014 11:34:10 -0500, Stephen M. Webb wrote: W: zh-autoconvert: hardening-no-relro usr/bin/autogb To fix this one, you need to add $CPPFLAGS and $LDFLAGS to your linker command line in your Makefile. And add the following at the top of the Makefile as well: # use

Re: Please help me fix these build problems

2014-01-04 Thread Stephen M. Webb
On 01/04/2014 05:04 PM, T o n g wrote: Thanks. On Fri, 03 Jan 2014 11:34:10 -0500, Stephen M. Webb wrote: W: zh-autoconvert: hardening-no-relro usr/bin/autogb To fix this one, you need to add $CPPFLAGS and $LDFLAGS to your linker command line in your Makefile. And add the following at

pkg-has-shlibs-control-file-but-no-actual-shared-libs triggered by a private shared library

2014-01-04 Thread T o n g
Hi, pkg-has-shlibs-control-file-but-no-actual-shared-libs is sometimes triggered for packages with a private shared library due to a bug in Debhelper That seems to have bitten me. E: zh-autoconvert: pkg-has-shlibs-control-file-but-no-actual-shared-libs W: zh-autoconvert:

Requirement for compat level 9

2014-01-04 Thread T o n g
On Sat, 04 Jan 2014 17:22:49 -0500, Stephen M. Webb wrote: The instructions available on the web are for older versions of the build infrastructure. The debhelper(7) manual page does mention dpkg-buildflags flags are passed through at compat level 9, but it isn't necessarily obvious what

Re: Requirement for compat level 9

2014-01-04 Thread Stephen M. Webb
On 01/04/2014 05:31 PM, T o n g wrote: On Sat, 04 Jan 2014 17:22:49 -0500, Stephen M. Webb wrote: The instructions available on the web are for older versions of the build infrastructure. The debhelper(7) manual page does mention dpkg-buildflags flags are passed through at compat level 9,

Re: Requirement for compat level 9

2014-01-04 Thread T o n g
On Sat, 04 Jan 2014 18:39:23 -0500, Stephen M. Webb wrote: How can I make sure my building environment is at compat level 9? From he debhelper(7) manpage: Tell debhelper what compatibility level to use by writing a number to debian/compat. For example, to turn on v9 mode: %

Re: Requirement for compat level 9

2014-01-04 Thread Russ Allbery
T o n g mlist4sunt...@yahoo.com writes: I know I can force compat level to 9 just like that. But what I want to know is how to make sure my building environment is up to that level. E.g., in a very old Debian system, e.g., potato, you can set debian/ compat to 9, but I don't think it will

Re: Requirement for compat level 9

2014-01-04 Thread Stephen M. Webb
On 01/04/2014 06:48 PM, T o n g wrote: On Sat, 04 Jan 2014 18:39:23 -0500, Stephen M. Webb wrote: I know I can force compat level to 9 just like that. But what I want to know is how to make sure my building environment is up to that level. E.g., in a very old Debian system, e.g., potato,

Bug#733455: marked as done (RFS: grap/1.44-1 [ITA])

2014-01-04 Thread Debian Bug Tracking System
Your message dated Sun, 05 Jan 2014 04:26:11 + with message-id e1vzfhv-0008ta...@quantz.debian.org and subject line closing RFS: grap/1.44-1 [ITA] has caused the Debian Bug report #733455, regarding RFS: grap/1.44-1 [ITA] to be marked as done. This means that you claim that the problem has