mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 22:01:23 -06:00
[GH-ISSUE #248] Version info in v2.1.2 is wrong #199
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#199
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kakra on GitHub (Feb 4, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/248
These lines in v2.1.2 tag are wrong:
53ebc47ace/cmake/Version.cmake (L4)Probably a merge glitch that slipped through...
Building this version results in the binary identifying itself as 2.2.0 while it isn't. I think this problem has also been there already in a previous version.
@AdrianKoshka commented on GitHub (Feb 4, 2019):
Yeah, forgot to update some metadata.
@yjqg6666 commented on GitHub (May 7, 2019):
so is the release version which should be 2.1.2 instead of 2.2.0.
@parkerlreed commented on GitHub (Jun 7, 2019):
Yeah 2.2.0 still links to https://github.com/debauchee/barrier/archive/v2.1.2.tar.gz
@AdrianKoshka commented on GitHub (Jun 7, 2019):
Yeah…it's not high priority and I'm on vacation right now…
@mirh commented on GitHub (Aug 14, 2019):
This is fixed.. I guess?
@shymega commented on GitHub (Aug 14, 2019):
As of commit
8e8b38b493, the version tag has been updated to 2.3.0. I can see from commit73c13ab023, the version tag is 2.2.0.@walker0643 How can we fix this? I'd rather not rewrite the Git history, but I'm not convinced there's any other way, given the nature of Git.
@mirh commented on GitHub (Aug 14, 2019):
... I don't know which commits you are picking up, but it seems just right here
https://github.com/debauchee/barrier/blob/v2.3.1/cmake/Version.cmake
@shymega commented on GitHub (Aug 14, 2019):
Didn't look look like it from my end.
@shymega commented on GitHub (Aug 14, 2019):
Ah.. I've just seen my repo is a few commits behind 😅 I guess we can close this issue now.