Closed legoktm closed 3 years ago
This is probably due to the remove of zlib support (https://github.com/openzim/libzim/commit/8db2816fcf3341e8fe1c6811d6c77e8d52c69759)
While it doesn't change the libzim ABI, it now raise an exception if we try to create a zim file with zip compression. The bug is in the wrapper code that doesn't catch this exception correctly.
Thanks for the explanation. I rebuilt the Debian package for now, so it's no longer an issue for me. I'll leave it up to you whether to close this or leave it open for "..the wrapper code that doesn't catch this exception correctly."
With the work of adaptation on libzim_next I will rework this. I will close the issue then.
@mgautierfr Is this fixed with #82?
@rgaudin @legoktm @mgautierfr I propose to close this ticket as the new python-libzim 1.0.0 to be published will work only and is tested against libzim7+. Does that sounds good to you?
This isn't an issue for me from the Debian side, it was fixed when I rebuilt the package.
Yes, we can close it. We will change a lot of things soon and this issue will be somehow obsolete. As it is not a issue for @legoktm, let's close it.
In Debian, python-libzim was initially built against libzim 6.2.2. Yesterday I updated libzim to 6.3.0, with no rebuild for python-libzim, and now the python-libzim test suite segfaults:
https://gist.github.com/legoktm/ef86b76242e853d53826d4e885391c03 is the beginning of the backtrace. I can provide full reproduction steps for a docker container if that's needed.
If I rebuild python-libzim against libzim 6.3.0, then it's all fine. But I expect that because there was no ABI bump in libzim, that updating it shouldn't cause any problems for python-libzim. Is that assumption wrong?