I at least would absolutely not mind if you prepared a new release :)
I normally work on a release in Q4, but last year the response to my
email(s?) was quieter than usual. Because doing a proper release takes
quite a bit of time*, I didn't pursue it further.
Since it's that time of year again, I'd be happy to work on a new stable
release, hopefully toward the
There have however been quite a few alphas released since then (ie
Pike 8.0.1760 and later):
8.0.1760 8.0.1772 8.0.1784 8.0.1796 8.0.1808 8.0.1820 8.0.1832 8.0.1844
8.0.1762 8.0.1774 8.0.1786 8.0.1798 8.0.1810 8.0.1822 8.0.1834 8.0.1846
8.0.1764 8.0.1776 8.0.1788 8.0.1800
This has actually been fixed by
http://pike-librarian.lysator.liu.se/index.xml?checkins=cea2e25e7cf493a94b736accc3a2e20d1eb861b7
in the 8.0 branch in git, but there has not been a new release since then.
Diagnosing this issue was made a bit harder by the fact that the
configure script unconditionally writes
Gz.. no (zlib is too old)
in pike_Gz.feature. Shouldn't the
PIKE_FEATURE(Gz,[no (zlib is too old)])
code only be executed if the result of the AC_TRY_LINK above
The Pike Gz module is missing on Debian 12 because the configure
script believes the system zlib is broken.
It runs src/modules/Gz/gz_test.c, which errors out with:
inflate should report DATA_ERROR
gz_test.c is an edited version of test/example.c from the zlib
distribution. Upstream commit
