Bug 580964

- I'm not a naitive speaker, but I'd change 'tasklets' to 'task-lets' like proposed by rpmlint...

- Why do you remove the header file?
  Better include that, in case someone wants to use it...

- BR python2-devel would be better than just python-devel

Rest looks ok on the first sight.

I would rather not change 'tasklet' because it is an original term used in Stackless and greenlets documentation.

The header file is removed because it is needed only for the hypothetical C source code modules using greenlets (never seen them in the wild, but if you insist I can split it into a -devel package).

Also changed python-devel to python2-devel.

Should I also change python-setuptools to python2-setuptools? Haven't checked what's coming up with new python in Fedora 13.

Updated SPEC: http://abbot.fedorapeople.org/python-greenlet.spec
Updates SRPM: http://abbot.fedorapeople.org/python-greenlet-0.3.1-2.fc12.src.rpm

Hey Lev. I was working on my own packages for greenlet/eventlet, so I would be happy to review these for you. ;) 

Look for a full review later today.

OK - Package meets naming and packaging guidelines
OK - Spec file matches base package name. 
OK - Spec has consistant macro usage. 
OK - Meets Packaging Guidelines. 
OK - License (MIT)
OK - License field in spec matches
OK - License file included in package
OK - Spec in American English
OK - Spec is legible.
OK - Sources match upstream md5sum:
8d75d7f3f659e915e286e1b0fa0e1c4d  greenlet-0.3.1.tar.gz
8d75d7f3f659e915e286e1b0fa0e1c4d  greenlet-0.3.1.tar.gz.orig

OK - BuildRequires correct
OK - Package has %defattr and permissions on files is good. 
OK - Package has a correct %clean section. 
OK - Package has correct buildroot
      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
OK - Package is code or permissible content. 
OK - Packages %doc files don't affect runtime. 
OK - Package has rm -rf RPM_BUILD_ROOT at top of %install

OK - Headers/static libs in -devel subpackage. 
OK - -devel package Requires: %{name} = %{version}-%{release}

OK - Package compiles and builds on at least one arch. 
OK - Package has no duplicate files in %files. 
OK - Package doesn't own any directories other packages own. 
OK - Package owns all the directories it creates. 
OK - Package obey's FHS standard (except for 2 exceptions)
See below - No rpmlint output. 
OK - final provides and requires are sane.

SHOULD Items:

OK - Should build in mock. 
OK - Should build on all supported archs
OK - Should function as described. 
OK - Should have sane scriptlets. 
OK - Should have subpackages require base package with fully versioned depend. 
OK - Should have dist tag
OK - Should package latest version
OK - Should not use file requires outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin

Issues: 

1. rpmlint says: 

python-greenlet.src: W: spelling-error %description -l en_US tasklets -> task lets, task-lets, anklets
python-greenlet.src: W: spelling-error %description -l en_US Tasklets -> Task lets, Task-lets, Anklets
python-greenlet.x86_64: W: spelling-error %description -l en_US tasklets -> task lets, task-lets, anklets
python-greenlet.x86_64: W: spelling-error %description -l en_US Tasklets -> Task lets, Task-lets, Anklets
python-greenlet-devel.x86_64: W: no-documentation

All can be ignored. 

2. I'm not sure about having the devel subpackage. Sure there is a header file, but 
as you said nothing really uses it. I suppose it doesn't hurt, but seems like a waste. 

3. There are included tests, could be worth adding them to %check section?
(They run ok here with a 'python setup.py test')

I don't see any blockers here, so this package is APPROVED. 
Consider the test point before importing if you like. 

Also, if you would like co-maintainers, I would be happy to help co-maintain.

New Package CVS Request
=======================
Package Name: python-greenlet
Short Description: Lightweight in-process concurrent programming
Owners: abbot
Branches: F-11 F-12 F-13 EL-5
InitialCC:

(In reply to comment #4)
Thanks for the review. Yes, I would be glad to have a co-maintainer. Please write your FAS username so I would add you as a co-maintainer as soon as package is created.

As for the devel subpackage, I think it is not that much waste, so let's keep it. I will add tests to the final package version before importing.

CVS done (by process-cvs-requests.py).

python-greenlet-0.3.1-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.fc11

python-greenlet-0.3.1-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.fc12

python-greenlet-0.3.1-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.fc13

python-greenlet-0.3.1-2.el5 has been submitted as an update for Fedora EPEL 5.
http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.el5

(In reply to comment #6)
> As for the devel subpackage, I think it is not that much waste, so let's keep
> it. I will add tests to the final package version before importing.    

Kevin,

I can't find the way to add a co-maintainer to a package. Can you please give me a hint how to do this? Thanks.

Ah, from what I see (http://fedoraproject.org/wiki/Using_the_package_database#I.27m_the_package_maintainer.2C_how_do_I_give_someone_commit_access_to_my_package.3F), you need to apply for all branches you are interested in at https://admin.fedoraproject.org/pkgdb/acls/name/python-greenlet and I will approve the requests.

Yep. Requested. ;) 

Thanks.

Done.

That was really a BIG set of email notifications. :)
Dunno, may be I should open a bug/suggestion for pkgdb authors to send these notifications in digests, say after 10 minutes of no-acl-actions on the package.

Yeah, I am sure they would be open to ideas on it. It does generate a ton of emails. ;(

python-greenlet-0.3.1-2.el5 has been pushed to the Fedora EPEL 5 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update python-greenlet'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.el5

python-greenlet-0.3.1-2.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update python-greenlet'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.fc11

python-greenlet-0.3.1-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update python-greenlet'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.fc12

python-greenlet-0.3.1-2.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update python-greenlet'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/python-greenlet-0.3.1-2.fc13

python-greenlet-0.3.1-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

python-greenlet-0.3.1-2.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

python-greenlet-0.3.1-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

python-greenlet-0.3.1-2.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.