Your message dated Fri, 01 Nov 2013 16:49:38 +0000
with message-id <[email protected]>
and subject line Bug#727926: fixed in lunar-date 2.4.0-2
has caused the Debian Bug report #727926,
regarding lunar-date: update config.{sub,guess} for the AArch64 port
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 [email protected]
immediately.)


-- 
727926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727926
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:lunar-date
Version: 2.4.0-1
Severity: normal
User: [email protected]
Usertags: arm64

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 autotools_dev (yes, underscore).

  - For other rules files, call dh_autotools-dev_updateconfig before
    calling configure (in the build or configure target), and call
    dh_autotools-dev_restoreconfig before calling 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-20131027/buildlog_ubuntu-trusty-arm64.lunar-date_2.4.0-1_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

[...]
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh='${SHELL} /build/buildd/lunar-date-2.4.0/install-sh'
libdir='${prefix}/lib/aarch64-linux-gnu'
libexecdir='${prefix}/lib/aarch64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p='/bin/mkdir -p'
oldincludedir='/usr/include'
pdfdir='${docdir}'
pkgpyexecdir=''
pkgpythondir=''
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
pyexecdir=''
pythondir=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME "lunar-date"
#define PACKAGE_TARNAME "lunar-date"
#define PACKAGE_VERSION "2.4.0"
#define PACKAGE_STRING "lunar-date 2.4.0"
#define PACKAGE_BUGREPORT "[email protected]"
#define PACKAGE_URL ""
#define LUNAR_DATE_MAJOR_VERSION 2
#define LUNAR_DATE_MINOR_VERSION 4
#define LUNAR_DATE_MICRO_VERSION 0
#define LUNAR_DATE_BINARY_AGE 400
#define STDC_HEADERS 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 
--libdir=${prefix}/lib/aarch64-linux-gnu 
--libexecdir=${prefix}/lib/aarch64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-gtk-doc --enable-vala-bindings returned 
exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory `/build/buildd/lunar-date-2.4.0'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

--- End Message ---
--- Begin Message ---
Source: lunar-date
Source-Version: 2.4.0-2

We believe that the bug you reported is fixed in the latest version of
lunar-date, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
YunQiang Su <[email protected]> (supplier of updated lunar-date 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 02 Nov 2013 00:30:44 +0800
Source: lunar-date
Binary: liblunar-date-dev liblunar-date-2.0-0 liblunar-date-dbg 
liblunar-date-doc gir1.2-lunar-date-2.0
Architecture: source amd64 all
Version: 2.4.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Chinese Team <[email protected]>
Changed-By: YunQiang Su <[email protected]>
Description: 
 gir1.2-lunar-date-2.0 - GObject Introspection for lunar-date
 liblunar-date-2.0-0 - Chinese Lunar library based on GObject
 liblunar-date-dbg - Chinese Lunar library based on GObject - debug symbols
 liblunar-date-dev - Chinese Lunar library based on GObject - develop files
 liblunar-date-doc - Chinese Lunar library based on GObject - API documents
Closes: 713902 727926
Changes: 
 lunar-date (2.4.0-2) unstable; urgency=low
 .
   * Remove DMUA stanza.
   * Update policy version to 3.9.5: no modification needed.
   * Update Git URL to be canonical.
   * dh with option autotools_dev to fix build on arm64 and
     maybe other new archs (Closes: 727926).
   * Fix a typo in package description (Closes: #713902)
Checksums-Sha1: 
 fadd84cd7fd0933b3776f7899502fa681b10b3dc 1952 lunar-date_2.4.0-2.dsc
 0134e7ba73fee26d62cfe43d95f927e9246a3aec 2409 lunar-date_2.4.0-2.debian.tar.gz
 454185f1b5d117b65d06d7c400674c3c5ba7a54c 41642 
liblunar-date-dev_2.4.0-2_amd64.deb
 ee15f0644f8a2868266fc0ba4de58b8c9ed2646d 17928 
liblunar-date-2.0-0_2.4.0-2_amd64.deb
 2cd3dac92531660c2f599f4d82222d39f2e2e795 25874 
liblunar-date-dbg_2.4.0-2_amd64.deb
 ab32057929a1e4e397f515a578a97f9d6eeaa518 11910 
liblunar-date-doc_2.4.0-2_all.deb
 f1c6accc24b214e0a5dbd8d653996464f7a8d1a1 5834 
gir1.2-lunar-date-2.0_2.4.0-2_amd64.deb
Checksums-Sha256: 
 6654bb1acb1077aab268cbeffd564e6de63a102bd846474f07fd5da80a08fdee 1952 
lunar-date_2.4.0-2.dsc
 6cf17cbc9474111cf76b8eb66db2e349ce2b94bd0672b102c2a5412f5435a6d1 2409 
lunar-date_2.4.0-2.debian.tar.gz
 af5379f16c89c6b8aa978359b27919b2282abb7c5217c163b2353812d55fd0e9 41642 
liblunar-date-dev_2.4.0-2_amd64.deb
 bf246ea10e4a10d00a38e90f3cbc224eeedc48e136960c1aecc44005fb4fa9a3 17928 
liblunar-date-2.0-0_2.4.0-2_amd64.deb
 f77240e93095849e700a3f02e60289d270bf5689f315aaad9fc4b5115a63ffaa 25874 
liblunar-date-dbg_2.4.0-2_amd64.deb
 e93a67b3eb4806485d0d975ee3b97da0cbe9a4683c0949dde41b9bac80b256fe 11910 
liblunar-date-doc_2.4.0-2_all.deb
 d5e21c41b0e30f1d839f2fd1d3a5287d4c5bcad14eb72435b28d3f1addff4459 5834 
gir1.2-lunar-date-2.0_2.4.0-2_amd64.deb
Files: 
 f270abed415c2708b4aded8b8682119b 1952 libs optional lunar-date_2.4.0-2.dsc
 2ea31520f3ffb68eaf3eaddef0830d84 2409 libs optional 
lunar-date_2.4.0-2.debian.tar.gz
 93944556fc7b2b67468afba777c3e2c8 41642 libdevel optional 
liblunar-date-dev_2.4.0-2_amd64.deb
 da83c27a4042eec63bf49a2de31a9524 17928 libs optional 
liblunar-date-2.0-0_2.4.0-2_amd64.deb
 f1ea3ca3b45625d0d2b3955d4ab53fe2 25874 debug extra 
liblunar-date-dbg_2.4.0-2_amd64.deb
 81055aaf0298fb42983541a2a50342eb 11910 doc optional 
liblunar-date-doc_2.4.0-2_all.deb
 fc63565422f198ed72bfc1a32bcf3556 5834 introspection optional 
gir1.2-lunar-date-2.0_2.4.0-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQEcBAEBCAAGBQJSc9mbAAoJECVrfCskLhmedhgIALeMGR8ih0k68QOOgKDy1rMG
frJN4d7ItbWW4yQC5Iks2hcUQ7lGz/h4IllOJAo0EiuXF+sg3zy56c7B5jAQzExN
//AaoZA74Di4+zH56/q2qswf2DNT87494HCmFJmaTpxyFFxmxSOcGzf3s34stTBU
LmQlX4SYipZOsPWlMjEMWcz3+MbxsW3VkX8Qp8QIXjQZUfFdQ1J71oIL0BmjF30d
wh5UtZsKnePDhfeTDKoKZhBeFSp0AGARwA2XEJEwYKC614G9TrfPgbd0ieXHoLO2
hFin3WYZcYirL7hJbb2i0WIFFqpg9yO7V2Z88yCII2vB8QcB2eHUEheuPde9KqQ=
=e1i9
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to