[Bug 730644] Review Request: svgSalamander - An SVG engine for Java

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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=730644

Mohamed El Morabity <pikachu.2014@xxxxxxxxx> changed:

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

--- Comment #4 from Mohamed El Morabity <pikachu.2014@xxxxxxxxx> 2011-09-08 18:11:22 EDT ---
Here is the review:

 +:ok, =:needs attention, -:needs fixing

MUST Items:
[-] MUST: rpmlint must be run on every package.
    $ rpmlint svgsalamander-0.0-3.fc14.src.rpm
    svgsalamander.src: W: spelling-error %description -l en_US graphcs ->
graphs, graphics, graph's
    svgsalamander.src: W: strange-permission svgsalamander-generate-tarball.sh
0775L
    svgsalamander.src: W: invalid-url Source0: svgsalamander-0.0.tar.gz
    > All these warnings can be ignored, EXCEPT the "strange-permission" one
    $ rpmlint svgsalamander-0.0-3.fc15.noarch.rpm
    svgsalamander.noarch: W: spelling-error %description -l en_US graphcs ->
graphs, graphics, graph's
    svgsalamander.noarch: W: non-conffile-in-etc
/etc/maven/fragments/svgsalamander
    > All these warnings can be ignored
[+] MUST: The package must be named according to the Package Naming Guidelines.
[+] MUST: The spec file name must match the base package %{name}
[+] 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.
[+] 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.
[+] MUST: The package must successfully compile and build into binary rpms on
at
          least one supported 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.
[+] MUST: All build dependencies must be listed in BuildRequires
[+] MUST: The spec file MUST handle locales properly. This is done by using
          the %find_lang macro.
[+] MUST: Every binary RPM package 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: If the package is designed to be relocatable, the packager must state
          this fact in the request for review
[+] 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 package must not contain any duplicate files in the %files listing.
[+] MUST: Permissions on files must be set properly. Executables should be set
          with executable permissions, for example. Every %files section must
          include a %defattr(...) line.
[+] MUST: Each package must consistently use macros, as described in the macros
          section of Packaging Guidelines.
[+] MUST: The package must contain code, or permissible content. This is
          described in detail in the code vs. content section of Packaging
          Guidelines.
[+] MUST: Large documentation files should go in a doc subpackage.
[+] MUST: If a package includes something as %doc, it must not affect the
          runtime of the application.
[+] MUST: Header files must be in a -devel package.
[+] MUST: Static libraries must be in a -static package.
[+] MUST: Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig'
          (for directory ownership and usability).
[+] MUST: 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.
[+] MUST: In the vast majority of cases, devel packages must require the base
          package using a fully versioned dependency: Requires: %{name}
          = %{version}-%{release}
[+] MUST: Packages must NOT contain any .la libtool archives, these should be
          removed in the spec.
[+] 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.
[+] MUST: Packages must not own files or directories already owned by other
packages.
[+] MUST: All filenames in rpm packages must be valid UTF-8.

Once the permissions on %{SOURCE1} fixed, I will approve this package.

-- 
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.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review


[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]