Follow-up Comment #1, bug #67933 (group groff): At 2026-01-19T07:34:49-0500, Colin Watson wrote: > The groff 1.24.0.rc1 tarball has these rather misleading files: > > $ cat .version > 1.23.0.rc1.1418-3e78f-dirty > $ cat .tarball-version > 1.23.0.5077-7dcc8 > > This confused my Debian packaging, which expects to be able to derive > the upstream version from .tarball-version; build-aux/git-version-gen > describes this file as "[containing] the version number assigned by > the maintainer", so that seems like a legitimate thing to do. Of > course I can easily override that, but perhaps you might like to > arrange that whatever generates these files does a better job with > pre-releases.
Thanks for the report. You already made me aware of the latter problem, but the former is a new one. Yes, maybe I can convince "dist-hook" or something like that to trash old ".version" files. The tarball (and directory) naming issue is one that needs humans to follow correct procedure for now, and I didn't. Here is my pending "fix" from my working copy. commit 9119a112c382b3316dd0b216c86b2b55f3d4cdad Author: G. Branden Robinson <[email protected]> Date: Sun Jan 18 18:46:27 2026 -0600 FOR-RELEASE: Add item; thanks to Ingo Schwarze. diff --git a/FOR-RELEASE b/FOR-RELEASE index 905ceca05..96d48bd4f 100644 --- a/FOR-RELEASE +++ b/FOR-RELEASE @@ -69,5 +69,12 @@ This file describes how to prepare 'groff' for a new release. * Run the "set-man-page-time-stamps" Makefile target from your build directory to fix up the stamps on the man pages. +* Build (and test!) a distribution archive with "make distcheck". It's + important to do this especially after tagging a first release + candidate, because this increments the version number visible in + installed file names (such as "/usr/share/groff/1.24.0") and in the + archive file, so that it unpacks to an appropriately named source + directory. + * groff 1.24.0: Edit the groff home page. Revise the sentence "Most commands installed by groff recognize this option." to say "All". _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?67933> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
