Spec URL: http://fedorapeople.org/~brouhaha/python-tinycss/python-tinycss.spec SRPM URL: http://fedorapeople.org/~brouhaha/python-tinycss/python-tinycss-0.3-1.fc19.src.rpm Description: tinycss is a complete yet simple CSS parser for Python. It supports the full syntax and error handling for CSS 2.1 as well as some CSS 3 modules. It is designed to be easy to extend for new CSS modules and syntax, and integrates well with cssselect for Selectors 3 support. Fedora Account System Username: brouhaha
Issues: 1. Please use https://github.com/SimonSapin/tinycss OR https://pypi.python.org/pypi/tinycss as URL; 2. And please use pypi download link as Source0: https://pypi.python.org/packages/source/t/tinycss/tinycss-0.3.tar.gz 3. python-tinycss.i686: E: non-standard-executable-perm /usr/lib/python2.7/site-packages/tinycss/speedups.so 0775L
What is the rationale for issues 1 and 2? Is there some Fedora policy regarding github vs. pypi that I've overlooked? For issue 1, the URL I provide seems to be much closer to a "home page" for the project than the github page, provides a superset of the information on the github page, and provides a link to the github page. It seems like a more useful URL for users of the package. In fact, that's the page that pypi says is the home page. For issue 2, the release tarballs on github seem to be upstream from pypi, so they seem like a better candidate to be considered authoritative. Although pypi does appear to offer older versions, they aren't listed, while on github they are. This means that the using the github release URL for the Source makes it easier for someone maintaining the spec to look at the version history and find older or newer versions. Also, the github release page gives a portion of the hash useful to identify the correct sources in git.
I think issue 3 is caused by some problem on the system you're building with. I've run rpmlint on the binary RPMs built by Koji for F19 and rawhide, and they don't give that warning. The speedups.so in the Koji builds are 0755. f19: http://koji.fedoraproject.org/koji/taskinfo?taskID=5637905 rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=5637921 $ ls *.rpm python-tinycss-0.3-1.fc19.i686.rpm python-tinycss-0.3-1.fc20.i686.rpm python-tinycss-0.3-1.fc19.x86_64.rpm python-tinycss-0.3-1.fc20.x86_64.rpm $ rpmlint *.rpm python-tinycss.i686: W: spelling-error %description -l en_US cssselect -> selectness, select python-tinycss.x86_64: W: spelling-error %description -l en_US cssselect -> selectness, select python-tinycss.i686: W: spelling-error %description -l en_US cssselect -> selectness, select python-tinycss.x86_64: W: spelling-error %description -l en_US cssselect -> selectness, select 4 packages and 0 specfiles checked; 0 errors, 4 warnings. $ rpm -qlvp *.rpm | grep speedups.so -rwxr-xr-x 1 root root 65060 Jul 22 01:28 /usr/lib/python2.7/site-packages/tinycss/speedups.so -rwxr-xr-x 1 root root 76840 Jul 22 01:28 /usr/lib64/python2.7/site-packages/tinycss/speedups.so -rwxr-xr-x 1 root root 65056 Jul 22 01:33 /usr/lib/python2.7/site-packages/tinycss/speedups.so -rwxr-xr-x 1 root root 80936 Jul 22 01:33 /usr/lib64/python2.7/site-packages/tinycss/speedups.so
(In reply to Eric Smith from comment #2) > What is the rationale for issues 1 and 2? Is there some Fedora policy > regarding github vs. pypi that I've overlooked? AFAIK, there is no such policy. Your URLs look fine. I'm tending to use urls looking more "official" or tending to be long stable, since your package might stay in fedora repos for a long time.
The other reason I prefer github for the Source is that if we ever wanted to use a git snapshot, the Source URL would have to change, but it's at least on the same site. However, you are right that the pypi URLs are likely stable even if the developer changes from github to another site. If you still want me to change the URL and Source to the ones you previously recommended, let me know, and I'll do it, but my preference is to keep them as they are.
Pypi is a bit like CPAN, yes, it's an index of python packages. IMO, pypi not only provides a stable home URL for search and download, but also provides a better link of source0. You needed to check out the rev, and download, and waste 3 lines in your spec just because github doesn't provide a download way like sourceforge... I hate checking out a package from VCS, maybe the upstream forgets to tag releases? Maybe it is just a snapshot place? Or maybe bahbahbah... This module is lucky because the author can tag it as normal. I've seen many packages hosted on gitorious or bitbucket, they don't have a version number, even a downloadable link is unavailable, too. Anyway, it's up to you. I would keep all my things simple, but if you think it's ok, then I'll support, not only 2 hands, but also 2 feet. ;) My machine is rawhide, there shouldn't have difference between yours.. weird... APPROVED.
(In reply to Eric Smith from comment #5) > The other reason I prefer github for the Source is that if we ever wanted to > use a git snapshot, the Source URL would have to change, but it's at least > on the same site. Source0 URL is just taken to create a file name for unpacking sources. I can't really recommend using git snapshots, because no human can remember the version.
It's not necessary to remember the hash used for the snapshot. It needs to be documented in the spec file, usually as a %global. It's also possible with github to construct a URL for a snapshot tarball. For example, from smartsim.spec: %global git_hash 3b11cf8 [...] Source0: https://github.com/ashleynewson/SmartSim/tarball/%{git_hash}/sma rtsim-%{git_hash}.tar.gz That said, using release tarballs rather than snapshots is preferred unless there is a really good reason to use a snapshot.
New Package SCM Request ======================= Package Name: python-tinycss Short Description: CSS parser for Python Owners: brouhaha Branches: f18 f19 el6 InitialCC:
Git done (by process-git-requests).
python-tinycss-0.3-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-tinycss-0.3-1.fc19
python-tinycss-0.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/python-tinycss-0.3-1.fc18
python-tinycss-0.3-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/python-tinycss-0.3-1.el6
python-tinycss-0.3-1.el6 has been pushed to the Fedora EPEL 6 testing repository.
python-tinycss-0.3-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-tinycss-0.3-2.fc19
python-tinycss-0.3-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/python-tinycss-0.3-2.fc18
python-tinycss-0.3-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
python-tinycss-0.3-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
python-tinycss-0.3-1.el6 has been pushed to the Fedora EPEL 6 stable repository.
Package Change Request ====================== Package Name: python-tinycss New Branches: epel7 Owners: brouhaha