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 -kanarip
"JvM" == Jeroen van Meeuwen kanarip@kanarip.com writes:
JvM> More details are in the review request[1], and I would appreciate JvM> your opinion on this Obsoletes header becoming a blocker.
I personally think that such things should indeed not be part of the Fedora repository. FPC actually discussed something similar to this; the results of that are Use of Epochs section: http://fedoraproject.org/wiki/Packaging:Guidelines#Use_of_Epochs
Basically, you can carry over an epoch from a non-Fedora repository if it was "publicly accessible". I see package renames as essentially the same situation, although they certainly aren't as permanent as epochs so I can see room for considering them differently, and I'm sure we'd consider a proposal if someone wrote it up and submitted it.
Finally, I really don't understand why there's a significant issue over this anyway. What would you have to do if any other package in your private repository entered the distribution under a different name? You wouldn't petition the maintainer to add an Obsoletes/Provides pair for you, you'd generate one yourself in your private repository and then transition to the Fedora package.
- J<
packaging@lists.fedoraproject.org