gb pidgin-musictracker with dpkg-dev 1.17.1 (was: Re: Bug#727131: pidgin-musictracker: FTBFS: /bin/sh: 1: Syntax error: "(" unexpected)
On 2013-10-23 06:14, Craig Small wrote:
> On Tue, Oct 22, 2013 at 04:25:23PM +0200, Niels Thykier wrote:
>> dpkg-buildflags: unknown option `--export=cmdline'
> $ dpkg-buildflags --export=cmdline
> CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security" CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security" FFLAGS="-g -O2" GCJFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4" LDFLAGS="-Wl,-z,relro"
>
> So, which version of dpkg-dev are you using?
s/you/buildds/ and at least kfreebsd-i386 was using dpkg-dev 1.16.10,
which could definitely explain it.
> I have 1.17.1 which has this flag. 1.17.0 introduced it.
> That came out in July. Shouldn't the buildds be using the latest
> version of things so we don't get this sort of regression?
>
> - Craig
>
Well, "shouldn't you had a versioned build-depends if you depend of a
recent feature" :). On a more serious note; the "base" system (e.g.
build-essential) used by the buildds need to be upgraded manually[1]. So
generally it is a very good idea to add versioned dependencies -
especially for stuff like dpkg.
Dear build admins; please upgrade dpkg-dev in your chroots and then:
gb pidgin-musictracker_0.4.22-3 . ALL -amd64 -armhf -i386
(or schedule it now with an --extra-depends 'dpkg-dev (>= 1.17.1)').
~Niels
[1] Or something like that; not entirely sure what the deal is here -
just remember the perl5.18 transition required the buildd admins to
upgrade their buildds.
Reply to: