zlib-dev change breaks pyenv installs

[QuiteClose]

Recently, this commit changed the zlib-dev dependencies: 26f8c4f Since then, pyenv installs have been failing with a non-zero exit code. Build logs show that zlib was not included in the python build because it was not found.

Workaround: Explicitly installing the zlib-static package provides the libz.a file that python's distutils expects. Because pyenv then detects zlib python builds can succeed.

I posted here for informational purposes, as I was using an image that only installed zlib-dev - the pyenv build stage was failing. The docker build output doesn't make this especially obvious and no doubt pyenv should be more flexible in their zlib detection. (They rely on the deprecated distutils package to detect libraries and that expects the .a suffix.)

I'm happy with the workaround to explicitly installing zlib-static. Noting the change in behaviour here, as I suspect this post would have saved me some time.

Maybe ignore? Forcing people to explicitly install zlib could be desired behaviour. Please close if this is not an issue.

[QuiteClose]

@javacruft re: the diff here #77286

My package manager had selected zlib-dev 1.3.1.2-r0 to install, but that is one of the excluded packages.

I suspect therefore that some cache in my build pipeline allowed me to install this dev package when the zlib package for that had been marked as unavailable.

Closed.