On Wed, Dec 13, 2023 at 01:41:01PM +0200, Eli Zaretskii wrote:
> > We'll probably have to investigate each of these changes separately to
> > see where they occur. I am probably not going to fix them all in one
> > go.
> >
> > First, could you confirm which version of Texinfo you got these results
> > with.
> >
> > I tested with Texinfo 7.1, ran configure with the same configure line
> > as you, then ran "make distclean".
>
> Let me point out that "make distclean" is NOT supposed to revert the
> tree to a clean state as far as Git is concerned. "make distclean" is
> supposed to remove any files built or modified as part of building a
> release tarball, and release tarballs can legitimately include files
> that are not versioned, and therefore are not managed by Git. So
> looking at the results of "git status" is not the correct way of
> finding files that "make distclean" is supposed to remove. Instead,
> one should:
>
> . create a release tarball
> . unpack and build the release tarball in a separate directory
> . run "make distclean" in the directory where the tarball was built
> . unpack the release tarball in another directory, and then compare
> that other directory with the one where you run "make distclean"
>
I've just done this on the release/7.1 branch and the results look
good.
I think we have investigated everything we can now based on the original
report, without getting more information. I suspect there is some more
Debian-specific context about how the package is being built that we are
missing.
Regarding these changes:
modified: man/makeinfo.1
modified: man/texi2dvi.1
modified: man/texindex.1
These files aren't tracked in the official git repository. Since they
are distributed files that can also be rebuilt, it is always possible
that they are modified if the rules to rebuild them trigger. This
seems unavoidable.
