Bug 23440 - Info manuals state incorrect version
Summary: Info manuals state incorrect version
Status: RESOLVED FIXED
Alias: None
Product: binutils
Classification: Unclassified
Component: binutils (show other bugs)
Version: 2.31
: P2 minor
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-23 18:18 UTC by Eli Zaretskii
Modified: 2022-08-02 10:05 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eli Zaretskii 2018-07-23 18:18:37 UTC
All the Info manuals that come with the Binutils 2.31.1 tarball state version 2.30.90, not 2.31.  The file bfdver.texi does state the correct version, but it looks like it was updated after the Info files were generated.
Comment 1 Eli Zaretskii 2019-02-09 12:04:46 UTC
Seems like this was never fixed, and the latest Binutils 2.32 have the same problem: the version is stated as 2.31.90.
Comment 2 Sourceware Commits 2019-02-12 11:06:37 UTC
The master branch has been updated by Nick Clifton <nickc@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=04d7fa2132c05b962d85e2047646e15b8a490f4e

commit 04d7fa2132c05b962d85e2047646e15b8a490f4e
Author: Nick Clifton <nickc@redhat.com>
Date:   Tue Feb 12 11:05:21 2019 +0000

    Update description of how to make a release to include the use of the git clean command.
    
    	PR 23440
    	* README-how-to-make-a-release: Use git clean to delete spurious
    	files from the local source repository.
Comment 3 Nick Clifton 2019-02-12 11:12:00 UTC
Hi Eli,

  Sorry - this was basically a problem with my "how to make a release"
  document.  When the source tarball is created using the src-release.sh
  script, old versions of the .info files were already in the source
  directory.  (Left over from a previous use of src-release).  Since they
  are ignored by git I never noticed that they were there and had not
  been regenerated.

  I have now updated the how to document to recommend the use of the
  "git clean -fdx ." command to clean out the source directory before
  running the sec-release.sh script.  This should then force the script
  to rebuild the info files with the correct version number embedded.

Cheers
  Nick
Comment 4 Alan Modra 2022-08-02 10:05:59 UTC
.