Hello, I'm the upstream author of cowsql [0], and a maintainer of Incus [1] as well. Please consider switching the upstream of the gentoo raft [2] package from github.com/canonical/raft to github.com/cowsql/raft. I'm the original author of the github.com/canonical/raft project and I have now forked it to github.com/cowsql/raft, for many of the same reasons which prompted LXD developers to fork it to Incus. The cowsql/raft code is compatible with canonical/dqlite and with canonical/raft, but it's not guaranteed that the other way round will hold true. Please see also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053663 for more background. Thanks, Free [0] https://packages.gentoo.org/packages/dev-libs/cowsql [1] https://packages.gentoo.org/packages/app-containers/incus [2] https://packages.gentoo.org/packages/dev-libs/raft
I think it makes sense, seeing incus will become the main focus and I believe we'll drop lxd once incus's first LTS becomes available. But, and as noted by you, the soname change is a bit... well messy but I think we'll manage.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52cc74d381d9f73203673290b1d36c73a11ed666 commit 52cc74d381d9f73203673290b1d36c73a11ed666 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2023-10-18 16:37:18 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2023-10-18 16:39:26 +0000 dev-libs/raft: add 0.18.1 - switch upstream away from Canonical. This is a 100 % compatible change for now at least, but our main focus will be incus in the long run so it makes sense to follow the community-maintained libraries as well. See bgo#915960 for details. Closes: https://bugs.gentoo.org/915960 Signed-off-by: Joonas Niilola <juippis@gentoo.org> dev-libs/raft/Manifest | 1 + dev-libs/raft/metadata.xml | 2 +- dev-libs/raft/raft-0.18.1.ebuild | 55 ++++++++++++++++++++++++++++++++++++++++ 3 files changed, 57 insertions(+), 1 deletion(-)
Thanks! The soname change is a one-off to cleanup some previous mess. It will be stable from now on, since I have control on it. If there's any issue, I'm happy to help work it out.
(In reply to Free Ekanayaka from comment #3) > > The soname change is a one-off to cleanup some previous mess. It will be > stable from now on, since I have control on it. Yep, read through https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042989#55 which explained it and the future clearly. It's totally fine for us if you introduce .so.1 later too when things have calmed down a bit. Especially since not many packages depend on raft yet. > > If there's any issue, I'm happy to help work it out. Awesome :) I'll of course file bugs normally to upstream etc. Be seeing you!
