Spec URL: http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5.spec SRPM URL: http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5-0.5.3-1.fc10.src.rpm Description: SQLAlchemy is an Object Relational Mappper (ORM) that provides a flexible, high-level interface to SQL databases. Database and domain concepts are decoupled, allowing both sides maximum flexibility and power. SQLAlchemy provides a powerful mapping layer that can work as automatically or as manually as you choose, determining relationships based on foreign keys or letting you define the join conditions explicitly, to bridge the gap between database and domain.
This package is for the 0.5 release of SQLAlchemy, packaged to work alongside of python-sqlalchemy (0.4) on Fedora 11 and below.
aah! I got confused here http://koji.fedoraproject.org/koji/packageinfo?packageID=3643 What is need of this package in F11 and below? I see python-sqlalchemy-0.5.4-1.p2.fc11 as latest package in F-11 I think this package will not be needed then.
Correct. This package is needed for EPEL4/5. It could be used on F-10 as well although I don't know if lmacken plans on branching it there. Fedora Community needs to have sqlalchemy-0.5.x in order to run so getting it running on an EL-5 box depends on having this package.
Review: + package builds in mock (rawhide i586). koji Build =>http://koji.fedoraproject.org/koji/taskinfo?taskID=1432964 + source files match upstream url 0a4f50b690ae946c3188614eeea6f1e5f02681d9 SQLAlchemy-0.5.3.tar.gz + package meets naming and packaging guidelines. + specfile is properly named, is cleanly written + Spec file is written in American English. + Spec file is legible. + dist tag is present. + build root is correct. + license is open source-compatible. + License text is included in package. + %doc is present. + BuildRequires are proper. + %clean is present. + package installed properly. + Macro use appears rather consistent. + Package contains code, not content. + no headers or static libraries. + no .pc file present. + no -devel subpackage + no .la files. + no translations are available + Does owns the directories it creates. + no scriptlets present. + no duplicates in %files. + file permissions are appropriate. + Not a GUI application I don't get why all .py* files installed under /usr/lib/python2.6/site-packages/SQLAlchemy-0.5.3-py2.6.egg ? Why rpmlint is complaining script-without-shebang error with this package whereas I don't see such rpmlint messages in rawhide package? why following is added to SPEC ? BuildRequires: python-sqlite2
ping?
I will close this review within this week as submitter is non-responsive.
The .py files are installed under /usr/lib/python2.6/site-packages/SQLAlchemy-0.5.3-py2.6.egg because it needs to work alongside python-sqlalchemy. See our egg guidelines for more details: http://fedoraproject.org/wiki/Packaging/Python/Eggs The BuildRequires: python-sqlite2 is for the test suite. http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5-0.5.3-2.fc10.src.rpm http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5.spec * Fri Jul 10 2009 Luke Macken <lmacken> - 0.5.3-2 - Remove the executable bit from *.py
Umm, you're supposed to give him a month to reply, then ping, then close after a week. You didn't even give Luke a full week before your first ping, and now I see you've dropped the other tickets in the dependency chain back into the review queue. Is there some problem?
I think Luke is very busy with his security work. I almost ping him daily on #fedora-devel and #fedora-python. But very few times I got reply like he will be going to work. So I thought instead of pinging him again and again I better move on and pick some other reviews. And if I am dropping first package in chain then it will be good to drop others also. As first package itself will take some more time to appear in rawhide repository. I hope there is no policy that prevents reviewer from leaving review at any point. If there is any please point me.
Of course you're welcome to drop reviews at any time if you feel like you can't stick with it and wait a while for a busy person to respond. That just means that I or one of the other few reviewers will have to take care of them.
and hey! I have not closed this review. Just moved back to New queue. Don't worry I will pick some more reviews to look queue count lower for you. I know you are very much worried about New Package Count. And if you are really, I will say first we should try to do something for Merge-reviews. I also see we have not very good but good amount of reviewers nowadays. I also know you got busy with fedora-cvs work that is not giving you much time on reviews.
This looks good. All of Parag AN's comments have been addressed. I see a problem that comes from the guidelines, though: %{python_sitelib}/easy_install.pth will conflict when there's more than one compat package installed on the system. With F11's version of setuptools, there doesn't seem to be a reason to touch easy_install.pth in the first place. If you're going to build this package for EL-5/EL-4 could you test build it there with the touch %{buildroot}%{python_sitelib}/easy_install.pth removed and see if we can just remove that?
I did a little bit of testing after removing the easy-install.pth file, and this package still seems to work (after running pkg_resources.require("SQLAlchemy>0.5"), of course). http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5-0.5.3-2.fc10.src.rpm http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5.spec * Wed Aug 12 2009 Luke Macken <lmacken> - 0.5.3-3 - Remove conflicting easy-install.pth file from our site-packages
I think you mean this SRPM: http://lmacken.fedorapeople.org/rpms/python-sqlalchemy0.5-0.5.3-3.fc11.src.rpm Checking it now.
easy_install.pth no longer conflicts. Package builds in koji. Two problems that you can fix when you import the package: There's a new version sqlalchemy-0.5.5 that you might want to update to before pushing this to EPEL for the first time. 0.5.5 contains a rarely used API breaking change so getting it into the first release will make sure that no one is depending on the old behaviour if you need to update later. The egg info files are executable. I believe this is a bug in python-setuptools that I submitted a patch for and was fixed for Fedora but it's still plaguing the RHEL5 version of setuptools. You can probably change your chmod line like this: - find $RPM_BUILD_ROOT%{python_sitelib} -name '*.py' | xargs chmod -x + chmod -R a-X $RPM_BUILD_ROOT%{python_sitelib} Since there shouldn't be any scripts under %{python_sitelib}. Provided you make those two changes when you import, this package is APPROVED.
New Package CVS Request ======================= Package Name: python-sqlalchemy0.5 Short Description: Modular and flexible ORM library for python Owners: lmacken, toshio Branches: F-10 EL-5
CVS done.
Hmm, with that chmod usage I'm getting error. I'm not sure if it's something messed up with my environment. The original version still works for me. + chmod -R a-X /home/lmacken/rpmbuild/BUILDROOT/python-sqlalchemy0.5-0.5.3-4.fc11.x86_64/usr/lib/python2.6/site-packages chmod: cannot access `/home/lmacken/rpmbuild/BUILDROOT/python-sqlalchemy0.5-0.5.3-4.fc11.x86_64/usr/lib/python2.6/site-packages/SQLAlchemy-0.5.3-py2.6.egg': Permission denied
Also, the nosetest changes don't work with this package. The old %check still works.
(In reply to comment #18) > Hmm, with that chmod usage I'm getting error. I'm not sure if it's something > messed up with my environment. The original version still works for me. > I'm a dummy and reversed what "X" does in chmod but we resolved this on IRC using find -type f The nosetest changes worked when updated to sqlalchemy-0.5.5.
python-sqlalchemy0.5-0.5.5-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/python-sqlalchemy0.5-0.5.5-1.el5
python-sqlalchemy0.5-0.5.5-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/python-sqlalchemy0.5-0.5.5-1.fc10
python-sqlalchemy0.5-0.5.5-1.fc10 has been pushed to the Fedora 10 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-sqlalchemy0.5'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-8675
python-sqlalchemy0.5-0.5.5-1.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-sqlalchemy0.5'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2009-0282
python-sqlalchemy0.5-0.5.5-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
python-sqlalchemy0.5-0.5.5-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.