jewel -> master upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
--
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



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux