Opened 5 years ago
Closed 5 years ago
#13071 closed Bugs (fixed)
Release commit not available anymore
Reported by: | Owned by: | James E. King, III | |
---|---|---|---|
Milestone: | To Be Determined | Component: | uuid |
Version: | Boost 1.55.0 | Severity: | Problem |
Keywords: | Cc: |
Description
The release 1.55.0 of boost points to the commit 8c395a888c2d77bdc91e956ef24a07c0c87cdd24 of uuid. However, this commit is not available!
The tag boost.1.55.0 in the uuid repository is pointing to commit 98cf8322aef86e6398dbac7f9cd6bf766621d645.
Change History (6)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:3 by , 5 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
I think you missed the point. In uuid the tag 'boost-1.55.0' is at 98cf832..., however in the boost repository for the tag 'boost-1.55.0' uuid is at 8c395a888c2d77bdc91e956ef24a07c0c87cdd24. As you already checked, this commit is not available.
Just try to checkout 'boost-1.55.0' of the boost repository:
git clone https://github.com/boostorg/boost.git
cd boost
git submodule init libs/uuid
git checkout boost-1.55.0
git submodule update libs/uuid
and the last step will fail with:
fatal: reference is not a tree: 8c395a888c2d77bdc91e956ef24a07c0c87cdd24
Unable to checkout '8c395a888c2d77bdc91e956ef24a07c0c87cdd24' in submodule path 'libs/uuid'
comment:4 by , 5 years ago
I see - this is a boost supermodule issue then. Since the supermodule repository does not have github issues enabled, I am going to email the boost developer mailing list with this issue for resolution and I will attach replies/resolution here. Thanks!
comment:5 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
comment:6 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I was able to find someone with that git hash in their fork and I pushed it up as the tag old-boost-1.55.0 and now your recipe to reproduce the issue no longer fails, so I am resolving this issue as fixed.
I do not see the same issue in my fork of uuid:
My guess is you have a an extra commit in your fork. This should be closed as invalid.