Your message dated Mon, 12 Jun 2017 23:05:10 +0300
with message-id <20170612200509.b4jpacqqrkbymnon@localhost>
and subject line Closing obsolete autotools/autoreconf requests
has caused the Debian Bug report #727847,
regarding encfs: 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.)
--
727847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727847
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:encfs
Version: 1.7.4-2.4
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.encfs_1.7.4-2.4build2_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.
[...]
Setting up python3 (3.3.2-14ubuntu1) ...
running python rtupdate hooks for python3.3...
running python post-rtupdate hooks for python3.3...
Setting up dh-python (1.20131003-1) ...
Setting up apparmor-easyprof (2.8.0-0ubuntu31) ...
Setting up dh-apparmor (2.8.0-0ubuntu31) ...
Setting up debhelper (9.20130921ubuntu1) ...
Processing triggers for libc-bin ...
Checking correctness of source dependencies...
Toolchain package versions: libc6-dev_2.17-93ubuntu4 make_3.81-8.2ubuntu3
dpkg-dev_1.16.12ubuntu1 gcc-4.8_4.8.2-1ubuntu2 g++-4.8_4.8.2-1ubuntu2
binutils_2.23.90.20131017-1ubuntu1 libstdc++-4.8-dev_4.8.2-1ubuntu2
libstdc++6_4.8.2-1ubuntu2
------------------------------------------------------------------------------
dpkg-source: warning: -sn is not a valid option for
Dpkg::Source::Package::V3::quilt
gpgv: Signature made Fri Apr 26 18:19:12 2013 UTC using RSA key ID 8B3C16AE
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./encfs_1.7.4-2.4build2.dsc
dpkg-source: info: extracting encfs in encfs-1.7.4
dpkg-source: info: unpacking encfs_1.7.4.orig.tar.gz
dpkg-source: info: unpacking encfs_1.7.4-2.4build2.debian.tar.gz
dpkg-source: info: applying fix_bashisms
dpkg-source: info: applying i18n_updates
dpkg-source: info: applying debian-changes-1.7.4-2.3
dpkg-buildpackage: source package encfs
dpkg-buildpackage: source version 1.7.4-2.4build2
dpkg-source --before-build encfs-1.7.4
dpkg-buildpackage: host architecture arm64
/usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
/usr/bin/make distclean || true
make[1]: Entering directory `/build/buildd/encfs-1.7.4'
make[1]: *** No rule to make target `distclean'. Stop.
make[1]: Leaving directory `/build/buildd/encfs-1.7.4'
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.
#-autoreconf -fi
./configure --build=aarch64-linux-gnu --prefix=/usr
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... Invalid configuration `aarch64-linux-gnu':
machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
This email closes autotools/autoreconf in packages that have
successfully been built on all current release architectures.
debhelper defaults to updating autotools files since January 2016,
which automatically fixed many of these bugs and makes explicit
updating for these packages obsolete.
debhelper compat 10 defaults to running autoreconf,
making manual adding of dh-autoreconf mostly obsolete.
Updating to compat 10 is a better solution than adding dh-autoreconf,
and compat < 10 is expected to become a lintian warning before buster.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--- End Message ---
