Your message dated Fri, 25 Apr 2014 10:04:16 +0000
with message-id <[email protected]>
and subject line Bug#744657: fixed in sdate 0.4
has caused the Debian Bug report #744657,
regarding sdate: 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 [email protected]
immediately.)
--
744657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744657
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:sdate
Version: 0.3.1+nmu1
User: [email protected]
Usertags: autoreconf
The package fails to build on ppc64el (powerpc64le-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
powerpc64le in the configure, aclocal.m4 and/or libtool.m4 file(s)
should print some lines. It is not enough to just update the
config.guess and config.sub files.
The full build log can be found at:
http://people.debian.org/~doko/logs/ppc64el-20140414/buildlog_ubuntu-trusty-ppc64el.sdate_0.3.1+nmu1_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.
[...]
cd obj && ./libtool --finish
/build/buildd/sdate-0.3.1+nmu1/debian/sdate/usr/lib/sdate
PATH="$PATH:/sbin" ldconfig -n
/build/buildd/sdate-0.3.1+nmu1/debian/sdate/usr/lib/sdate
----------------------------------------------------------------------
Libraries have been installed in:
/build/buildd/sdate-0.3.1+nmu1/debian/sdate/usr/lib/sdate
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
cd objfake && ./libtool --finish
/build/buildd/sdate-0.3.1+nmu1/debian/sdate/usr/lib
PATH="$PATH:/sbin" ldconfig -n
/build/buildd/sdate-0.3.1+nmu1/debian/sdate/usr/lib
----------------------------------------------------------------------
Libraries have been installed in:
/build/buildd/sdate-0.3.1+nmu1/debian/sdate/usr/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
dh_installchangelogs
dh_installdocs
dh_lintian
dh_compress
dh_strip
dh_strip debug symbol extraction: not enabling -a because /CurrentlyBuilding
exists
dh_strip debug symbol extraction: all non-arch-all packages for this build
platform ppc64el: sdate
dh_strip debug symbol extraction: packages to act on: sdate
dh_strip debug symbol extraction: ignored packages:
sdate has no unstripped objects, ignoring
find: `/build/buildd/sdate-0.3.1+nmu1/debian/sdate-dbgsym': No such file or
directory
/usr/bin/pkg_create_dbgsym: nothing in
/build/buildd/sdate-0.3.1+nmu1/debian/sdate-dbgsym and no dbgdepends, ignoring
chmod 4644 debian/sdate/usr/lib/libsdate.so.0.0.1
chmod: cannot access 'debian/sdate/usr/lib/libsdate.so.0.0.1': No such file or
directory
make: *** [binary-arch] Error 1
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error
exit status 2
--- End Message ---
--- Begin Message ---
Source: sdate
Source-Version: 0.4
We believe that the bug you reported is fixed in the latest version of
sdate, 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.
Christoph Berg <[email protected]> (supplier of updated sdate 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: Fri, 25 Apr 2014 10:05:19 +0200
Source: sdate
Binary: sdate
Architecture: source amd64
Version: 0.4
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg <[email protected]>
Changed-By: Christoph Berg <[email protected]>
Description:
sdate - never ending September date
Closes: 744657
Changes:
sdate (0.4) unstable; urgency=medium
.
* B-D on dh-autoreconf and update rules file to use dh --with autoreconf.
Closes: #744657.
Checksums-Sha1:
43cf0fd709c5c2cbedc8f018adefa34b3ef9e75b 1507 sdate_0.4.dsc
2c339dd8f42d3a1d6342208b8ba95cf5385aa688 225702 sdate_0.4.tar.gz
aa31fd6dbf048257465f28736fb690d0e0806a4b 10238 sdate_0.4_amd64.deb
Checksums-Sha256:
187882995f0b4e5459bd1f0f905787204f25737d8d828199dd02d3028c9248f3 1507
sdate_0.4.dsc
40cd6eb73688421282aed2338c89bfb82f0be181f0c156acb96a8847d0587d5a 225702
sdate_0.4.tar.gz
758b2086c775a20bf32f1ff11e427741fcc9c1625f15a1eb41114eab64a9213c 10238
sdate_0.4_amd64.deb
Files:
fd4a180c17ee27af691b5d476a55defb 1507 utils optional sdate_0.4.dsc
1fad9d51a73e1ccfd86c03f539fb9419 225702 utils optional sdate_0.4.tar.gz
03eaffcf5178d4aca929f47a593115e1 10238 utils optional sdate_0.4_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJTWi5UAAoJEExaa6sS0qeui5cP/i8xxuWK0h7V6U/nrzLtfpMx
vz3/AJY0ai7+NTp2Q7dfY0iXfG3UsoGNeiRSmf2aU1L8DVJKJ2ocGPnjPLO/I6MY
uEs2IdioQyTkCgGDrmJsxotwkTHNDpiKbGlzsalsXsXc6Eje53OHV69R3Sx93/XU
QTBF+3PnrKdsKI/hr6eOMjyLlBpjKakI5QAAMVih2cv0e06N2G3/T0Og7iNOgU39
1gLPkU1wob5UFbr+jhPCMkQK1pl8FPxdBP9jJD7jnWy+LgGyYM9fI8DTkfumQ1DR
JwS/NakrHPuh7iWe/S2VAX3K7ueZquP0Ltr4GgSTw4J+mqSnVSkFEpWH2usmGr7j
bs6ESqlPBT1tpi8Ubd0ZhYzXn91wUzfFvqzR1gQ+5VnYCt9NEFdL3FdySgzHXZxO
NJBgPOHAI2Srl3BDbAA3DA3foO1Vg142CRPfDZAMqGnhA8MmdL8nQO5naOrn5GUW
7FinsgtEIEKJ2jfraRRDih2gOlsZXjtLAtDzEi8IiEZV7VEpM/WtTImvE2r4t3ok
sEZtlkWzfdIRDOAtJJGC0mBETGM/0lES6C6iU6h+WPh3Z3l8leMz87Z4yxawUMJu
qR74TQFW6lEvJQlsJlwfigyjTDoefzbqEelwz2QJKWLUFFOi+LidTP8JH39WqPgd
zdCQVRPiERkBji7PqXqj
=acNU
-----END PGP SIGNATURE-----
--- End Message ---
