Bug#1044517: euslisp: Fails to build source after successful build

Lucas Nussbaum lucas at debian.org
Sun Aug 13 17:56:54 BST 2023


Source: euslisp
Version: 9.27+dfsg-7
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S
> -------------------------------------------------------------------------------------------------------------------------
> 
> dpkg-buildpackage: info: source package euslisp
> dpkg-buildpackage: info: source version 9.27+dfsg-7
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Kei Okada <kei.okada at gmail.com>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_auto_clean
> 	make -j8 clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> "-- GCC_MACHINE = x86_64-linux-gnu"
> "--      OS = Linux"
> "-- ARCHDIR = Linux64"
> "-- MAKEFILE = Makefile.Linux64"
> "--  EUSDIR = /<<PKGBUILDDIR>>"
> (cd lisp/image/jpeg/; make ARCH=Linux64 clean)
> make[2]: Entering directory '/<<PKGBUILDDIR>>/lisp/image/jpeg'
> make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
> rm -f /<<PKGBUILDDIR>>/Linux64/obj/jpegmemcd.o /<<PKGBUILDDIR>>/Linux64/obj/jmemsrc.o /<<PKGBUILDDIR>>/Linux64/obj/jmemdst.o /<<PKGBUILDDIR>>/Linux64/lib/jpegmemcd.so eusjpeg.c eusjpeg.h
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/lisp/image/jpeg'
> make -C lisp -f Makefile.Linux64 clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
> rm -fr /<<PKGBUILDDIR>>/data/* 
> rm -f /<<PKGBUILDDIR>>/Linux64/obj/* /<<PKGBUILDDIR>>/Linux64/lib/eusmap /<<PKGBUILDDIR>>/Linux64/lib/libeus* /<<PKGBUILDDIR>>/Linux64/bin/* l/constants.l.[co]\
> 	l/eusstart.l.[co] comp/builtins.l.[co] so_locations
> sh tool/clean-ch.sh
> rm -f c/makedate.c /<<PKGBUILDDIR>>/include
> rmdir --ignore-fail-on-non-empty /<<PKGBUILDDIR>>/Linux64/obj /<<PKGBUILDDIR>>/Linux64/lib /<<PKGBUILDDIR>>/Linux64/bin
> rmdir --ignore-fail-on-non-empty /<<PKGBUILDDIR>>/Linux64
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/lisp'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building euslisp using existing ./euslisp_9.27+dfsg.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  euslisp-9.27+dfsg/lisp/c/eus.c
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/euslisp_9.27+dfsg-7.diff.lklXsl
> dpkg-source: info: Hint: make sure the version in debian/changelog matches the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/euslisp_9.27+dfsg-7_unstable.log

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.



More information about the debian-science-maintainers mailing list