Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1025292 - Review Request: python-twiggy - A Pythonic logger
Summary: Review Request: python-twiggy - A Pythonic logger
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mario Blättermann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1025369
TreeView+ depends on / blocked
 
Reported: 2013-10-31 12:03 UTC by Ralph Bean
Modified: 2014-10-13 21:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-23 02:44:25 UTC
Type: ---
Embargoed:
mario.blaettermann: fedora-review+
gwync: fedora-cvs+


Attachments (Terms of Use)

Description Ralph Bean 2013-10-31 12:03:42 UTC
Spec URL: http://ralph.fedorapeople.org//python-twiggy.spec
SRPM URL: http://ralph.fedorapeople.org//python-twiggy-0.4.5-1.fc19.src.rpm

Description:
Twiggy is a Pythonic logger.

Comment 1 Ralph Bean 2013-10-31 12:03:47 UTC
This package built on koji:  http://koji.fedoraproject.org/koji/taskinfo?taskID=6119184

Comment 2 Mario Blättermann 2013-10-31 16:41:09 UTC
Your package is almost fine, but have a look at the latest Python guidelines first:
https://fedoraproject.org/wiki/Packaging:Python#Macros

%{__python} > %{__python}

Even %{python2_sitelib} instead of %{python_sitelib} would work (not in EPEL!) but this isn't part of the guidelines yet. However, to be mor future-proof, you might use it anyway.

Comment 4 Mario Blättermann 2013-11-01 20:29:04 UTC
Scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6123979

$ rpmlint -i -v *
python-twiggy.src: I: checking
python-twiggy.src: I: checking-url http://pypi.python.org/pypi/Twiggy (timeout 10 seconds)
python-twiggy.src: I: checking-url http://pypi.python.org/packages/source/T/Twiggy/Twiggy-0.4.5.tar.gz (timeout 10 seconds)
python-twiggy.noarch: I: checking
python-twiggy.noarch: I: checking-url http://pypi.python.org/pypi/Twiggy (timeout 10 seconds)
python-twiggy.spec: I: checking-url http://pypi.python.org/packages/source/T/Twiggy/Twiggy-0.4.5.tar.gz (timeout 10 seconds)
2 packages and 1 specfiles checked; 0 errors, 0 warnings.


---------------------------------
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.
    BSD
[+] 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 %doc.
[+] 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 *
    4e8f1894e5aee522db6cb245ccbfde3c5d1aa08d31330c7e3af783b0e66eec23  Twiggy-0.4.5.tar.gz
    4e8f1894e5aee522db6cb245ccbfde3c5d1aa08d31330c7e3af783b0e66eec23  Twiggy-0.4.5.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

----------------

Comment 5 Ralph Bean 2013-11-02 02:26:12 UTC
Thanks, Mario!

Comment 6 Ralph Bean 2013-11-02 02:27:10 UTC
New Package SCM Request
=======================
Package Name: python-twiggy
Short Description: A Pythonic logger
Owners: ralph
Branches: f20 f19 f18
InitialCC:

Comment 7 Gwyn Ciesla 2013-11-04 12:57:11 UTC
Git done (by process-git-requests).

Comment 8 Fedora Update System 2013-11-04 15:57:04 UTC
python-twiggy-0.4.5-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/python-twiggy-0.4.5-2.fc20

Comment 9 Fedora Update System 2013-11-04 15:57:23 UTC
python-twiggy-0.4.5-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-twiggy-0.4.5-2.fc19

Comment 10 Fedora Update System 2013-11-04 15:57:40 UTC
python-twiggy-0.4.5-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/python-twiggy-0.4.5-2.fc18

Comment 11 Mario Blättermann 2013-11-17 16:11:55 UTC
Packages for the requested branches are in the testing repos, so this ticket is ON_QA.

Comment 12 Fedora Update System 2013-11-23 19:39:06 UTC
python-twiggy-0.4.5-2.fc19 has been pushed to the Fedora 19 stable repository.

Comment 13 Fedora Update System 2013-11-23 19:46:51 UTC
python-twiggy-0.4.5-2.fc18 has been pushed to the Fedora 18 stable repository.

Comment 14 Fedora Update System 2013-11-24 03:55:38 UTC
python-twiggy-0.4.5-2.fc20 has been pushed to the Fedora 20 stable repository.

Comment 15 Ralph Bean 2014-09-17 15:27:29 UTC
Package Change Request
======================
Package Name: python-twiggy
New Branches: epel7
Owners: ralph

Comment 16 Gwyn Ciesla 2014-09-17 16:54:11 UTC
Git done (by process-git-requests).

Comment 17 Fedora Update System 2014-09-17 18:15:20 UTC
python-twiggy-0.4.5-3.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/python-twiggy-0.4.5-3.el7

Comment 18 Fedora Update System 2014-10-13 21:37:31 UTC
python-twiggy-0.4.5-3.el7 has been pushed to the Fedora EPEL 7 stable repository.


Note You need to log in before you can comment on or make changes to this bug.