Boost C++ Libraries: Ticket #13071: Release commit not available anymore

Fri, 04 Aug 2017 01:48:11 GMT

I do not see the same issue in my fork of uuid:

svtbuild@dvm:~/boost/libs/uuid$ git checkout boost-1.55.0

Note: checking out 'boost-1.55.0'.

HEAD is now at 98cf832... fixed bug in sha1.hpp for messages longer than 536,870,912 bytes, ticket #7128

svtbuild@dvm:~/boost/libs/uuid$ git show 8c395a888c2d77bdc91e956ef24a07c0c87cdd24

My guess is you have a an extra commit in your fork. This should be closed as invalid.

fatal: bad object 8c395a888c2d77bdc91e956ef24a07c0c87cdd24

status changed; resolution set

James E. King, III — Sat, 12 Aug 2017 20:16:09 GMT

status new → closed
resolution → invalid

status changed; resolution deleted

michael.moldaschl@… — Fri, 18 Aug 2017 08:56:26 GMT

status closed → reopened
resolution invalid

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'

James E. King, III — Sun, 27 Aug 2017 18:15:44 GMT

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!

owner, status changed

James E. King, III — Sun, 27 Aug 2017 18:16:20 GMT

owner changed from Andy Tompkins to James E. King, III
status reopened → new

status changed; resolution set

James E. King, III — Wed, 30 Aug 2017 01:48:10 GMT

status new → closed
resolution → fixed

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.