Folks, I'm using rpm-4.0.4-7x-18 on RedHat 7.3. I've found a small issue with the use of rpm that I would like to run past you guys. I believe I under- stand the reason rpm acts the way it does -- I'd just like more knowledgeable folks to confirm my suspicion. I have a configuration file that is being install by an example rpm named myapp-1.01.i386.rpm. The same configuration was then slightly changed by a second rpm named myapp-patch-1.01p1.i386.rpm. At this point myapp-1.01 and myapp-patch-1.01p1 are installed. Finally, the same configuration file was changed back to the exact same content found in rpm myapp-1.01 by an upgrade using myapp-patch-1.01p2.i386.rpm, so only myapp-1.01 and myapp-patch-1.01p2 are installed in the final scenario. What I found was the configuation file in myapp-patch-1.01p2 would not install. My guess is that the reason it would not install was the version of the configuration file in myapp-1.01 matched the version in myapp-patch-1.01p2 *EVEN THOUGH* the most recently installed version of the file. The configuration file would install if I changed it ever so slightly, creating a third instance of the file. Is this a known feature? Perhaps it is a bug? If it is a known feature could anyone point out a source of documentation for this so I can read up on it? Thank you, Joel Breazeale _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
