Your message dated Fri, 14 Oct 2016 11:50:41 +0000
with message-id <e1bv10b-0003n2...@franck.debian.org>
and subject line Bug#835369: Removed package(s) from unstable
has caused the Debian Bug report #542082,
regarding dsyslog: 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 ow...@bugs.debian.org
immediately.)


-- 
542082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dsyslog
Version: 0.6.0
User: debian-de...@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.dsyslog_0.6.0build2_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.

[...]
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
[ ! -f Makefile ] || /usr/bin/make distclean
rm -f config.sub config.guess
dh_clean 
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
dh_testdir
# Add here commands to configure the package.
ln -sf /usr/share/misc/config.sub config.sub
ln -sf /usr/share/misc/config.guess config.guess
./configure --host=aarch64-linux-gnu --build=aarch64-linux-gnu --prefix=/ 
--mandir=\${prefix}/usr/share/man --infodir=\${prefix}/usr/share/info 
--sbindir=\${prefix}/usr/sbin --sysconfdir=\${prefix}/etc 
--libdir=\${prefix}/usr/lib --datadir=\${prefix}/usr/share --disable-rpath 
CFLAGS="-Wall -g -O2"
checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether aarch64-linux-gnu-gcc accepts -g... yes
checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... aarch64-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking build system type... Invalid configuration `aarch64-linux-gnu': 
machine `aarch64' not recognized
configure: error: /bin/bash autoconf/config.sub aarch64-linux-gnu failed
make: *** [configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

--- End Message ---
--- Begin Message ---
Version: 0.6.0+nmu2+rm

Dear submitter,

as the package dsyslog has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/835369

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to