[Bug 494693] Review Request: gloox - A rock-solid, full-featured Jabber/XMPP client library

[bugzilla at redhat.com]

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


Peter Lemenkov <lemenkov at gmail.com> changed:

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




--- Comment #7 from Peter Lemenkov <lemenkov at gmail.com>  2009-04-19 08:47:44 EDT ---
+ MUST: rpmlint must be run on every package. The output should be posted in
the review.[1]

[petro at Sulaco SPECS]$ rpmlint ../RPMS/ppc/gloox-*
gloox-devel.ppc: W: no-documentation
3 packages and 0 specfiles checked; 0 errors, 1 warnings.
[petro at Sulaco SPECS]$

This warning is safe to ignore.

+ MUST: The package must be named according to the Package Naming Guidelines .
+ MUST: The spec file name must match the base package %{name}, in the format
%{name}.spec unless your package has an exemption. [2] .
+ 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. [3]
+ 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.[4]
+ MUST: The spec file must be written in American English. [5]
+ MUST: The spec file for the package MUST be legible. [6]
+ MUST: The sources used to build the package must match the upstream source,
as provided in the spec URL. Reviewers should use md5sum for this task. If no
upstream URL can be specified for this package, please see the Source URL
Guidelines for how to deal with this.

Actually, we cannot simply use md5sum for verifying sources from VCS, but we
can diff -ru them.

[petro at Sulaco SOURCES]$ tar xf gloox-1.0-SVNr4003.tar.bz2 
[petro at Sulaco SOURCES]$ svn export -r4003 svn://svn.camaya.net/gloox/trunk
gloox-1.0.svn > /dev/null 
[petro at Sulaco SOURCES]$ diff -ru gloox-1.0 gloox-1.0.svn/
[petro at Sulaco SOURCES]$

+ MUST: The package MUST successfully compile and build into binary rpms on at
least one primary architecture.
+ MUST: 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.
+ MUST: Every binary RPM package (or subpackage) which stores shared library
files (not just symlinks) in any of the dynamic linker's default paths, must
call ldconfig in %post and %postun. [10]
+ MUST: A Fedora package must not list a file more than once in the spec file's
%files listings. [13]
+ 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. [14]
+ MUST: Each package must have a %clean section, which contains rm -rf
%{buildroot} (or $RPM_BUILD_ROOT). [15]
+ MUST: Each package must consistently use macros. [16]
+ MUST: The package must contain code, or permissable content. [17]
+ MUST: If a package includes something as %doc, it must not affect the runtime
of the application. To summarize: If it is in %doc, the program must run
properly if it is not present. [18]
+ MUST: Header files must be in a -devel package. [19]
+ MUST: Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig'
(for directory ownership and usability). [21]
+ 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. [19]
+ MUST: In the vast majority of cases, devel packages must require the base
package using a fully versioned dependency: Requires: %{name} =
%{version}-%{release} [22]
+ MUST: Packages must NOT contain any .la libtool archives, these must be
removed in the spec if they are built.[20]
+ MUST: Packages must not own files or directories already owned by other
packages. The rule of thumb here is that the first package to be installed
should own the files or directories that other packages may rely upon. This
means, for example, that no package in Fedora should ever share ownership with
any of the files or directories owned by the filesystem or man package. If you
feel that you have a good reason to own a file or directory that another
package owns, then please present that at package review time. [24]
+ MUST: At the beginning of %install, each package MUST run rm -rf %{buildroot}
(or $RPM_BUILD_ROOT). [25]
+ MUST: All filenames in rpm packages must be valid UTF-8. [26]

APPROVED.

-- 
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.