The easiest, in my opinion, is to do a local build, do osc cheroot and try to rpm -e the offending package... Should give a hint what pulled it in.
If setting up the build root fails, add the one you want to keep as BuildIgnore to your spec... Which results and the offending one being able to be installed... And you can see in the cheroot what pulled it in.
Best regards,
Dominique
Sent from my iPad
On 22 nov. 2012, at 18:50, Ralf Lang
horde5-content has conflicts for SLES11 because it prefers php53 but something forced "php5" to be installed. How can I find out which package(s) in the dependency tree forced this?
-- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de
B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org