On Thu, May 24, 2012 at 10:32 AM, Lamar Owen lowen@pari.edu wrote:
I think I've illustrated the process at this point. I have a tradeoff between not having crm114 at all and not having certain features that I may or may not use in a program that I use once in a blue moon (but blue moons happen, and I have used scalpel a few times in the past).... I'll probably end up doing a yum remove of scalpel, excluding the EPEL and the CERT Forensics versions of scalpel in the respective repo files in /etc/yum.repos.d, and then reinstalling scalpel, which should pull the RPMforge one, and make the crm114 install possible.
But odds are pretty good that you could grab the scalpel src rpm from epel and fix it to rebuild against the newer libtre in a matter of minutes. - just changing the spec, not the source... Stuff like that does happen, but it's rare (what, one conflict out of thousands of packages?) and it is usually a lot less trouble to work around than to avoid the repositories and routinely build source from tarballs yourself.