[Bug 442371] Review Request: collectd - Statistics collection daemon for filling RRD files

bugzilla at redhat.com bugzilla at redhat.com
Mon Apr 21 14:12:26 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: collectd - Statistics collection daemon for filling RRD files


https://bugzilla.redhat.com/show_bug.cgi?id=442371


berrange at redhat.com changed:

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




------- Additional Comments From berrange at redhat.com  2008-04-21 10:12 EST -------
MUST: rpmlint must be run on every package.

$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-4.3.2-6.i386.rpm
collectd.i386: W: incoherent-subsys /etc/rc.d/init.d/collectd $prog
collectd.i386: W: incoherent-subsys /etc/rc.d/init.d/collectd $prog
collectd.i386: W: incoherent-subsys /etc/rc.d/init.d/collectd $prog
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-apache-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-email-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-mysql-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-nginx-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/perl-Collectd-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-sensors-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-snmp-4.3.2-6.i386.rpm
$ rpmlint /home/berrange/rpm/RPMS/i386/collectd-virt-4.3.2-6.i386.rpm
$ rpmlint collectd-4.3.2-6.src.rpm 

The warnings are rpmlint bugs, not being able to understand/interpret shell
variable substitutions

=> PASS

MUST: The package must be named according to the Package Naming Guidelines.

PASS

MUST: The spec file name must match the base package %{name}

PASS

MUST: The package must meet the Packaging Guidelines.

PASS

MUST: The package must be licensed with a Fedora approved license and meet the
Licensing Guidelines.

PASS

MUST: The License field in the package spec file must match the actual license.

PASS

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.

PASS

MUST: The spec file must be written in American English.

PASS

MUST: The spec file for the package MUST be legible.

PASS

MUST: The sources used to build the package must match the upstream source

PASS

MUST: The package must successfully compile and build into binary rpms on at
least one supported architecture.

PASS

MUST: If the package does not successfully compile, build or work on an
architecture, then those architectures should be listed in the spec in ExcludeArch.

PASS

MUST: All build dependencies must be listed in BuildRequires

PASS

MUST: The spec file MUST handle locales properly

N/A - no locales

MUST: Every binary RPM package which stores shared library files (not just
symlinks) in any of the dynamic linker's default paths, must call ldconfig in
%post and %postun.

N/A - no public libs, only plugins

MUST: If the package is designed to be relocatable, the packager must state this
fact in the request for review

N/A

MUST: A package must own all directories that it creates.

PASS

MUST: A package must not contain any duplicate files in the %files listing.

PASS

MUST: Permissions on files must be set properly.

PASS

MUST: Each package must have a %clean section

PASS

MUST: Each package must consistently use macros

PASS

MUST: The package must contain code, or permissable content

PASS

MUST: Large documentation files should go in a -doc subpackage

N/A

MUST: If a package includes something as %doc, it must not affect the runtime of
the application

PASS

MUST: Header files must be in a -devel package.

N/A

MUST: Static libraries must be in a -static package.

N/A

MUST: Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig'

N/A

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.

N/A

MUST: In the vast majority of cases, devel packages must require the base
package using a fully versioned dependency

N/A

MUST: Packages must NOT contain any .la libtool archives

PASS

MUST: Packages containing GUI applications must include a %{name}.desktop file

N/A

MUST: Packages must not own files or directories already owned by other packages

PASS

MUST: At the beginning of %install, each package MUST run rm -rf %{buildroot}

PASS

MUST: All filenames in rpm packages must be valid UTF-8.

PASS

SHOULD: If the source package does not include license text(s) as a separate
file from upstream, the packager SHOULD query upstream to include it.

N/A

SHOULD: The description and summary sections in the package spec file should
contain translations for supported Non-English languages, if available.

N/A

SHOULD: The reviewer should test that the package builds in mock.

PASS

SHOULD: The package should compile and build into binary rpms on all supported
architectures.

PASS

SHOULD: The reviewer should test that the package functions as described.

PASS

SHOULD: If scriptlets are used, those scriptlets must be sane.

PASS

SHOULD: Usually, subpackages other than devel should require the base package
using a fully versioned dependency.

PASS, though recommend

Requires:      collectd = %{version}

be changed to more specific:

Requires:      collectd = %{version}-%{release}

SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and this
is usually for development purposes, so should be placed in a -devel pkg.

N/A

SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin,
/usr/bin, or /usr/sbin consider requiring the package which provides the file
instead of the file itself.

N/A


=> 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, or are watching someone who is.




More information about the package-review mailing list