openstack-swift-proxy-1.13.1-1.el6.noarch has a dependency on openstack-swift-plugin-swift3 swift3 isn't configured by default or used by many people (as it stands won't work very well) so for those who do want it, an upstream replacement is preferred the dependency makes this uglier than it should be # rpm -qR openstack-swift-proxy | grep swift3 openstack-swift-plugin-swift3
Derek (because your name is on the trunk packages): I don't see any references to swift3 in the openstack-swift-proxy package, but I don't know anything about swift. Is this a dependency we can safely remove?
Looks to me like it can be removed I don't see anything in the default install looking for it. Pete does removing it look ok to you.
I was always against saddling RPM dependencies with this. However, if you look at e.g. bug 882977, you see me making the same argument as Chris and losing. Alan thought that it was needed to pull these optional modules in for the complete functionality to be present. It comes down to the way installers operate, and what is expected to be present without manually doing "yum install foo". I think the real problem here is that swift3 that we ship is badly out of date. That is why Chris reached for upstream swift3 and that is why he wants to get rid of the one we ship. I waited and waited for Tomo to cut another release, but obviously this is not happening. We need to find the active upstream and return to git snapshots. Then there would be no need to drop the dependency.
Seeing how we aren't getting any releases even after the move to Sourceforge, I went back to snapshots and built one in F23 Rawhide: openstack-swift-plugin-swift3-1.7-5.20150601git69f94393.fc23 I'm going to spin these every half release for RDO now. Let's close this as WONTFIX, I'm sure Chris has moved on long ago.