Please suggest,

I am on RHEL 6.8 and need zlib 1.2.5 or later version. currently have 1.2.3

when I try to install,

$ rpm -i zlib-1.2.5-8.1.x86_64.rpm
warning: zlib-1.2.5-8.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY
********file /lib64/libz.so.1 from install of zlib-1.2.5-8.1.x86_64 conflicts with file from package zlib-1.2.3-29.el6.x86_64

:/lib64 $ ll libz*

-rwxr-xr-x 1 root root libz.so.1.2.3
lrwxrwxrwx 1 root root*libz.so.1 -> libz.so.1.2.3
Rm libz.so.1 for the libz 1.2.5 install

now, when I try to remove the link, it seems breaking rpm and yum.

# ls -l libz*
lrwxrwxrwx 1 root root libz.so.1 -> libz.so.1.2.3
-rwxr-xr-x 1 root root libz.so.1.2.3

# unlink libz.so.1
# pwd
/lib64
lib64]# rpm -qa |grep -i libz
rpm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory


I desperately need new zlib version, any work around I can perform?

Right...because if you read the message you got, you didn't actually INSTALL it...it told you it conflicted and exited. Never installed the new zlib. You then removed the one you DID have installed manually, which broke things. An RPM file can be manually extracted...make a directory somewhere in your $HOME, copy the RPM file to it, and run
Then copy the ONE file back to the location where you removed it, and see if you can then run RPM commands. After that, do not use RPM to install packages...yum exists for a reason, because it takes care of dependencies for you. Without telling rpm to forcibly update/upgrade a package (see the man page on the rpm command), it won't. Yum asks, and takes care of housekeeping for you...removing files manually is bad.

And didn't you say before that you are not the system admin?
http://www.linuxquestions.org/questi...5/#post5696115

...and you were advised to call Red Hat support, since RHEL 6.8 is a commercial, pay for distro:
http://www.linuxquestions.org/questi...6/#post5660462
The best thing to avoid such problems is to pay for the commercial distros you use, let your admins do their jobs and use the right tools for the job.

You can always install a later version to a hidden location.
And export the location when you start the application requiring v1.2.5

zlib compiles in seconds.
$ configure --prefix=/opt/zlib && make

1 members found this post helpful.

yes, I am not sys admin and most probably shouldn't be matter for most people in community, never had any hidden or misleading purpose. Since we have new sys admin, we try to help any possible way. for us, its one person/sys. admin issue, its group/team issue and we will continue doing it.

Thanks all for commenting...

If you're not the systems admin, you are not helping the person who is. If it's not your job, and you don't have the knowledge to do it, you shouldn't. If you worked as an accountant at a garage, you wouldn't just go out and start trying to fix cars would you?? Would you appreciate it if one of the mechanics came in and started trying to do the accounts??

You 'helped' the person that was hired, by breaking a working server, giving them one more thing to fix. Again, if you have RHEL 6.8 you need to be paying for it, which would let you have used the correct "yum" command to do the installation. Your system, so you're free to do what you'd like, of course. But consider how things have turned out by doing so.

"yum upgrade zlib" should have been all you had to do. Reading the man page on RPM.."rpm -Uvh <file>" would have forced it in, and probably broken something else.

Trust me that is really bad example, if I am an accountant at garage and mechanic need some help, i would do it as I have some knowledge of car. I am on planet earth where people helps people. And guess what, we didn't break anything, we still have older version zlib - its just not compatible with 3rd party tool, so we just trying to get new version of zlib on board.

And "WE" will fix this,

Thanks again for your comment (of-course about zlib).

Good for you. Replace it with whatever you'd like, ok??? It was an example.

Yes you should help folks...if you know how to help them. Otherwise, you cause the people who DO know more trouble than you wind up helping. This is a good example.
You didn't break anything??? Then how come in your first post you said that after you messed with it, you couldn't then run yum or rpm commands??? You say you have the old version....how do you have it, after you said (again in your first post), that you deleted it, causing the yum/rpm commands to stop working???

According to you, you broke the system.

Actually you do too much guessing...good luck...!!!

Not guessing at all. YOU SAID:

• You weren't the system administrator: http://www.linuxquestions.org/questi...5/#post5696115
• You ran the wrong command to perform an update (post #1)
• You removed files (post #1)
• You then could not run rpm or yum commands (post #1) AFTER...
• ...you botched the installation of a package, because...
• ...you didn't use the right commands, syntax, or contact support

What, exactly, is guesswork?? Can you point to a single thing you've done to 'help' your systems admin??? You don't have the skills or knowledge to be doing things like this, obviously, and ignored the advice from months ago about contacting RHEL support, because they could have easily walked you through this on the phone CORRECTLY, which would actually have helped.

You didn't. Your system is broken. Mine aren't....tell your systems admin good luck instead.

what you doing here not helping anyone (you knows that). But its really funny, entertainment for sure...(like 5 year old kid fighting in school...omg you did this, you did that...but you didn't that...tell me what you did...haha)...keep doing...

at this point your OS is " FUBAR "
-- google it !!!

call redhat tech support

and reinstall the operating system and restore data from the good Back up . You did make one ?

yum and rpm need certain programs to be installed that have been built with specific options

if both are broken then the easiest and FASTEST fix is to reinstall from an original image and restore the data

now it might be fixable ???
this might be rather easy or nearly impossible

wl, regarding these two posts, please refer to the LQ Rules And please take note of the following specific ones:It is obviously more helpful for everyone to remain civil in these threads.