https://bugzilla.redhat.com/show_bug.cgi?id=845115 --- Comment #6 from Bohuslav "Slavek" Kabrda <bkabrda@xxxxxxxxxx> --- (In reply to comment #5) > Phew, > > the version in our repositories is: 0.1-3, not 0.0.4 > Doing a version comparison, your package will not be taken as an update. > > What happened to the old package? It looks like you're taking totally > different sources. > old one for django-recaptcha: > https://code.google.com/p/recaptcha-django/source/browse/ > #svn%2Ftrunk%2Frecaptcha_django > > new ones: https://github.com/praekelt/django-recaptcha/tree/master/captcha > > I'd say, this is a totally different package, not a rename. > Yep, looks like that. Probably the best way to do is just retire the old package, pointing out that upstream is dead and introducing this one. What I think is appropriate here is using only Obsoletes (not Provides, as the API is different, I think). Also, introducing Epoch: 1 will solve the versioning problem. > Nevertheless, when you want to continue, you should take care of obsoleting > that old package, and of course deprecate that old package as fast as you > can. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review