Opened 7 years ago
Closed 7 years ago
#55126 closed defect (fixed)
Incorrect version number 2.4.0 in port manpage (s/b 2.4.2)
Reported by: | todofixthis (Phoenix) | Owned by: | |
---|---|---|---|
Priority: | Low | Milestone: | |
Component: | base | Version: | 2.4.2 |
Keywords: | Cc: | neverpanic (Clemens Lang), raimue (Rainer Müller) | |
Port: |
Description (last modified by mf2k (Frank Schima))
- Install MacPorts 2.4.2
- Run
man port
- Scroll to the bottom.
The version number at the bottom of the manpage is 2.4.0 instead of 2.4.2
Change History (7)
comment:1 Changed 7 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:2 Changed 7 years ago by mf2k (Frank Schima)
comment:3 Changed 7 years ago by mf2k (Frank Schima)
I can confirm this bug is in 2.4.2 but not in the latest port version from GitHub.
comment:4 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | neverpanic added |
---|
Looks like this applies to all MacPorts manpages. Should we be regenerating the manpages automatically when we build, or should we be manually updating them when we change the version number, as we do when we manually run autogen.sh after changing the version number?
comment:5 Changed 7 years ago by raimue (Rainer Müller)
Cc: | raimue added |
---|
I guess 2.4.0 was what I had on disk when tagging the release and generating the 2.4.2 release tarball. We should add a step to regenerate all man pages after incrementing the version number to ReleaseProcess.
comment:6 Changed 7 years ago by raimue (Rainer Müller)
comment:7 Changed 7 years ago by raimue (Rainer Müller)
Resolution: | → fixed |
---|---|
Status: | new → closed |
release-2.4: [931c3ed39b15e5aa56eb9ad4fdef2a19bd3d4e9a/macports-base]
Thank you for noticing and the report, but we cannot fix this for 2.4.2 as the problem is in the tag and release tarball. I am closing this ticket as the additional documentation should ensure we will not miss this next time.
It works correctly for me. Please tell us the output of the following: