@legoktm, in order to avoid mistakes like #172, we've decided we should automatically build deb packages in the CI, as we do for libzim and other projects.
I've looked at the recipe in https://salsa.debian.org/debian/python-libzim but I think it'd best if you could do it. I don't know how you want to sync that with your downstream repo and all.
As you've probably noticed, we released 3.2.0 so the patch is not needed anymore. As per target versions, I think only unstable and testing can be targeted as latest release targets libzim >= 8.2.1.
I see no reason not to push to our PPAs as well.
@legoktm, in order to avoid mistakes like #172, we've decided we should automatically build deb packages in the CI, as we do for libzim and other projects.
I've looked at the recipe in https://salsa.debian.org/debian/python-libzim but I think it'd best if you could do it. I don't know how you want to sync that with your downstream repo and all.
As you've probably noticed, we released 3.2.0 so the patch is not needed anymore. As per target versions, I think only unstable and testing can be targeted as latest release targets
libzim >= 8.2.1.I see no reason not to push to our PPAs as well.