https://bugzilla.redhat.com/show_bug.cgi?id=1181317 Bug ID: 1181317 Summary: Review Request: python-itools - The itools library Product: Fedora Version: rawhide Component: Package Review Severity: medium Assignee: nobody@xxxxxxxxxxxxxxxxx Reporter: reiner@xxxxxxxxxxx QA Contact: extras-qa@xxxxxxxxxxxxxxxxx CC: package-review@xxxxxxxxxxxxxxxxxxxxxxx Spec URL: https://raw.githubusercontent.com/rrottmann/rpmbuild/master/SPECS/python-itools.spec SRPM URL: https://github.com/rrottmann/rpmbuild/blob/master/SRPMS/python-itools-0.75.1-1.fc20.src.rpm Description: Please note, I am still a new rpm packager. My first rpm package is still in review under bz#734248. I Had a look at http://fedoraproject.org/wiki/SIGs/Python#Package_requests and saw the request to create a Fedora RPM package for itools: The itools library offers a collection of packages covering a wide range of capabilities. Including support for many file formats (XML, CSV, HTML, etc.), a virtual file system (itools.fs), the simple template language (STL), an index and search engine, and much more. While this is my first package for a python library, I took the challenge and created above SPEC/SRPM files. I checked it with rpmlint and got the following warnings: python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/xml/doctype.c A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/xml/arp.c A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/xml/pyparser.c A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/xml/parser.h A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/web/soup.c A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/xml/parser.c A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: hidden-file-or-dir /usr/lib64/python2.7/site-packages/itools/.mailmap The file or directory is hidden. You should see if this is normal, and delete it from the package if not. python-itools.x86_64: W: devel-file-in-non-devel-package /usr/lib64/python2.7/site-packages/itools/xml/arp.h A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. python-itools.x86_64: W: no-manual-page-for-binary iodf-greek.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary ipkg-update-locale.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary igettext-build.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary idb-inspect.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary ipkg-docs.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary igettext-merge.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary ipkg-build.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary ipkg-copyright.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary igettext-extract.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: no-manual-page-for-binary ipkg-quality.py Each executable in standard binary directories should have a man page. python-itools.x86_64: W: file-not-in-%lang /usr/lib64/python2.7/site-packages/itools/locale/en.mo python-itools.x86_64: W: file-not-in-%lang /usr/lib64/python2.7/site-packages/itools/locale/es.mo python-itools.x86_64: W: file-not-in-%lang /usr/lib64/python2.7/site-packages/itools/locale/fr.mo python-itools.x86_64: W: file-not-in-%lang /usr/lib64/python2.7/site-packages/itools/locale/it.mo python-itools.x86_64: W: file-not-in-%lang /usr/lib64/python2.7/site-packages/itools/locale/zh.mo 1 packages and 0 specfiles checked; 0 errors, 23 warnings. In order to fix these, I will need some guidance, how to deal with missing man pages and how to get rid of the source files in the non-devel package. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review