Source: golang-github-tidwall-rtree Version: 0.0~git20180113.6cd4270-2 Severity: normal
There's a upstream release of github.com/tidwall/rtree ... While looking at the difference between the currently packaged version and the new upstream release it became apparent that the new rtree is not a derived work of the previously packaged version! Apparently the currently packaged version has been renamed and is now available as github.com/tidwall/rtred (note the last character changed!). It's also been archived and says to instead use the (new) github.com/tidwall/rtree. The only reverse dependency of golang-github-tidwall-rtree(-dev) is golang-github-tidwall-buntdb(-dev). The upstream buntdb was switched to use rtred (instead of rtree) in: https://github.com/tidwall/buntdb/commit/62d43edfcf1c243845f9b923c30d5d639b6176ee Since we're already in bullseye freeze, it seems too late to do anything to clear up the situation now. After the release we should look to see if buntdb has been ported to the new rtree, if so we can just replace the current rtree with the new rtree and add a Breaks against old buntdb. If not, we should likely upload a new source under the new name and update golang-github-tidwall-buntdb to new upstream release and update it's (build-)dependencies accordingly. Hopefully this bug report helps clear out the somewhat confusing situtation once we're ready to act on it. Regards, Andreas Henriksson
