Hi Santiago,

Is there any reason why the make clean command should remove Makefiles. To me the easier fix is not to build web alpine, just add '--without-tcl' as one of the options of the configure script.

  Does this address this issue to your satisfaction.

--
Eduardo

On Mon, 15 Dec 2025, Santiago Vila wrote:

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.


Reply via email to