Closed kloczek closed 4 years ago
I’ll need more details here; where did you get the sources?
What we have in the Fedora lookaside cache is necessarily a tarball generated from the dist
target. The tagged commit also has nothing that references the older version.
I'm not using Fedora.
I';m using tagged tar ball https://github.com/abrt/satyr/archive/0.26.tar.gz + patch which dissabllows regenerate ac/am/lt files by use git versioning.
--- a/configure.ac~ 2019-10-11 12:17:15.000000000 +0100
+++ b/configure.ac 2019-11-21 13:01:29.608177236 +0000
@@ -1,4 +1,4 @@
-AC_INIT([satyr], m4_esyscmd([cat ./satyr-version]), [crash-catcher@fedorahosted.org])
+AC_INIT([satyr], [0.29], [crash-catcher@fedorahosted.org])
AC_CANONICAL_TARGET
AC_CONFIG_HEADERS([lib/config.h])
AM_INIT_AUTOMAKE([-Wall -Werror foreign])
Cannot find in am files what dist/distchech targets adds to packad source tree to add that fragment to my build procedure on top of tagged tar ball (can you point on that?).
If some files are needed for test suite why they are not part of the git repo?
OK .. I see that wrong version reported by test suite is caused by not updated my patch :P
Also as you can see below version reported by test suite is wrong (satyr 0.29)