[Fedora-packaging] Obsoletes in renamed rubygem a blocker?

Jeroen van Meeuwen kanarip at kanarip.com
Fri Nov 20 09:21:13 UTC 2009

Hi there,

I've had rubygem-net-ldap packaged and deployed throughout my company, 
e.g. on all development workstations and on all dev/test/beta/prod servers.

My company is letting me package this ruby gem for Fedora as well, along 
with a bunch of other ruby gems. During the review[1], M. Tasaka 
suggested the name should have been rubygem-ruby-net-ldap instead, and 
so I added an Obsoletes header for rubygem-net-ldap.

This is now a blocker for M. Tasaka to approve the package, but if and 
when I remove it, and the new package is in Fedora I have to manually 
update all of approximately 40-50 development workstations and Fedora 
servers. I just need that Obsoletes header to be in the RPM, and that 
RPM with that header to be in the updates repository once.

More details are in the review request[1], and I would appreciate your 
opinion on this Obsoletes header becoming a blocker.

Kind regards,

Jeroen van Meeuwen

[1] https://bugzilla.redhat.com/show_bug.cgi?id=532309

More information about the Fedora-packaging mailing list