Well, you really need to create a new zlib.spec file (or whatever it's called) and give it a different version/build number than what you got from your distribution. To get the base spec file, install the zlib SRPM from your distribution, and modify it. Then, do an "rpm -bb zlib.spec" and when that completes successfully, do an "rpm -ivh zlib-ab.cyd.s390.rpm" to actually install it. Do that from the beginning, and you don't have to repeat it to let RPM know about it.
Mark Post -----Original Message----- From: Kern, Thomas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 2:53 PM To: [EMAIL PROTECTED] Subject: Re: Zlib security alert I have downloaded the tar.gz file and gone through the make clean;./configure -s;make install process. Now how do I update the RPM database to reflect the new version of zlib? I haven't noticed any function of RPM to just update its database with my arbitrary data. /Thomas Kern /(301)903-2211 -----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 03:12 To: [EMAIL PROTECTED] Subject: Re: Zlib security alert What is there to think? It's a problem, a fix has been developed, every one needs to put it on. My Linux distribution, Slackware, has already posted their fix on their FTP server, and notified their security mailing list. I guess I'll be putting it on tomorrow after I get up.
