Hi Andreas,
Thanks for the note. Those files are generated automatically by the
gtk-doc-scan scripts - in this case at some point back in 2007. The
build process related to this was copied from the gtk library source
tree. In any case, I don't see why those files need to hang around, and
updated the makefile to clean them out.
Andy
On 01/09/2012 01:25 PM, Andreas Tille wrote:
Hi Andy,
as you can see the Debian packaged version of Amide recived a bug
report. I checked this problem and realised that the cause is not
connected to the outdated autotools (even if it would definitely help to
update these and call autoreconf).
The problem is that your release tarball contains some backup files
(find . -name "*.bak") which are cleaned in your clean target in
principle but obviosely the tarball was created without cleaning up the
source tree before. This is not only nasty in principly it just makes
us extra trouble in packaging. Would you please be so kind to clean
up the source tree before releasing the next version of amide?
Kind regards and thanks for your cooperation
Andreas.
On Tue, Dec 27, 2011 at 03:24:51PM +0100, Julian Taylor wrote:
Package: amide
Version: 1.0.0-1
Severity: minor
User: [email protected]
Usertags: qa-doublebuild
due to the regeneration of the autotools files the package fails to
build twice in a row.
please consider using dh-autoreconf to handle the regeneration which can
restore the original tree in clean for you.
_______________________________________________
Debian-med-packaging mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
