Re: libtasn1 | autoreconf on 4.2.21 sets wromg mtime for doc/libtasn1.texi (#57)
Read-only notification of GnuTLS library development activities <[email protected]>
| Newsgroups | gmane.comp.encryption.gpg.gnutls.devel |
|---|---|
| Message-ID | <[email protected]> |
Simon Josefsson commented: https://gitlab.com/gnutls/libtasn1/-/issues/57#note_2998087542 Thank you, great catch! Indeed `makeinfo` shouldn't be a required tool when building. It seems getting this right is rather tricky... I noticed that Bruno Haible's recent `git-merge-changelog` package uses a `version.sh` for similar information. It feels a bit redundant because the information is in `NEWS`. I wonder why not any of our CI/CD jobs caught this. I'll see if it is possible to reproduce. My initial idea to solve this is to avoid using git to find out the last commit date, and just use the last release date from `NEWS` instead. I'm not yet sure what the best fix to avoid touching the file when building from a tarball though. Maybe touching the file should go into `./bootstrap` instead of `./configure`. -- Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/libtasn1/-/issues/57#note_2998087542 You're receiving this email because of your account on gitlab.com. _______________________________________________ Gnutls-devel mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnutls-devel