Bug 709051 - Review Request: sonatype-gossip - SLF4j Gossip Provider
Summary: Review Request: sonatype-gossip - SLF4j Gossip Provider
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andrew Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 708842
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-30 13:27 UTC by Marek Goldmann
Modified: 2011-09-26 09:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-09-26 09:04:49 UTC
Type: ---
Embargoed:
andjrobins: fedora-review+
andjrobins: needinfo-
gwync: fedora-cvs+


Attachments (Terms of Use)

Description Marek Goldmann 2011-05-30 13:27:19 UTC
Spec URL: http://goldmann.fedorapeople.org/package_review/gossip/1/gossip.spec
SRPM URL: http://goldmann.fedorapeople.org/package_review/gossip/1/gossip-1.7-1.fc15.src.rpm
Description:

Gossip is a plugin for SLF4j which has simple and flexible configuration.

Comment 1 Andrew Robinson 2011-09-07 18:04:31 UTC
Package Review
==============

Key:
- = N/A
x = Check
! = Problem
? = Not evaluated

=== REQUIRED ITEMS ===
[X]  Rpmlint output:
/home/arobinso/runtime-EclipseApplication/gossip/gossip.spec: W: invalid-url Source0: gossip-1.7.tar.xz
The value should be a valid, public HTTP, HTTPS, or FTP URL.

0 packages and 1 specfiles checked; 0 errors, 1 warnings.
[X]  Package is named according to the Package Naming Guidelines[1].
[X]  Spec file name must match the base package name, in the format %{name}.spec.
[!]  Package meets the Packaging Guidelines[2].
[!]  Package successfully compiles and builds into binary rpms.
[X]  Buildroot definition is not present
[X]  Package is licensed with an open-source compatible license and meets other legal requirements as defined in the legal section of Packaging Guidelines[3,4].
[X]  License field in the package spec file matches the actual license.
License type:ASL 2.0
[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 is included in %doc.
[X]  All independent sub-packages have license of their own
[X]  Spec file is legible and written in American English.
[X]  Sources used to build the package matches the upstream source, as provided in the spec URL.
MD5SUM this package    :e5502293cc40c9b76d92800fc0599834
MD5SUM upstream package:e5502293cc40c9b76d92800fc0599834
[!]  All build dependencies are listed in BuildRequires, except for any that are listed in the exceptions section of Packaging Guidelines[5].
[X]  Package must own all directories that it creates.
[X]  Package requires other packages for directories it uses.
[X]  Package does not contain duplicates in %files.
[X]  File sections do not contain %defattr(-,root,root,-) unless changed with good reason
[X]  Permissions on files are set properly.
[X]  Package does NOT have a %clean section which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT). (not needed anymore)
[X]  Package consistently uses macros (no %{buildroot} and $RPM_BUILD_ROOT mixing)
[X]  Package contains code, or permissable content.
[X]  Fully versioned dependency in subpackages, if present.
[-]  Package contains a properly installed %{name}.desktop file if it is a GUI application.
[X]  Package does not own files or directories owned by other packages.
[X]  Javadoc documentation files are generated and included in -javadoc subpackage
[X]  Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlinks)
[!]  Packages have proper BuildRequires/Requires on jpackage-utils
[X]  Javadoc subpackages have Require: jpackage-utils
[X]  Package uses %global not %define
[X]  If package uses tarball from VCS include comment how to re-create that tarball (svn export URL, git clone URL, ...)
[-]  If source tarball includes bundled jar/class files these need to be removed prior to building
[X]  All filenames in rpm packages must be valid UTF-8.
[X]  Jar files are installed to %{_javadir}/%{name}.jar (see [6] for details)
[X]  If package contains pom.xml files install it (including depmaps) even when building with ant
[X]  pom files has correct add_maven_depmap

=== Maven ===
[X]  Use %{_mavenpomdir} macro for placing pom files instead of %{_datadir}/maven2/poms
[-]  If package uses "-Dmaven.test.skip=true" explain why it was needed in a comment
[-]  If package uses custom depmap "-Dmaven.local.depmap.file=*" explain why it's needed in a comment
[!]  Package DOES NOT use %update_maven_depmap in %post/%postun
[!]  Packages DOES NOT have Requires(post) and Requires(postun) on jpackage-utils for %update_maven_depmap macro

=== Other suggestions ===
[X]  If possible use upstream build method (maven/ant/javac)
[X]  Avoid having BuildRequires on exact NVR unless necessary
[X]  Package has BuildArch: noarch (if possible)
[X]  Latest version is packaged.
[!]  Reviewer should test that the package builds in mock.
Tested on:x86_64

=== Issues ===
1. Package doesn't build on rawhide. It is missing a BR for fusesource-pom and may have other issues.
2. Remove the post and postun requires.
3. Remove the entire post and postun setcions.

Comment 2 Stanislav Ochotnicky 2011-09-15 11:25:05 UTC
FYI in the meantime gossip 1.9 has been released.

