Bug 630591 - Review Request: mojo-parent - Codehaus MOJO parent project pom file
Summary: Review Request: mojo-parent - Codehaus MOJO parent project pom file
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Kurtakov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-06 10:59 UTC by Stanislav Ochotnicky
Modified: 2010-09-16 08:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-16 08:47:40 UTC
Type: ---
Embargoed:
akurtako: fedora-review+
petersen: fedora-cvs+


Attachments (Terms of Use)

Description Stanislav Ochotnicky 2010-09-06 10:59:08 UTC
Spec URL: http://sochotni.fedorapeople.org/packages/mojo-parent.spec
SRPM URL: http://sochotni.fedorapeople.org/packages/mojo-parent-24-1.fc15.src.rpm

Description: Codehaus MOJO parent project pom file

Comment 1 Alexander Kurtakov 2010-09-06 11:10:44 UTC
I'll do this one.

Comment 2 Stanislav Ochotnicky 2010-09-06 11:46:09 UTC
Spec URL: http://sochotni.fedorapeople.org/packages/mojo-parent.spec
SRPM URL:
http://sochotni.fedorapeople.org/packages/mojo-parent-24-2.fc15.src.rpm

Changes: removed %build section and BRs

Comment 3 Alexander Kurtakov 2010-09-06 16:27:56 UTC
Review:
OK: rpmlint must be run on every package. Output:
mojo-parent.noarch: W: spelling-error Summary(en_US) Codehaus -> Codename, Codewords, Code's
mojo-parent.noarch: W: spelling-error %description -l en_US Codehaus -> Codename, Codewords, Code's
False positive.
mojo-parent.noarch: W: no-documentation
No suitable documentation.
mojo-parent.noarch: W: non-conffile-in-etc /etc/maven/fragments/mojo-parent
Not a problem.
OK: The package must be named according to the Package Naming Guidelines .
OK: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption.
OK: The package must meet the Packaging Guidelines .
FIXIT: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines .
FIXIT: The License field in the package spec file must match the actual license.
OK: The spec file must be written in American English. 
OK: The spec file for the package MUST be legible. 
OK: The sources used to build the package must match the upstream source, as provided in the spec URL.
OK: The package MUST successfully compile and build into binary rpms on at least one primary architecture.
OK: 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.
OK: Packages must NOT bundle copies of system libraries.
OK: A package must own all directories that it creates. 
OK: A Fedora package must not list a file more than once in the spec file's %files listings. 
OK: Permissions on files must be set properly. Executables should be set with executable permissions, for example. Every %files section must include a %defattr(...) line. [
OK: Each package must consistently use macros.
OK: The package must contain code, or permissable content.
OK: Packages must not own files or directories already owned by other packages. 
OK: All filenames in rpm packages must be valid UTF-8. 

So one big issue. We need license cleared.

Comment 5 Alexander Kurtakov 2010-09-14 13:57:39 UTC
Thanks,
This package is APPROVED.

Comment 6 Stanislav Ochotnicky 2010-09-14 14:15:27 UTC
Thank you for the review.

New Package CVS Request
=======================
Package Name: mojo-parent
Short Description: Codehaus MOJO parent project pom file
Owners: sochotni
Branches: F-14 devel
InitialCC:

Comment 7 Jens Petersen 2010-09-16 04:15:18 UTC
Git done (by process-git-requests).

Comment 8 Stanislav Ochotnicky 2010-09-16 08:47:40 UTC
Thank you.

Koji build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2470886


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