https://bugzilla.redhat.com/show_bug.cgi?id=806040 --- Comment #8 from Volker Fröhlich <volker27@xxxxxx> --- Great! The disttag should be the last part of release: 2.r298%{?dist} To make it a tiny bit more comfortable for you, you could define a macro and use that: %global svn r298 2.%{svn}%{?dist} Source: ...%{svn}... Don't use the macro in the changelog though, but explictly write down the proper release there. That is 1.9.0-2.r298 in this case. If you are interested, you can still build Pyproj 1.8.9 on Fedora 16 and 17. You can use this approach to avoid providing the private libs: %{?filter_setup: %filter_provides_in %{python_sitearch}.*\.so$ %filter_setup } Taken from http://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering The SRPMs are the same, no matter if they have a fc16 or fc18 disttag. In case you don't know how to build the Python 3 module yet, it is described on http://fedoraproject.org/wiki/Packaging:Python. If you're looking for inspiration, you can also take a look at: http://pkgs.fedoraproject.org/gitweb/?p=pyshp.git;a=blob_plain;f=pyshp.spec;hb=9e99ead3811736584eadf547c1496c5e3ec9a0b4 -- 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