id,summary,reporter,owner,description,type,status,priority,component,version,resolution,keywords,cc 88,"Installation problem with fresh Python 2.7 RPM from ""Computational""",andreas.motl@…,thomas,"Hey there, first things first: Thanks for your work! We recently required Python 2.7 on RHEL6/CentOS6 and - voilà - found out you provide it in your ""Computational"" repositories. However, we discovered there had been new releases of `python27-2.7.3-6.2.sdl6.{1,2}` on March, 11. A few days ago everything went fine installing `python27-2.7.3-6.2.puias6` from your repositories after attaching to `http://springdale.math.ias.edu/data/puias/$releasever/$basearch/os/Computational`. The distribution i'm verifying this on, is: {{{ $ cat /etc/redhat-release CentOS release 6.3 (Final) }}} With the fresh Python packages we receive: {{{ Error: Package: python27-libs-2.7.3-6.2.sdl6.2.x86_64 (puias-computational) Requires: libz.so.1(ZLIB_1.2.0)(64bit) }}} It appears zlib 1.2.3 is installed: {{{ $ yum info zlib.x86_64 | grep Version Version : 1.2.3 }}} We also checked ""Red Hat Enterprise Linux Server release 6.3 (Santiago)"": Same zlib version (1.2.3). Do you know why Computational's new Python 2.7 package is linked against zlib 1.2.0? FYI: It's not a showstopper at all, we can either install `python27-2.7.3-6.2.puias6` manually or explicitly attach to `http://springdale.math.ias.edu/data/puias/computational/6.3/x86_64/` instead. Just wanted to get in touch and inform you about the problem in case this would break something more serious (indeed it prevents package upgrades when using baseline $releasever=6, this would receive the fresh Python packages linked against zlib 1.2.0 and croak). To be more specific, the new Python packages appear in: - http://puias.princeton.edu/data/puias/6/x86_64/os/Computational/ - http://puias.princeton.edu/data/puias/6.4/x86_64/os/Computational/ However, even RHEL6/CentOS6 release 6.4 would have zlib 1.2.3 installed, imho. Cheers, Andreas.",bug,new,major,Server,,,python27 zlib,