On 11/22/2012 07:10 PM, Guido Berhoerster wrote:

* Ralf Lang [2012-11-22 18:52]:

...

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?

You can try "rpm -q --whatrequires php5" from within the build chroot.

Be aware that this one only returns packages which require php5 directly - but not its provides or files. Just compare the list returned from command above with dependency conflicts you get trying to remove the package (may not be case of this particular package, though) Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

...

You can try "rpm -q --whatrequires php5" from within the build chroot.

Yes, one can try this and that until one ends up in madness... ;-)

Only "rpm -e --test package" shows the full truth which other package(s) require package, see my English excerpt in http://lists.opensuse.org/opensuse-de/2011-11/msg00076.html

Yes, I was not far from there. I found some culprits but not all. My procedure is now like this: Find the dependency which enables the (failing) build when removed. Go to the dependency. Look with rpm -e for the dependency's conflicting dependency. It's tedious, but it works. Thank you for that link. -- 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