[Debian-med-packaging] Bug#857900: scythe: binNMUs always FTBFS
Adrian Bunk
bunk at debian.org
Thu Mar 16 11:08:01 UTC 2017
On Thu, Mar 16, 2017 at 11:34:25AM +0100, Andreas Tille wrote:
> Hi Adrian,
Hi Andreas,
> On Thu, Mar 16, 2017 at 10:43:35AM +0200, Adrian Bunk wrote:
> > Source: scythe
> > Version: 0.994-3
> > Severity: serious
> >
> > https://buildd.debian.org/status/package.php?p=scythe&suite=sid
> >
> > ...
> > cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic -DVERSION="0.994-3+b1" -std=gnu99 -fPIC -c src/scythe.c -o scythe.o
> > src/scythe.c: In function 'main':
> > <command-line>:0:17: error: 'b1' undeclared (first use in this function)
> > ...
> > Makefile:31: recipe for target 'scythe.o' failed
> > make[2]: *** [scythe.o] Error 1
>
> I've just upgraded my pbuilder chroot to make sure I can reproduce the
> issue but I can't. Build runs smoothly and recreates the package on
> amd64.
>
> Any further hints how to track down the issue?
you need a binNMU version with +b1 in debian/changelog for seeing the FTBFS.
The VERSION string "0.994-3+b1" is interpreted as arithmetic expression
0.994 - 3 + b1
A less fatal variant of this bug is already present in the
non-binNMU version in stretch/unstable:
$ scythe --version
scythe version -2.006
scythe.c treating version numbers as floating point is pretty strange.
And due to that, 0003-Get-package-version-from-dpkg-parsechangelog.patch
causes these funny problems.
> Kind regards
>
> Andreas.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
More information about the Debian-med-packaging
mailing list