Bug#973150: emacs-async: FTBFS: Wrong type argument: stringp, nil
Source: emacs-async
Version: 1.9.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with elpa
> dh_update_autotools_config
> dh_autoreconf
> dh_auto_configure
> dh_auto_build
> make -j4
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -f async-bytecomp.elc async-pkg.elc async-test.elc async.elc dired-async.elc smtpmail-async.elc
> emacs -Q -batch --eval "(let ((generated-autoload-file (expand-file-name \"async-autoloads.el\" \".\")) \
> (backup-inhibited t)) (update-directory-autoloads \".\"))"
> emacs -Q -batch -L . -f batch-byte-compile async-bytecomp.el async-pkg.el async-test.el async.el dired-async.el smtpmail-async.el
> Wrong type argument: stringp, nil
> make[1]: *** [Makefile:64: autoloads] Error 255
The full build log is available from:
http://qa-logs.debian.net/2020/10/27/emacs-async_1.9.4-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: