pspp-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v0.10.2-129-gf02c


From: Friedrich Beckmann
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v0.10.2-129-gf02c896
Date: Sun, 11 Jun 2017 15:03:25 -0400 (EDT)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU PSPP".

The branch, master has been updated
       via  f02c89686fbe706e2800a91d13933f1129ec5c36 (commit)
      from  e5ed663e9f1998c1c2409a668288d4e5d496beda (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit f02c89686fbe706e2800a91d13933f1129ec5c36
Author: Friedrich Beckmann <address@hidden>
Date:   Sun Jun 11 20:56:35 2017 +0200

    Fixed perl regression problem due to Version name - Fixes Bug #51218
    
    The regression failed in some perl tests due to an incompatible
    pspp version number. I changed to a version number that includes
    a "-". The problem is described in acinclude.m4. See
    
      The PSPP autobuilder appends a build number to the PSPP version number,
      e.g. "0.7.2-build40".  But Perl won't parse version numbers that contain
      anything other than digits and periods, so "-build" causes an error.  So 
we
      define $(VERSION_FOR_PERL) that drops everything from the hyphen onward.
      VERSION_FOR_PERL=`echo "$VERSION" | sed 's/-.*//'`
      AC_SUBST([VERSION_FOR_PERL])
    
    The version name was 0.10.5pre1 without a "-". Therefore the version name
    for perl results in a problem.

-----------------------------------------------------------------------

Summary of changes:
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
GNU PSPP



reply via email to

[Prev in Thread] Current Thread [Next in Thread]