Your message dated Mon, 15 Dec 2025 18:15:35 +0100 with message-id <aUBCN0SW-OzUMZgj@nuc> has caused the report #1043940, regarding alpine: Fails to build source after successful build to be marked as having been forwarded to the upstream software author(s) [email protected]
(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.) -- 1043940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043940 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Hello from Debian. Some time ago, there was a QA effort by Lucas Nussbaum to ensure that the clean target of Debian packages was correct. The alpine package was affected, and this was the error: > [...] > dpkg-source: warning: ignoring deletion of file pith/Makefile.in, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file pith/osdep/Makefile.in, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file pith/charconv/Makefile.in, > use --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > alpine-2.26+dfsg/web/src/Makefile > alpine-2.26+dfsg/web/src/alpined.d/Makefile > alpine-2.26+dfsg/web/src/pubcookie/Makefile > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/alpine_2.26+dfsg-1.diff.3mBJCF These kind of errors are first and foremost a problem in the Debian package, but in some cases, and I believe this is one of them, it may indicate a problem in the upstream makefiles. In this case one would wonder why ./configure; make; make clean would leave those three Makefiles there: web/src/Makefile web/src/alpined.d/Makefile web/src/pubcookie/Makefile instead of they being removed, which is what one would naturally expect from "make clean" when it's the case that those Makefiles are generated from their Makefile.in templates. Thanks.
--- End Message ---
