GNU bug report logs - #29376
automake gnits version check vs. gnulib's git-version-gen?

Previous Next

Package: automake;

Reported by: Bernhard Voelker <mail <at> bernhard-voelker.de>

Date: Tue, 21 Nov 2017 07:46:02 UTC

Severity: minor

To reply to this bug, email your comments to 29376 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-automake <at> gnu.org:
bug#29376; Package automake. (Tue, 21 Nov 2017 07:46:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Bernhard Voelker <mail <at> bernhard-voelker.de>:
New bug report received and forwarded. Copy sent to bug-automake <at> gnu.org. (Tue, 21 Nov 2017 07:46:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bernhard Voelker <mail <at> bernhard-voelker.de>
To: bug-automake <at> gnu.org
Cc: Eric Blake <eblake <at> redhat.com>, James Youngman <jay <at> gnu.org>,
 bug-gnulib <bug-gnulib <at> gnu.org>
Subject: automake gnits version check vs. gnulib's git-version-gen?
Date: Tue, 21 Nov 2017 08:44:53 +0100
At GNU findutils, we're trying to use gnulib's git-version-gen [1]
to derive the version string from the current git commit.

Until now, we've been using a 3-level versioning scheme X.Y.Z, e.g. the
latest tag was 'v4.6.0'.  Now for any non-release commit version
before the next release, 'git-version-gen' determines a version
like e.g. '4.6.0.149-2f6a' for the 149th commit past the v4.6.0 tag;
but the automake gnits check complains:

  ...
  running: AUTOPOINT=true LIBTOOLIZE=true autoreconf --verbose --install --force -I gl/m4  --no-recursive
  autoreconf: Entering directory `.'
  autoreconf: running: true --force
  autoreconf: running: aclocal -I gl/m4 --force -I gl/m4 -I m4
  autoreconf: configure.ac: tracing
  autoreconf: configure.ac: not using Libtool
  autoreconf: running: /usr/bin/autoconf --include=gl/m4 --force
  autoreconf: running: /usr/bin/autoheader --include=gl/m4 --force
  autoreconf: running: automake --add-missing --copy --force-missing
  configure.ac:95: installing 'build-aux/compile'
  configure.ac:51: installing 'build-aux/config.guess'
  configure.ac:51: installing 'build-aux/config.sub'
  configure.ac:46: installing 'build-aux/install-sh'
  configure.ac:46: installing 'build-aux/missing'
  configure.ac:195: installing 'build-aux/mkinstalldirs'
  Makefile.am: installing './INSTALL'
  configure.ac:25: error: version '4.6.0.149-2f6a' doesn't follow Gnits standards

So my question: aren't 3-level version strings allowed by the gnits check
in combination with gnulib's git-version-gen script?  Do we have to change
the strictness from gnits to gnu?

[1] https://git.sv.gnu.org/cgit/gnulib.git/tree/build-aux/git-version-gen

Thanks & have a nice day,
Berny






Information forwarded to bug-automake <at> gnu.org:
bug#29376; Package automake. (Wed, 22 Nov 2017 19:32:01 GMT) Full text and rfc822 format available.

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>, bug-automake <at> gnu.org
Cc: bug-gnulib <bug-gnulib <at> gnu.org>, James Youngman <jay <at> gnu.org>,
 Eric Blake <eblake <at> redhat.com>
Subject: Re: automake gnits version check vs. gnulib's git-version-gen?
Date: Wed, 22 Nov 2017 11:30:47 -0800
On 11/20/2017 11:44 PM, Bernhard Voelker wrote:
> So my question: aren't 3-level version strings allowed by the gnits check
> in combination with gnulib's git-version-gen script?  Do we have to 
> change
> the strictness from gnits to gnu?

I would think so, unless someone takes the time to change Automake so 
that gnits supports the new format of version strings that 
git-version-gen is generating.





Severity set to 'minor' from 'normal' Request was from Mathieu Lirzin <mthl <at> gnu.org> to control <at> debbugs.gnu.org. (Fri, 05 Jan 2018 01:52:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-automake <at> gnu.org:
bug#29376; Package automake. (Fri, 05 Jan 2018 03:16:02 GMT) Full text and rfc822 format available.

Message #13 received at 29376 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Lirzin <mthl <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: James Youngman <jay <at> gnu.org>, Eric Blake <eblake <at> redhat.com>,
 mail <at> bernhard-voelker.de, bug-gnulib <bug-gnulib <at> gnu.org>,
 29376 <at> debbugs.gnu.org
Subject: Re: bug#29376: automake gnits version check vs. gnulib's
 git-version-gen?
Date: Fri, 05 Jan 2018 04:15:11 +0100
Paul Eggert <eggert <at> cs.ucla.edu> writes:

> On 11/20/2017 11:44 PM, Bernhard Voelker wrote:
>> So my question: aren't 3-level version strings allowed by the gnits check
>> in combination with gnulib's git-version-gen script?  Do we have to
>> change
>> the strictness from gnits to gnu?
>
> I would think so, unless someone takes the time to change Automake so
> that gnits supports the new format of version strings that
> git-version-gen is generating.

Such change would be welcome.

Basically one would have to adapt the following regexp from automake.

--8<---------------cut here---------------start------------->8---
# This pattern recognizes a Gnits version id and sets $1 if the
# release is an alpha release.  We also allow a suffix which can be
# used to extend the version number with a "fork" identifier.
my $GNITS_VERSION_PATTERN = '\d+\.\d+([a-z]|\.\d+)?(-[A-Za-z0-9]+)?';
--8<---------------cut here---------------end--------------->8---

Ideally with some unit tests.  :-)

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37




This bug report was last modified 7 years and 161 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.