On 16 Apr 2025, at 21:56, Karl Berry wrote:
>1. build intltool out-of-tree from a fresh tarball with automake 1.17.0
>
> Where did you get this intltool, precisely? Not that it's likely to
> matter, granted, but for purposes of reproducing ...
The intltool 0.51.0 tarball on launchpad[1].
> A
Is there a way to get more visibility into what autom4te is doing?
autom4te --help lists various options (at a glance: --verbose, --debug,
--trace=AM_TRY_LOG, who knows what else). I've never actually understood
autom4te in the slightest, sorry to say. Maybe best to bring it up on
bug-autoc...
Hi Eric and all,
eb> now questioning why Debian ever needed a patch to rip UPDATED out of
eb> the manual in the name of reproducibility.
Me too.
If the mtime isn't changed, then the original UPDATED should be
unchanged, and there's no problem.
If the mtime is intentionally changed by a patch or
Hi Ross - continuing on bug-automake from your report at
https://lists.gnu.org/archive/html/automake/2025-04/msg2.html.
(No reason to bother platform-testers with this.)
> I repeated my tests and rebuilds of existing source trees that have
> been configured with 1.70 still break for me
On Tue, Apr 15, 2025 at 07:55:08PM +0200, Santiago Vila wrote:
> El 15/4/25 a las 14:52, Eric Blake escribió:
> > I'm not sure the exact process Debian uses to do downstream builds,
> > but my guess is that it involves a downstream git repository for their
> > patches to be applied on top of the up
