On Tue, 28 Jun 2016, Nathan Cutler wrote: > I have been working on http://tracker.ceph.com/issues/14995 which has been > causing lots of failures in the upgrade suites, and now I think I know why. > > At the moment, the highest tag in jewel is v10.2.2, while in master the > highest tag is v10.2.0 - this can be verified by doing "git describe" in both > branches. > > Since the version numbers of all the packages are derived from "git describe", > we now have a situation where the package managers (rpm, dpkg, etc.) consider > master packages (i.e. packages built from the master branch) to be _older_ > than jewel packages. > > The solution, I guess, would be to add a v11.0.0 tag to master. That would explain it. We can just add a tag and not bother doing a release build for now... that is probably the simplest. Any objections? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
