After checking SELinux configuration options, I have the feeling that SELinux may indeed
be the cause. Any ideas how to configure it to accept the new zlib, other than disabling
SELinux NTPD protection? :-)
Chris Dennis wrote:
> I believe this is the same problem:
>
> https://www.redhat.com/archives/fedora-list/2005-January/msg00174.html
>
> but in different libraries. I'm guessing that the "apt-get update" has
> gone slightly wrong, so it may be an issue for the SL guys to look at.