MantisBT - Doomseeker |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004054 | Doomseeker | [All Projects] Bug | public | 2022-11-11 15:14 | 2024-11-03 18:55 |
|
| Reporter | WubTheCaptain | |
| Assigned To | Zalewa | |
| Priority | low | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | duplicate | |
| Platform | | OS | | OS Version | |
| Product Version | 1.3.3 | |
| Target Version | 1.5.0 | Fixed in Version | 1.4.1 | |
|
| Summary | 0004054: Doomseeker's Git repository doesn't have annotated tags for releases (only lightweight tags) |
| Description | Doomseeker's Git repository doesn't have annotated tags for releases. Only lightweight tags have been historically added to releases, which are meant for "private or temporary object labels".
Quote from git-tag(1)
Annotated tags are meant for release while lightweight tags are meant for private or temporary object labels. For this reason, some git commands for naming objects (like git describe) will ignore lightweight tags by default.
This caused me an issue when I was trying to git describe a version I was using for testing another issue, and received an error. |
| Steps To Reproduce | $ git describe
fatal: No annotated tags can describe 'd7638cb2d2811d215db44b981592bb1c8aab630b'.
However, there were unannotated tags: try --tags.
$ git describe --tags
1.3.3-49-gd7638cb2
$ git tag
0.10b
0.11.1b
0.11b
0.12.1b
0.12.2b
0.12b
0.1a
0.2a
0.3a
0.4b
0.5b
0.6b
0.7b
0.8.1b
0.8.1b-p1
0.8.1b-p2
0.8.1b-p3
0.8b
0.9b
1.0
1.1
1.1-p1
1.2
1.3
1.3.1
1.3.2
1.3.3 |
| Additional Information | 'https://git-scm.com/book/en/v2/Git-Basics-Tagging [^]'
I actually noticed this in January 2022, but didn't consider its impact: 0003959:0022107 |
| Tags | No tags attached. |
| Relationships | | duplicate of | 0003971 | closed | Zalewa | No annotated Git tags are available (since the repository migration from Mercurial to Git) |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2022-11-11 15:14 | WubTheCaptain | New Issue | |
| 2022-11-11 15:14 | WubTheCaptain | Note Added: 0022489 | |
| 2022-11-11 15:26 | WubTheCaptain | Note Added: 0022491 | |
| 2022-11-11 20:01 | Zalewa | Note Added: 0022495 | |
| 2022-11-11 20:02 | Zalewa | Note Edited: 0022495 | bug_revision_view_page.php?bugnote_id=22495#r13765 |
| 2023-01-25 22:20 | Zalewa | Target Version | => 1.5.0 |
| 2023-02-20 20:28 | Zalewa | Status | new => confirmed |
| 2023-02-25 21:30 | Zalewa | Note Added: 0022786 | |
| 2023-02-25 21:30 | Zalewa | Relationship added | duplicate of 0003971 |
| 2023-02-25 21:30 | Zalewa | Status | confirmed => resolved |
| 2023-02-25 21:30 | Zalewa | Fixed in Version | => 1.4.1 |
| 2023-02-25 21:30 | Zalewa | Resolution | open => duplicate |
| 2023-02-25 21:30 | Zalewa | Assigned To | => Zalewa |
| 2024-11-03 18:55 | Zalewa | Status | resolved => closed |
|
Notes |
|
|
|
|
I think the existing lightweight tags should be converted to annotated tags, to fix this issue. OpenPGP signatures are optional. |
|
|
|
|
|
|
|
(0022495)
|
|
Zalewa
|
2022-11-11 20:01
(edited on: 2022-11-11 20:02) |
|
We could use the tags to improve the versioning mechanism for the various components, so that I won't have to manually bump everything up. `git describe` is the tool for the job. But this requires proper naming scheme for the tags, and tagging each component separately. This would also incur some more complexity to the builder and the source code exporter, as of course the exported source cannot rely on `git describe` to do the job. I've done things like that before.
|
|
|
|
(0022786)
|
|
Zalewa
|
|
2023-02-25 21:30
|
|
|
I just noticed this is a duplicate of 0003971. Closing it and will use 0003971 to track the problem because of precedence. |
|