Spec URL: same spec as the current oro SRPM URL: same SRPM as the current oro Description: same as before This package was renamed upstream to include the 'jakarta-' prefix at the request of the Jakarta folks. It is part of that project like the other jakarta-* ones that we have. Proper "Obsoletes:" and "Provides:" will be added. Provides: oro = %{epoch}:%{version}-%{release} Obsoletes: oro <= 0:2.0.8 and Provides: oro-javadoc = %{epoch}:%{version}-%{release} Obsoletes: oro-javadoc <= 0:2.0.8 So the javadoc part also gets replaced.
Since epoch is 0, you don't need to list that as part of our Provides. (or in the spec at all) Do you really need to define name, version, and release, just to fill them in at Name: Version: and Release:? Please don't do that. Othewise looks ok, for a java package (: Please create an srpm with the new name and import it as jakarta-oro. We'll stop using the 'oro' module. This would be a good time to change the release string to remove the _. Added to dist-fc6. Please close when built into rawhide.
Yes, the duplicate definition for name, version and release had already been removed from the package in the latest upstream release, which incorporated GCJ AOT bits (otherwise the same), so I merged that in. All new packages are being rebuilt without the '_NNfc' -- this one will be a .1 (as the first of our builds from this upstream release). The only thing that was not yet done was the removal of Epoch as we are trying to get it removed from all upstream packages so that the next round only have the Epoch > 1 ones specified.