Hi Maarten,
On 2025-12-03 10:42, Maarten L. Hekkelman wrote:
Op 02-12-2025 om 16:28 schreef Andrius Merkys:
I will have to come up with a new name I'm afraid. I guess this bug
should be closed now.
This happens, alas. I would suggest leaving the bug open and renaming
it once you come up with a different name. The bug already contains
some valuable details which I think are worth preserving.
The new name is libzeem. You can find a new repository at
https://salsa.debian.org/med-team/libzeem
Thanks, I will give it a look.
One manual test that might be nice to run since you are the upstream,
is to make sure that system-installed CMake configuration files are
usable by any relying reverse dependency. Sometimes paths happen to be
off, multiarch triplet incorrect and the like.
I'm not sure what you mean with this. Do you have examples for how this
is done in other packages?
If you have a package depending on libzeem, try building it with
system-installed libzeem. This does not have to be a part of the
testuite nor autopkgtest - it is enough to check once whether CMake's
FindPackage(zeem) correctly locates the system-installed libzeem. For me
this is a usual source of problems, thus I prefer doing this check once
to save time for subsequent fixing.
Best wishes,
Andrius
