Hi Christian,
The package is called openstack-neutron and it provides openstack-quantum?
Yes, but in a fixed version. That is for both compatibility as well as in order to trigger the package rename on update. (a package is only updated if there is a provide (!) with a newer (!) EVR).
I think that's just wrong so I changed every openstack-quantum to openstack-neutron
Which is wrong on two levels. First for the reason above (breaking update) and second because %name = %version is an autoprovide, it must not be added manually.
and also added obsoletes for openstack-quantum to get rid of existing installed openstack-quantum packages.
Which is also in this particular case wrong. (obsolete without a provide).
expected behaviour of the openstack-neutron packages. Or do I have a wrong understanding of the Provides keyword?
Yes, apparently. http://en.opensuse.org/openSUSE:Package_dependencies#Renaming_a_package
Example: Why does the package openstack-neutron-dhcp-agent provides the package openstack-quantum-dhcp-agent?
a) for compatibility b) for fixing upgrade. c) in order to create the rename pattern together with the Obsolete line below. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org