-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression tests fail if lazperf is not enabled #251
Comments
I think a Debian package would be useful. Why not adding lazperf debian package as well ? |
Yes, it would be awesome 👍 |
Hi @df7cb, Regression tests for laz compression should not be executed if lazperf is not enabled: https://github.com/pgpointcloud/pointcloud/blob/master/pgsql/Makefile.in#L35:L37 I just tested on my Archlinux and I didn't succeed in reproducing the issue. Can you give me the Debian version that you're currently using please? This way I'll try to reproduce the issue within a Docker container. Thanks! |
@strk, you suggested it on #postgis on Nov 28th. 😃 For packaging lazperf, I don't even know what it is, and I'm not keen to maintain even more things. A "simple" PG extension package like pointcloud would be no problem, but more libraries... you'd need to find someone else to do that. @pblottiere: That's on Debian unstable. But retrying the build, the regression file is excluded, so ignore this please. Still, would a Debian package without lazperf be useful to anyone? I understood that pointcloud is used somewhere in the PostGIS/OSGeo infrastructure. |
Hi @df7cb,
AFAIAC, working on an official Debian package is a long standing idea, but I never dare to strike out. I could definitely try for lazperf, but would you be available in case I need some support? |
Sure, I can help with the packaging and even sponsor the actual uploads. |
Awesome, thanks @df7cb 👍. I will come back to you shortly about this topic.
OK, I'm closing this issue then. |
lazperf is not in Debian, so we can't use it.
Is a Debian package even useful if that wouldn't be included? @strk?
The text was updated successfully, but these errors were encountered: