Bug 595220
Summary: | Review Request: buildnumber-maven-plugin - Build Number Maven Plugin | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Weinan Li <weli> |
Component: | Package Review | Assignee: | Alexander Kurtakov <akurtako> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | akurtako, fedora-package-review, notting, orion |
Target Milestone: | --- | Flags: | akurtako:
fedora-review+
dennis: fedora-cvs+ |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-05-28 08:06:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Weinan Li
2010-05-24 06:18:48 UTC
Things to be fixed: buildnumber-maven-plugin-javadoc.noarch: W: invalid-license The MIT License buildnumber-maven-plugin-javadoc.noarch: W: dangling-relative-symlink /usr/share/javadoc/buildnumber-maven-plugin buildnumber-maven-plugin-1.0 buildnumber-maven-plugin.noarch: W: incoherent-version-in-changelog 1.0-beta-4-1 ['1.0-0.1.beta4.fc13', '1.0-0.1.beta4'] javadoc subpackage is missing requires on jpackage-utils main package is missing standart requires: Requires: jpackage-utils Requires(post): jpackage-utils Requires(postun): jpackage-utils Requires: java global should be used instead of define Sorry the last link is incorrect. It does not contains necessary patches and depmap. This one is correct and checked with rpmlint: Package URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/ Spec URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin.spec SRPM URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin-1.0-0.1.b4.src.rpm Description: This mojo is designed to get a unique build number for each time you build your project. Note: - this needs to be built in the dist-f14-maven221 koji tag. Here is a successful koji scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2209827 - 'install' goal is disabled from 'integration-test' with a patch, because we need newer version of maven. - 'maven-scm-provider-svnjava' is removed from dependency because we don't have it yet. This is still not fixed: javadoc subpackage is missing requires on jpackage-utils And when you change something you should add a changelog entry. - Add requires on jpackage-utils for javadoc subpackage - Add standard jpackage-utils requires on main package - Use global instead of define - Fix license to MIT - Fix incoherent-version-in-changelog Spec URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin.spec SRPM URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin-1.0-0.2.b4.src.rpm Note: - This needs to be built in the dist-f14-maven221 koji tag. Here is a successful koji scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2210229 Review: FIXIT: rpmlint must be run on every package. Output: buildnumber-maven-plugin.noarch: W: spelling-error %description -l en_US mojo -> moo, mono, Tojo buildnumber-maven-plugin.noarch: W: spelling-error %description -l en_US scm -> cm, scam, scum buildnumber-maven-plugin.noarch: W: spelling-error %description -l en_US svn -> sen, sin, son buildnumber-maven-plugin.noarch: W: spelling-error %description -l en_US metadata -> meta data, meta-data, metatarsus buildnumber-maven-plugin.noarch: W: spelling-error %description -l en_US timestamp -> time stamp, time-stamp, times tamp buildnumber-maven-plugin.noarch: W: no-documentation buildnumber-maven-plugin.noarch: W: non-conffile-in-etc /etc/maven/fragments/buildnumber-maven-plugin Not a problem. buildnumber-maven-plugin-javadoc.noarch: W: dangling-relative-symlink /usr/share/javadoc/buildnumber-maven-plugin buildnumber-maven-plugin-1.0 Should be fixed. 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. Are you sure that you have all the Requires needed? E.g is svnkit,jna and etc. a build time dependency only? - Fix javadoc dangling-relative-symlink - No more requires needed (E.g no svnkit, jna needed) for Requires section after analyzing the project dependencies with JBoss Taletattle. Spec URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin.spec SRPM URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin-1.0-0.3.b4.src.rpm Note: - This needs to be built in the dist-f14-maven221 koji tag. Here is a successful koji scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2212137 License.txt and Readme.txt should be added as %doc - License.txt and Readme.txt added as %doc Spec URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin.spec SRPM URL: http://weli.fedorapeople.org/packages/fedora-14/bmp/buildnumber-maven-plugin-1.0-0.4.b4.src.rpm Note: - This needs to be built in the dist-f14-maven221 koji tag. Here is a successful koji scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2212209 Looks good. This package is APPROVED. New Package CVS Request ======================= Package Name: buildnumber-maven-plugin Short Description: This mojo is designed to get a unique build number for each time you build your project. Owners: weli Branches: InitialCC: akurtakov CVS Done Build in koji. http://koji.fedoraproject.org/koji/buildinfo?buildID=175426 Could we get a F14 build done? Thanks! Sorry, that was a f14 build - scratch that. |