Bug#744552: marked as done (yasr: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4)
Your message dated Sat, 19 Apr 2014 21:42:35 +0000
with message-id <E1Wbd1v-00031q-QR@franck.debian.org>
and subject line Bug#728012: fixed in yasr 0.6.9-4
has caused the Debian Bug report #728012,
regarding yasr: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4
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 owner@bugs.debian.org
immediately.)
--
728012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728012
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:yasr
Version: 0.6.9-3
User: debian-devel@lists.debian.org
Usertags: autoreconf
The package fails to build on arm64 (aarch64-linux-gnu), because the
config.{guess,sub} files are out of date, and are not updated during
the build. If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.
- For dh, call dh --with autoreconf.
- For cdbs based build systems, include
/usr/share/cdbs/1/rules/autoreconf.mk
- For other rules files, call dh_autoreconf before calling
configure (in the build or configure target), and call
dh_autoreconf_clean before dh_clean in the clean target.
For combining autoreconf and autotools_dev, see bug #698765.
After the build on any architecture, and before a clean, a grep for
aarch64 in the config.sub file(s) should print some lines.
The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20140414/buildlog_ubuntu-trusty-arm64.yasr_0.6.9-3_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.
Please note that these builds were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.
See https://wiki.debian.org/qa.debian.org/FTBFS for a guide how to
address these.
[...]
sysconfdir='/etc'
target_alias=''
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE_NAME "yasr"
#define PACKAGE_TARNAME "yasr"
#define PACKAGE_VERSION "0.6.9"
#define PACKAGE_STRING "yasr 0.6.9"
#define PACKAGE_BUGREPORT "mgorse@alum.wpi.edu"
#define PACKAGE "yasr"
#define VERSION "0.6.9"
#define STDC_HEADERS 1
#define HAVE_LIBUTIL 1
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_FCNTL_H 1
#define HAVE_SYS_IOCTL_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_UNISTD_H 1
#define HAVE_UTMPX_H 1
#define HAVE_LOCALE_H 1
#define HAVE_PTY_H 1
#define TIME_WITH_SYS_TIME 1
#define RETSIGTYPE void
#define HAVE_SELECT 1
#define HAVE_STRDUP 1
#define HAVE_STRTOL 1
#define HAVE_INET_PTON 1
#define HAVE_OPENPTY 1
#define HAVE_FORKPTY 1
#define HAVE_LOGIN_TTY 1
#define HAVE_CFMAKERAW 1
configure: exit 1
dh_auto_configure: ./configure --build=aarch64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libexecdir=${prefix}/lib/yasr --disable-maintainer-mode --disable-dependency-tracking --datadir=/etc returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 25
make[1]: Leaving directory `/build/buildd/yasr-0.6.9'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: yasr
Source-Version: 0.6.9-4
We believe that the bug you reported is fixed in the latest version of
yasr, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 728012@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Thibault <sthibault@debian.org> (supplier of updated yasr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 19 Apr 2014 22:21:46 +0200
Source: yasr
Binary: yasr
Architecture: source amd64
Version: 0.6.9-4
Distribution: unstable
Urgency: low
Maintainer: Debian Accessibility Team <debian-accessibility@lists.debian.org>
Changed-By: Samuel Thibault <sthibault@debian.org>
Description:
yasr - General-purpose console screen reader
Closes: 728012
Changes:
yasr (0.6.9-4) unstable; urgency=low
.
* Bump Standards-Version to 3.9.5 (no changes).
* control: depend on autotools-dev.
* rules: pass --with autotools_dev to dh (Closes: #728012).
Checksums-Sha1:
85764d3795f5cc76e84078e3076261c50f316a23 1922 yasr_0.6.9-4.dsc
c28323cb328dfa4fe56b2efdba06bc5aa4b9bf06 3699 yasr_0.6.9-4.diff.gz
2077867e229f5744a5b1bd6e5ddb93326644a232 55380 yasr_0.6.9-4_amd64.deb
Checksums-Sha256:
19644400c9d0134ecf5c713006682538562da1b8bf19f942b479ae5eec2d7e91 1922 yasr_0.6.9-4.dsc
8ea2c1372dc5d37e6b3049a03d98b2d93edfc0f59e7979730c4681578513237a 3699 yasr_0.6.9-4.diff.gz
18de8402e1bf15951ae7291bede67f36d149fe5da4eb9656181cfdc48796315b 55380 yasr_0.6.9-4_amd64.deb
Files:
c6718221d7886bd18748dbba9fb0f4ff 1922 admin extra yasr_0.6.9-4.dsc
3ede32cb9bc437476834632b20c30076 3699 admin extra yasr_0.6.9-4.diff.gz
d497434d8e79d4e4d00dbef7a1718968 55380 admin extra yasr_0.6.9-4_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJTUtuGAAoJEJTQtYw0gxjVi3IP/1+wMVjOJvP9wFL3SCTEnlZw
NkYqtxdJzVdMK9Frh+rGXqIII8gOse2ALet/0ga1Hiv4Q3B+hGt4IbzXNAWXiX0u
/tiilGjdMIkNuOFxu/hLKpbMWYG3+fkw7WJkomuVInv+9BzdK97FAaZpLmhC/J+d
OPBKPvmutm2/7NMKNOZeNH7U9d9Rwo8HVNJ9ju2sSTXHCb25A27Ts6IUoV9S2I5L
2AHnwAQ2jedswnpe8Cki57a3/aFTDWg6bLhLTNAyNe4XzTDgxhtdCNn7bO3DtHuM
LdNgjgbni+NEKJMWGmgzgsFaQnFEiIQhOuelwCuyXCJPWuTMnh6YbRZpQ09kELk5
q9tL2gF0AsCmZh4jETv3DYd6u4qItGkAYzMYsKj84rC/JQXmcbblKNEKlDpWh/cs
xQ8uf4IaZx2kReZrKI8Ce+B58f95r+EDpgj7ZTvL7fEV4OjVzzu8poYRVvA9to1K
TK0oG4w46J+c5Mz7XYI2yTiGOp4kxgn9e33C4G4e2uAlnYigb+1aaBSODGYgoeMH
DSMdBv6kzvzO8Wjzo5DURUcd2Xoawwdje9uEPSfgBcLxFa7MB5+xhSuXmm2N5tlM
s39v90yyY+IXjMW2zZ9LepY6h4l6x4xb/E94I1KzOyGXnOMMuHG36V9+yY6VhQlj
+0V0sKIa3bENA1GqGuk7
=/heU
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: