[Bug 735891] Review Request: python-mako0.4 - Mako template library for Python

bugzilla at redhat.com bugzilla at redhat.com
Thu Sep 8 18:32:19 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=735891

Pierre-YvesChibon <pingou at pingoured.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|fedora-review?              |fedora-review+

--- Comment #9 from Pierre-YvesChibon <pingou at pingoured.fr> 2011-09-08 14:32:17 EDT ---
Ok, there is the review:

[X] rpmlint must be run on every package.
    python-mako0.4.src: W: spelling-error %description -l en_US Mako's ->
Mao's, Macho's, Makos
    python-mako0.4.src: W: spelling-error %description -l en_US componentized
-> componential, component, compartmentalized
    python-mako0.4.noarch: W: spelling-error %description -l en_US Mako's ->
Mao's, Macho's, Makos
    python-mako0.4.noarch: W: spelling-error %description -l en_US
componentized -> componential, component, compartmentalized
    python-mako0.4.noarch: W: no-manual-page-for-binary mako-render-0.4
    python3-mako0.4.noarch: W: spelling-error %description -l en_US Mako's ->
Mao's, Macho's, Makos
    python3-mako0.4.noarch: W: spelling-error %description -l en_US
componentized -> componential, component, compartmentalized
    python3-mako0.4.noarch: W: no-manual-page-for-binary
python3-mako-render-0.4
    3 packages and 0 specfiles checked; 0 errors, 8 warnings.
They can safely be ignored.

[X] The package must be named according to the Package Naming Guidelines.

[X] The spec file name must match the base package %{name}, in the format
      %{name}.spec unless your package has an exemption.

[X] The package must meet the Packaging Guidelines.

[X] The package must be licensed with a Fedora approved license and meet the
      Licensing Guidelines.

[X] The License field in the package spec file must match the actual license.
   License is MIT and Python for _ast_util.py for the code
   License is BSD and GPLv2 for the doc (which relies on sphinx)

[X] 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.

[X] The spec file must be written in American English.

[X] The spec file for the package MUST be legible.

[X] The sources used to build the package must match the upstream source, as
      provided in the spec URL.
    5d2056553910b033ac50357b94d4dc2d510d0cde  Mako-0.4.2.tar.gz
    5d2056553910b033ac50357b94d4dc2d510d0cde 
~/rpmbuild/SOURCES/Mako-0.4.2.tar.gz

[X] The package MUST successfully compile and build into binary rpms on at
     least one primary architecture.
    Builds properly under 2.6.35.14-95.fc14.x86_64
    koji rawhide build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3336161

[NA] If the package does not successfully compile, build or work on an
      architecture, then those architectures should be listed in the spec in
      ExcludeArch.

[X] 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.

[NA] The spec file MUST handle locales properly. This is done by using the
      %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.

[NA] 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.

[X] Packages must NOT bundle copies of system libraries.

[NA] 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.

[X] 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.

[X] A Fedora package must not list a file more than once in the spec file's
      %files listings.

[X] Permissions on files must be set properly. Executables should be set with
     executable permissions, for example. Every %files section must include a
     %defattr(...) line.

[X] Each package must consistently use macros.

[X] The package must contain code, or permissable content.

[NA] Large documentation files must go in a -doc subpackage.

[X] 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.

[NA] Header files must be in a -devel package.

[NA] Static libraries must be in a -static package.

[NA] If a package contains library files with a suffix (e.g. libfoo.so.1.1),
      then library files that end in .so (without suffix) must go in a -devel
      package.

[NA] In the vast majority of cases, devel packages must require the base
      package using a fully versioned dependency: Requires: %{name} =
      %{version}-%{release}.

[NA] Packages must NOT contain any .la libtool archives, these must be removed
      in the spec if they are built.

[NA] 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.

[X] Packages must not own files or directories already owned by other
      packages.

[X] All filenames in rpm packages must be valid UTF-8.


As mentioned on IRC, _ast_util.py might be worth reporting upstream as it
contains two license tags, the MIT one is probably to be removed.
Since both license are valid and mentioned in the spec.

This package is APPROVED.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the package-review mailing list