[LIH] Resolving openssl RPM conflicts.

Hi,

I have built a RPM package of recent version of openssl-0.9.8k  
targeted for x86_64 platform.
The system has both i686 and x86_64 version of openssl-0.9.8b. When I  
update the system with the newly built rpm the "docs" fileset  
conflicts with the older version of openssl (i686).

# rpm  -qa openssl
openssl-0.9.8b-10.el5
openssl-0.9.8b-10.el5

# rpm -Uvh openssl-0.9.8k-5.el5.x86_64.rpm
Preparing...                 
########################################### [100%]
	file /usr/share/man/man1/asn1parse.1ssl.gz from install of  
openssl-0.9.8k-5.el5 conflicts with file from package  
openssl-0.9.8b-10.el5
	file /usr/share/man/man1/ca.1ssl.gz from install of  
openssl-0.9.8k-5.el5 conflicts with file from package  
openssl-0.9.8b-10.el5
	file /usr/share/man/man1/ciphers.1ssl.gz from install of  
openssl-0.9.8k-5.el5 conflicts with file from package  
openssl-0.9.8b-10.el5
	file /usr/share/man/man1/crl.1ssl.gz from install of  
openssl-0.9.8k-5.el5 conflicts with file from package  
openssl-0.9.8b-10.el5
         .................
         .................

I have gone through some documents which says each man page file's md5  
should match with the previous one and I guess it is difficult to do  
that.
I understand I can force install or use "--nodocs" option to overcome  
this. But, is there an elegant way of modifying the new rpm (spec  
file) to fix this issue all together (and also install the new docs).

regards
-logu



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july