Comment 4 Andrew Robinson 2011-09-19 14:31:57 UTC


[X]  Rpmlint output:
/home/arobinso/runtime-EclipseApplication/gossip/gossip.spec: W: invalid-url
Source0: gossip-1.7.tar.xz
The value should be a valid, public HTTP, HTTPS, or FTP URL.

0 packages and 1 specfiles checked; 0 errors, 1 warnings.
[X]  Package is named according to the Package Naming Guidelines[1].
[X]  Spec file name must match the base package name, in the format
%{name}.spec.
[X]  Package meets the Packaging Guidelines[2].
[X]  Package successfully compiles and builds into binary rpms.
[X]  Buildroot definition is not present
[X]  Package is licensed with an open-source compatible license and meets other
legal requirements as defined in the legal section of Packaging
Guidelines[3,4].
[X]  License field in the package spec file matches the actual license.
License type:ASL 2.0
[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 is included in %doc.
[X]  All independent sub-packages have license of their own
[X]  Spec file is legible and written in American English.
[X]  Sources used to build the package matches the upstream source, as provided
in the spec URL.
MD5SUM this package    :e5502293cc40c9b76d92800fc0599834
MD5SUM upstream package:e5502293cc40c9b76d92800fc0599834
[X]  All build dependencies are listed in BuildRequires, except for any that
are listed in the exceptions section of Packaging Guidelines[5].
[X]  Package must own all directories that it creates.
[X]  Package requires other packages for directories it uses.
[X]  Package does not contain duplicates in %files.
[X]  File sections do not contain %defattr(-,root,root,-) unless changed with
good reason
[X]  Permissions on files are set properly.
[X]  Package does NOT have a %clean section which contains rm -rf %{buildroot}
(or $RPM_BUILD_ROOT). (not needed anymore)
[X]  Package consistently uses macros (no %{buildroot} and $RPM_BUILD_ROOT
mixing)
[X]  Package contains code, or permissable content.
[X]  Fully versioned dependency in subpackages, if present.
[-]  Package contains a properly installed %{name}.desktop file if it is a GUI
application.
[X]  Package does not own files or directories owned by other packages.
[X]  Javadoc documentation files are generated and included in -javadoc
subpackage
[X]  Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlinks)
[X]  Packages have proper BuildRequires/Requires on jpackage-utils
[X]  Javadoc subpackages have Require: jpackage-utils
[X]  Package uses %global not %define
[X]  If package uses tarball from VCS include comment how to re-create that
tarball (svn export URL, git clone URL, ...)
[-]  If source tarball includes bundled jar/class files these need to be
removed prior to building
[X]  All filenames in rpm packages must be valid UTF-8.
[X]  Jar files are installed to %{_javadir}/%{name}.jar (see [6] for details)
[X]  If package contains pom.xml files install it (including depmaps) even when
building with ant
[X]  pom files has correct add_maven_depmap

=== Maven ===
[X]  Use %{_mavenpomdir} macro for placing pom files instead of
%{_datadir}/maven2/poms
[-]  If package uses "-Dmaven.test.skip=true" explain why it was needed in a
comment
[-]  If package uses custom depmap "-Dmaven.local.depmap.file=*" explain why
it's needed in a comment
[X]  Package DOES NOT use %update_maven_depmap in %post/%postun
[X]  Packages DOES NOT have Requires(post) and Requires(postun) on
jpackage-utils for %update_maven_depmap macro

=== Other suggestions ===
[X]  If possible use upstream build method (maven/ant/javac)
[X]  Avoid having BuildRequires on exact NVR unless necessary
[X]  Package has BuildArch: noarch (if possible)
[X]  Latest version is packaged.
[X]  Reviewer should test that the package builds in mock.
Tested on:x86_64, i386

=== Comments ===
1. I can only find 1.7 as being the most recent release and it is certainly thr most recent release for the URL provided.

********
APPROVED
********

Comment 5 Marek Goldmann 2011-09-19 14:41:36 UTC
Thank you for review!

New Package SCM Request
=======================
Package Name:      gossip
Short Description: SLF4j Gossip Provider
Owners:            goldmann

Comment 6 Gwyn Ciesla 2011-09-19 15:16:38 UTC
Unretired, please take ownership in pkgdb, and request any needed branches here.

Comment 7 Stanislav Ochotnicky 2011-09-20 13:33:48 UTC
Hmm, nevermind the 1.9, It must have been some glitch in my processing unit.

