Spec URL: http://yyang.fedorapeople.org/maven2/maven-stage-plugin.spec SRPM URL: http://yyang.fedorapeople.org/maven2/maven-stage-plugin-1.0-0.1.alpha2.src.rpm Description: The Maven Stage Plugin copies artifacts from one repository to another. Its main use is for copying artifacts from a staging repository to the real repository.
I'll take this one.
Review: OK: rpmlint must be run on every package. Output: maven-stage-plugin.noarch: W: no-documentation maven-stage-plugin.noarch: W: non-conffile-in-etc /etc/maven/fragments/maven-stage-plugin False positives. 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 . OK: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines . OK: The License field in the package spec file must match the actual license. OK: 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. 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. If it does not create a directory that it uses, then it should require a package which does create that directory. 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: Large documentation files must go in a -doc subpackage. OK: If a package includes something as %doc, it must not affect the runtime of the application. OK: Packages must not own files or directories already owned by other packages. OK: All filenames in rpm packages must be valid UTF-8. This package is APPROVED.
There's no CVS request here for us to process. Please follow http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure when setting the fedora-cvs flag.
New Package CVS Request ======================= Package Name: maven-stage-plugin Short Description: Plugin to copy artifacts from one repository to another Owners: yyang Branches: devel InitialCC: huwang liweinan akurakov dbhole
New Package CVS Request ======================= Package Name: maven-stage-plugin Short Description: Plugin to copy artifacts from one repository to another Owners: yyang Branches: devel InitialCC: huwang liweinan akurtako dbhole
Yang Yong, Why have you removed my review approval ???? Please read and follow the procedures EXACTLY.
It was not removed by me, may caused by the failure of previous cvs request.
Hi Kevin, cvs is not done yet after 12 hours passed, may be caused by wrong CC, please create cvs again and leave CC blank, thanks. New Package CVS Request ======================= Package Name: maven-stage-plugin Short Description: Plugin to copy artifacts from one repository to another system Owners: yyang Branches: devel InitialCC:
http://koji.fedoraproject.org/koji/buildinfo?buildID=177404