bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-22 Thread Mike Frysinger
On 21 Jan 2024 14:42, Karl Berry wrote: > I changed the pretest version to 1.16.90. Closing. thx bud. i appreciates you. -mike signature.asc Description: PGP signature

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-21 Thread Karl Berry
I changed the pretest version to 1.16.90. Closing.

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-16 Thread Sam James
"Zack Weinberg" writes: > On Sun, Jan 14, 2024, at 1:49 AM, Mike Frysinger wrote: >> On 13 Jan 2024 15:58, Karl Berry wrote: >>> Another alternative: when this came up 30-odd years ago, rms changed the >>> GNU maintainers doc to suggest x.y.90, .91, etc. for pretests. Doing >>> that would at le

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-16 Thread Zack Weinberg
On Sun, Jan 14, 2024, at 1:49 AM, Mike Frysinger wrote: > On 13 Jan 2024 15:58, Karl Berry wrote: >> Another alternative: when this came up 30-odd years ago, rms changed the >> GNU maintainers doc to suggest x.y.90, .91, etc. for pretests. Doing >> that would at least have the benefit of following

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-13 Thread Mike Frysinger
On 13 Jan 2024 15:58, Karl Berry wrote: > Another alternative: when this came up 30-odd years ago, rms changed the > GNU maintainers doc to suggest x.y.90, .91, etc. for pretests. Doing > that would at least have the benefit of following a recommendation, and > as a side effect, would also fix jami

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-13 Thread Karl Berry
there is nothing requiring or restricting the current version behavior other than "it's always been this way". True. but that doesn't mean it's better. No way to know what release or test scripts might be relying on the current convention. Changing for the sake of change doesn't se

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-12 Thread Mike Frysinger
On 06 Jan 2024 15:37, Karl Berry wrote: > Automake and other packages have used letters for pretests for decades, true ... > and it's not plausible to change now. eh ? there is nothing requiring or restricting the current version behavior other than "it's always been this way". but that doesn'

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-06 Thread Karl Berry
Carl - sorry, you'll need to adjust your script. Automake and other packages have used letters for pretests for decades, and it's not plausible to change now. Also, I have the impression that other packages use random git hexids in their pretest releases, which aren't numeric either. -k

bug#68274: automake 1.16j nonnumerical version confuses scripts

2024-01-05 Thread Carl Hansen
Building a package (happens to be "jami") , which runs a script it its build process that checks for automake expr: non-integer argument automake (GNU automake) 1.16j Fatal error: automake 1.7 or higher is required. Please set $AUTOMAKE to point to a newe