Comment 8 Marek Goldmann 2011-09-21 09:00:37 UTC
(In reply to comment #6)
> Unretired, please take ownership in pkgdb, and request any needed branches
> here.

Jon,

Uh, I think we have a collision here. My gossip is a Java library, whereas gossip in package database is a Jabber client. What's the best options here? Should I rename my package for example to gossip-java?

Comment 9 Marek Goldmann 2011-09-22 08:29:39 UTC
Andrew,

I changed the name of the package to sonatype-gossip to avoid above collision with previous Jabber client, could you please re-review this package? No changes were made other than changing the name, btw.

Spec URL: http://goldmann.fedorapeople.org/package_review/gossip/4/sonatype-gossip.spec
SRPM URL:
http://goldmann.fedorapeople.org/package_review/gossip/4/sonatype-gossip-1.7-3.fc17.src.rpm

Comment 10 Andrew Robinson 2011-09-22 13:24:29 UTC
[X]  Rpmlint output:
/home/arobinso/runtime-EclipseApplication/gossip/gossip.spec: W: invalid-url
Source0: gossip-1.7.tar.xz
The value should be a valid, public HTTP, HTTPS, or FTP URL.

0 packages and 1 specfiles checked; 0 errors, 1 warnings.
[X]  Package is named according to the Package Naming Guidelines[1].
[X]  Spec file name must match the base package name, in the format
%{name}.spec.
[X]  Package meets the Packaging Guidelines[2].
[X]  Package successfully compiles and builds into binary rpms.
[X]  Buildroot definition is not present
[X]  Package is licensed with an open-source compatible license and meets other
legal requirements as defined in the legal section of Packaging
Guidelines[3,4].
[X]  License field in the package spec file matches the actual license.
License type:ASL 2.0
[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 is included in %doc.
[X]  All independent sub-packages have license of their own
[X]  Spec file is legible and written in American English.
[X]  Sources used to build the package matches the upstream source, as provided
in the spec URL.
MD5SUM this package    :e5502293cc40c9b76d92800fc0599834
MD5SUM upstream package:e5502293cc40c9b76d92800fc0599834
[X]  All build dependencies are listed in BuildRequires, except for any that
are listed in the exceptions section of Packaging Guidelines[5].
[X]  Package must own all directories that it creates.
[X]  Package requires other packages for directories it uses.
[X]  Package does not contain duplicates in %files.
[X]  File sections do not contain %defattr(-,root,root,-) unless changed with
good reason
[X]  Permissions on files are set properly.
[X]  Package does NOT have a %clean section which contains rm -rf %{buildroot}
(or $RPM_BUILD_ROOT). (not needed anymore)
[X]  Package consistently uses macros (no %{buildroot} and $RPM_BUILD_ROOT
mixing)
[X]  Package contains code, or permissable content.
[X]  Fully versioned dependency in subpackages, if present.
[-]  Package contains a properly installed %{name}.desktop file if it is a GUI
application.
[X]  Package does not own files or directories owned by other packages.
[X]  Javadoc documentation files are generated and included in -javadoc
subpackage
[X]  Javadocs are placed in %{_javadocdir}/%{name} (no -%{version} symlinks)
[X]  Packages have proper BuildRequires/Requires on jpackage-utils
[X]  Javadoc subpackages have Require: jpackage-utils
[X]  Package uses %global not %define
[X]  If package uses tarball from VCS include comment how to re-create that
tarball (svn export URL, git clone URL, ...)
[-]  If source tarball includes bundled jar/class files these need to be
removed prior to building
[X]  All filenames in rpm packages must be valid UTF-8.
[X]  Jar files are installed to %{_javadir}/%{name}.jar (see [6] for details)
[X]  If package contains pom.xml files install it (including depmaps) even when
building with ant
[X]  pom files has correct add_maven_depmap

=== Maven ===
[X]  Use %{_mavenpomdir} macro for placing pom files instead of
%{_datadir}/maven2/poms
[-]  If package uses "-Dmaven.test.skip=true" explain why it was needed in a
comment
[-]  If package uses custom depmap "-Dmaven.local.depmap.file=*" explain why
it's needed in a comment
[X]  Package DOES NOT use %update_maven_depmap in %post/%postun
[X]  Packages DOES NOT have Requires(post) and Requires(postun) on
jpackage-utils for %update_maven_depmap macro

=== Other suggestions ===
[X]  If possible use upstream build method (maven/ant/javac)
[X]  Avoid having BuildRequires on exact NVR unless necessary
[X]  Package has BuildArch: noarch (if possible)
[X]  Latest version is packaged.
[X]  Reviewer should test that the package builds in mock.
Tested on:x86_64, i386

=== Comments ===
1. This time it doesn't collide.

********
APPROVED
********

Comment 11 Marek Goldmann 2011-09-22 13:41:30 UTC
Thank you for review, again!

SCM request sent again because of name collision - see comment #8 and #9.

New Package SCM Request
=======================
Package Name:      sonatype-gossip
Short Description: SLF4j Gossip Provider
Owners:            goldmann

Comment 12 Gwyn Ciesla 2011-09-24 15:22:50 UTC
Git done (by process-git-requests).

Comment 13 Marek Goldmann 2011-09-26 09:04:49 UTC
Thanks for git, closing.


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