Bug#1052917: scala-mode-el: FTBFS: make[1]: *** [Makefile:55: clean] Error 2
Source: scala-mode-el
Version: 1:1.1.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with elpa
> dh_auto_clean
> make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> End of file during parsing
> rm -f *.elc .latest-* autoloads.el scala-mode- Error: end-of-file nil mapbacktrace(#f(compiled-function (evald func args flags) #<bytecode 0x943b01ebae87e2>)) debug-early-backtrace() debug-early(error (end-of-file)) read(#<buffer scala-mode-pkg.el>) (nth 2 (read (find-file "./scala-mode-pkg.el"))) (format "%s\n" (nth 2 (read (find-file "./scala-mode-pkg.el")))) (princ (format "%s\n" (nth 2 (read (find-file "./scala-mode-pkg.el"))))) command-line-1(("-L" "." "--eval" "(princ (format \"%s\\n\" (nth 2 (read (find-file \"./scala-mode-pkg.el\")))))")) command-line() normal-top-level().tar
> /bin/sh: 1: Syntax error: "(" unexpected
> make[1]: *** [Makefile:55: clean] Error 2
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/scala-mode-el_1.1.0-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Reply to: