Your message dated Fri, 26 Sep 2014 01:00:56 +0200
with message-id <54249ea8.2090...@rezozer.net>
and subject line symmetrica: FTBFS: autoreconf: 'configure.ac' or 
'configure.in' is required
has caused the Debian Bug report #762730,
regarding symmetrica: FTBFS: autoreconf: 'configure.ac' or 'configure.in' is 
required
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
762730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: symmetrica
Version: 2.0+ds-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Automatic builds of symmetrica have been failing:

   debian/rules build-arch
  dh build-arch --with autoreconf --parallel
     dh_testdir -a -O--parallel
     dh_autoreconf -a -O--parallel
  autoreconf: 'configure.ac' or 'configure.in' is required
  dh_autoreconf: autoreconf -f -i returned exit code 1
  make: *** [build-arch] Error 2
  debian/rules:7: recipe for target 'build-arch' failed
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

The problem appears to be that the override_dh_auto_clean target
leaves the tree unpatched, and as such missing configure.ac (which
comes from upstream-autotoolization.patch).  It's not clear that you
need any explicit patch manipulation when using format "3.0 (quilt)",
but if you still do for some reason, please ensure that your patches
are actually in place for the main build* targets.

Thanks!

--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Folks,

at the time of writing, the fix is effective.

Enjoy,
Jerome
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJUJJ6VAAoJEIC/w4IMSybjhlcIANOYBGMBvBHu9QGefKpA1SCY
yJAPNal8EdVtHUsTzh6n/cKNl5wJXGyuiEuQlKXnsYp+Lu+24La4Oi4nmMjuyTBm
wF6iWB77Qlz2QWmUk4xUYwJh2viFfFZE/3n3KcfNfrQkVrcQxaNg/a162LuLBlXx
TLYT3CZ/REZXrEDhTwkJgW3MdZ7KS064Yfk4ODTUngWIlWRf2/U/ueyiOzlFX09u
kBg2/MX7Ycr+MmO0uCagPjZKP9Vv7uV6BkrCqOmxeATlzDApcaG0A1c+o0bkO2RR
jUlxM5r+033CrDSByggRCE/LAGdS7NsGBeDYWrI8tJb49YAxsP1Yj0rV32F0IsI=
=AnFa
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to