Spec URL: https://williamjmorenor.fedorapeople.org/rpmdev/python-honcho.spec SRPM URL: https://williamjmorenor.fedorapeople.org/rpmdev/python-honcho-0.5.0-1.fc20.src.rpm Description: Honcho is a Python port of Foreman,for managing Procfile-based applications Fedora Account System Username: williamjmorenor
Requires: python-markupsaf is incomplete, it has to be "python-markupsafe", otherwise the runtime dependencies couldn't be solved. I've tested whether it builds with Python v3, and it does [1]. Keep in mind, the next Fedora version will probably ship Python 3 as default, that's why it is mandatory to also build a Python 3 version, unless there are strange objections. Please build and test the Python 3 version, if it works as expected, you could also omit the Python 2 version. [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=8594105
Spec URL: https://williamjmorenor.fedorapeople.org/rpmdev/python-honcho.spec SRPM URL: https://williamjmorenor.fedorapeople.org/rpmdev/python-honcho-0.5.0-2.fc21.src.rpm %changelog - Add Python3 subpackage Really don't like me to have to build both for Python2 and Python3, but I think than make Python3 for default is a great step in the adoption of Python3.
%files %doc README.rst %{_bindir}/honcho %{python2_sitelib}/%{pypi_name} %{python2_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info %if 0%{?with_python3} %files -n python3-%{pypi_name} %doc README.rst %{_bindir}/honcho %{python3_sitelib}/%{pypi_name} %{python3_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info %endif # with_python3 The file %{_bindir}/honcho is included in both packages, but py2 and py3 versions of the same module have to be completely independent from each other. Imagine, someone needs both versions for resolve some dependencies, but this would end up in a unresolvable file conflict. Have a look at the appropriate guidelines: http://fedoraproject.org/wiki/Packaging:Python#Executables_in_.2Fusr.2Fbin Here's the scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=8812185 The file %{_bindir}/honcho looks the same in both py2 and py3 package: #!/usr/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'honcho==0.5.0','console_scripts','honcho' __requires__ = 'honcho==0.5.0' import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.exit( load_entry_point('honcho==0.5.0', 'console_scripts', 'honcho')() ) Even the py2 package has the shebang "#!/usr/bin/python3". As I already wrote, I don't know where you need this for, but if the py3 version works for you, then just drop the py2 package. Otherwise, rename the "binaries" according to the guidelines.
Spec URL: https://williamjmorenor.fedorapeople.org/rpmdev/python-honcho.spec SRPM URL: https://williamjmorenor.fedorapeople.org/rpmdev/python-honcho-0.5.0-3.fc21.src.rpm %changelog - Build only with Python3 I will keep only de Python3 build and target only to F21 and F22
Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=8851724 $ rpmlint -i -v * python-honcho.noarch: I: checking python-honcho.noarch: I: checking-url https://github.com/nickstenning/honcho (timeout 10 seconds) python-honcho.noarch: W: no-manual-page-for-binary honcho Each executable in standard binary directories should have a man page. python-honcho.src: I: checking python-honcho.src: I: checking-url https://github.com/nickstenning/honcho (timeout 10 seconds) python-honcho.src: I: checking-url https://pypi.python.org/packages/source/h/honcho/honcho-0.5.0.tar.gz (timeout 10 seconds) python-honcho.spec: I: checking python-honcho.spec: I: checking-url https://pypi.python.org/packages/source/h/honcho/honcho-0.5.0.tar.gz (timeout 10 seconds) 2 packages and 1 specfiles checked; 0 errors, 1 warnings. OK so far. --------------------------------- key: [+] OK [.] OK, not applicable [X] needs work --------------------------------- [+] MUST: rpmlint must be run on the source rpm and all binary rpms the build produces. The output should be posted in the review. [+] MUST: The package must be named according to the Package Naming Guidelines. [+] MUST: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption. [+] MUST: The package must meet the Packaging Guidelines. [+] MUST: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines. [+] MUST: The License field in the package spec file must match the actual license. MIT [.] MUST: If (and only if) the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package must be included in %license. [+] MUST: The spec file must be written in American English. [+] MUST: The spec file for the package MUST be legible. [+] MUST: The sources used to build the package must match the upstream source, as provided in the spec URL. Reviewers should use sha256sum for this task as it is used by the sources file once imported into git. If no upstream URL can be specified for this package, please see the Source URL Guidelines for how to deal with this. $ sha256sum * 623fe325939219f61b41ab6124c57f4960ce4f486516846aaaf7d4775d2a2eda honcho-0.5.0.tar.gz 623fe325939219f61b41ab6124c57f4960ce4f486516846aaaf7d4775d2a2eda honcho-0.5.0.tar.gz.orig [+] MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. [.] MUST: If the package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. Each architecture listed in ExcludeArch MUST have a bug filed in bugzilla, describing the reason that the package does not compile/build/work on that architecture. The bug number MUST be placed in a comment, next to the corresponding ExcludeArch line. [+] MUST: All build dependencies must be listed in BuildRequires, except for any that are listed in the exceptions section of the Packaging Guidelines ; inclusion of those as BuildRequires is optional. Apply common sense. [.] MUST: The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden. [.] MUST: Every binary RPM package (or subpackage) which stores shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in %post and %postun. [.] MUST: Packages must NOT bundle copies of system libraries. [.] MUST: If the package is designed to be relocatable, the packager must state this fact in the request for review, along with the rationalization for relocation of that specific package. Without this, use of Prefix: /usr is considered a blocker. [+] MUST: A package must own all directories that it creates. If it does not create a directory that it uses, then it should require a package which does create that directory. [+] MUST: A Fedora package must not list a file more than once in the spec file's %files listings. (Notable exception: license texts in specific situations) [+] MUST: Permissions on files must be set properly. Executables should be set with executable permissions, for example. [+] MUST: Each package must consistently use macros. [+] MUST: The package must contain code, or permissable content. [.] MUST: Large documentation files must go in a -doc subpackage. (The definition of large is left up to the packager's best judgement, but is not restricted to size. Large can refer to either size or quantity). [+] MUST: If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present. [.] MUST: Static libraries must be in a -static package. [.] MUST: Development files must be in a -devel package. [.] MUST: In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name}%{?_isa} = %{version}-%{release} [.] MUST: Packages must NOT contain any .la libtool archives, these must be removed in the spec if they are built. [.] MUST: Packages containing GUI applications must include a %{name}.desktop file, and that file must be properly installed with desktop-file-install in the %install section. If you feel that your packaged GUI application does not need a .desktop file, you must put a comment in the spec file with your explanation. [+] MUST: Packages must not own files or directories already owned by other packages. The rule of thumb here is that the first package to be installed should own the files or directories that other packages may rely upon. This means, for example, that no package in Fedora should ever share ownership with any of the files or directories owned by the filesystem or man package. If you feel that you have a good reason to own a file or directory that another package owns, then please present that at package review time. [+] MUST: All filenames in rpm packages must be valid UTF-8. [.] SHOULD: If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it. [.] SHOULD: The description and summary sections in the package spec file should contain translations for supported Non-English languages, if available. [+] SHOULD: The reviewer should test that the package builds in mock. See Koji build above (which uses Mock anyway). [+] SHOULD: The package should compile and build into binary rpms on all supported architectures. [.] SHOULD: The reviewer should test that the package functions as described. A package should not segfault instead of running, for example. [.] SHOULD: If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity. [.] SHOULD: Usually, subpackages other than devel should require the base package using a fully versioned dependency. [.] SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and this is usually for development purposes, so should be placed in a -devel pkg. A reasonable exception is that the main pkg itself is a devel tool not installed in a user runtime, e.g. gcc or gdb. [.] SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the file instead of the file itself. [.] SHOULD: your package should contain man pages for binaries/scripts. If it doesn't, work with upstream to add them where they make sense. ---------------- PACKAGE APPROVED ----------------
====================== Thanks for the review! ======================
New Package SCM Request ======================= Package Name: python-honcho - Short Description: Python clone of Foreman Upstream URL: https://github.com/nickstenning/honcho Owners: williamjmorenor Branches: f21 master InitialCC: williamjmorenor
WARNING: Requested package name python-honcho - doesn't match bug summary python-honcho Please correct.
New Package SCM Request ======================= Package Name: python-honcho Short Description: Python clone of Foreman Upstream URL: https://github.com/nickstenning/honcho Owners: williamjmorenor Branches: f21 master InitialCC: williamjmorenor
Git done (by process-git-requests).
python-honcho-0.5.0-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-honcho-0.5.0-3.fc21
python-honcho-0.5.0-3.fc21 has been pushed to the Fedora 21 testing repository.
python-honcho-0.5.0-3.fc21 has been pushed to the Fedora 21 stable repository.