https://bugzilla.redhat.com/show_bug.cgi?id=1493738 --- Comment #7 from Clement Verna <cverna@xxxxxxxxxxxx> --- > I did not get to comment about this, but note that this package was retired > because it is dead upstream. We usually avoid packaging dead projects in > Fedora and when the ones we have die, we retire them. It may be a bad idea > to put this back in Fedora, and since you are working directly on the > package that requires python-xappy, it would be a great opportunity to > remove/replace this dependency. I do agree, it is not ideal unfortunately, this package provides the backbone of fedora-packages (search engine). I could not see any easy way to replace it. There are talks about a rewrite of packages, but I don't see this happening soon. So it will be useful to have this package until we manage to remove this dependency from fedora-packages. > Now, to the package: > > - All your package Requires and BRs should be versioned. For example, > > BuildRequires: python-setuptools > should be > BuildRequires: python2-setuptools > I thought I had changed that. I will update the spec file. > According to the commits in upstream SVN, they never really released version > 0.6.0. The 0.6.0 version variable was set in __setup__.py in SVN commit 565. > Check the author's note: > > "Bump version to 0.6.0 - release won't be for a little while yet, but this > allows me to test the version for backward compatibility" > > 0.6.0-0.1.svn624 was the first Fedora package, the release tag reads > 0.1.svn624. > > It reads 0.1 because the packager wanted to show that this was a > pre-release, meaning that the author had not had released this version of > the package yet, and it was being shipped anyway. When we ship a pre-release > like that, we must show which revision of the VCS we are shipping, that is > where the svn624 part enters: it is the number of the SVN commit being > packaged for Fedora. > > The package was updated a few times: > > 0.6.0-0.2.svn624 > [...] > 0.6.0-0.10.svn624 > 0.6.0-0.11 <===== Why is it missing now? > Thanks for the explanations, it makes much more sense now. I went through the version guideline one more time and it is clearer for me. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
