Hi Free and Laszlo, On Sat, 2023-10-14 at 10:31 +0100, Free Ekanayaka wrote: > As a consequence, I've renamed the libraft2 binary package to > libraft0. Note that libraft0 already exists in bullseye, but there's > nothing depending on it, so even in the weird case where somebody > downloads libraft0 from sid and installs it in bullseye, nothing > should break.
Free, have you tested the upgrade path from a bullseye system with libraft0 installed incrementally through to sid? Even though it's probably a remote edge case, we should make sure the upgrade path works smoothly. (Both with just libraft0 installed directly, as well as indirectly by something like dqlite.) I've looked over the current packaging in salsa, and pushed a few commits cleaning up the packaging a bit. I have two remaining comments: First, it looks like you've intending to introduce a libraft-tools package, but it is currently empty -- do you mean to install something for that binary package? Also, its short description is a copy of libraft0's. Second, there's an existing patch in the packaging -- could that be included in the upstream code so we can eliminate the Debian-specific bit? Mathias
signature.asc
Description: This is a digitally signed message part
