On Fri, 10 Jun 2016 17:56:13 +0000 (UTC) Gianfranco Costamagna
<costamagnagianfra...@yahoo.it> wrote:
> source: mercurial-buildpackage
> severity: serious
> version: 0.10-1
> tags: patch
> 
> Hi Darren,
> I had to patch the package on Ubuntu, because you have a parsechangelog that 
> doesn't take care of rebuilds, NMUs, or whatever.
> 
> In Ubuntu it seems fine now, the following patch
> diff -Nru mercurial-buildpackage-0.10.1/debian/changelog 
> mercurial-buildpackage-0.10.1ubuntu1/debian/changelog
> --- mercurial-buildpackage-0.10.1/debian/changelog      2014-10-28 
> 03:27:29.000000000 +0100
> +++ mercurial-buildpackage-0.10.1ubuntu1/debian/changelog       2016-06-10 
> 19:43:53.000000000 +0200
> @@ -1,3 +1,10 @@
> +mercurial-buildpackage (0.10.1ubuntu1) yakkety; urgency=medium
> +
> +  * Rebuild against libneko2.
> +  * Strip the "build*" and "ubuntu*" from changelog
> +
> + -- Gianfranco Costamagna <locutusofb...@debian.org>  Tue, 07 Jun 2016 
> 16:23:35 +0200
> +
> mercurial-buildpackage (0.10.1) unstable; urgency=low
> 
> * Fix ‘class not found’ FTBFS. (Closes: #719405)
> diff -Nru mercurial-buildpackage-0.10.1/debian/rules 
> mercurial-buildpackage-0.10.1ubuntu1/debian/rules
> --- mercurial-buildpackage-0.10.1/debian/rules  2012-02-25 20:10:58.000000000 
> +0100
> +++ mercurial-buildpackage-0.10.1ubuntu1/debian/rules   2016-06-07 
> 20:11:01.000000000 +0200
> @@ -2,7 +2,7 @@
> # debian/rules for mercurial-buildpackage.
> 
> PACKAGE := $(shell dpkg-parsechangelog | head -1 | cut -c9-)
> -CHANGELOG := $(shell dpkg-parsechangelog | sed -e '/^Version: /! d; s/^.* 
> //')
> +CHANGELOG := $(shell dpkg-parsechangelog | sed -e '/^Version: /! d; s/^.* 
> //' | sed '-e s/build.*//' | sed '-e s/ubuntu.*//')
> 
> clean:
> dh_testdir
> 
> 
> 
> of course something more appropriate is needed, but this should become 
> shortly an RC bug in Debian too.
> 
> Can you please give it a look?
> 
> the failure is:
> 
> ./macro-expand < MercurialImportDsc.man > mercurial-importdsc.1
> ./macro-expand < MercurialPristineTar.man > mercurial-pristinetar.1
> ./macro-expand < MercurialPort.man > mercurial-port.1
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> touch build-stamp
> [ "0.10.1build1" = 0.10.1 ]
> debian/rules:22: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

This broke in Debian because of binNMUs:

[ "0.10.1+b1" = 0.10.1 ]
debian/rules:22: recipe for target 'build-arch' failed

What is that check needed for anyway?

Emilio

Reply via email to