[Bug 399301] Review Request: glusterfs - Cluster File System

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

Summary: Review Request: glusterfs - Cluster File System


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





------- Additional Comments From limb at jcomserv.net  2007-12-10 07:35 EST -------
Ah, much better.  This builds.

rpmlint:

Clean for SRPM.

glusterfs-client.i386: W: no-documentation
The package contains no documentation (README, doc, etc).
You have to include documentation files.

glusterfs-client.i386: W: log-files-without-logrotate /var/log/glusterfs
This package contains files in /var/log/ without adding logrotate
configuration for them.

glusterfs-devel.i386: W: no-documentation
The package contains no documentation (README, doc, etc).
You have to include documentation files.

glusterfs-devel.i386: W: no-dependency-on glusterfs
glusterfs-libs.i386: W: obsolete-not-provided glusterfs-common
If a package is obsoleted by a compatible replacement, the obsoleted package
must also be provided in order to provide clean upgrade paths and not cause
unnecessary dependency breakage.  If the obsoleting package is not a compatible
replacement for the old one, leave out the provides.

glusterfs-server.i386: W: log-files-without-logrotate /var/log/glusterfs
This package contains files in /var/log/ without adding logrotate
configuration for them.

glusterfs-server.i386: W: incoherent-subsys /etc/init.d/glusterfsd $prog
The filename of your lock file in /var/lock/subsys/ is incoherent
with your actual init script name. For example, if your script name
is httpd, you have to use 'httpd' as the filename in your subsys directory.
It is also possible that rpmlint gets this wrong, especially if the init
script contains nontrivial shell variables and/or assignments.  These
cases usually manifest themselves when rpmlint reports that the subsys name
starts a with '$'; in these cases a warning instead of an error is reported
and you should check the script manually.

glusterfs-server.i386: W: incoherent-subsys /etc/init.d/glusterfsd $prog
The filename of your lock file in /var/lock/subsys/ is incoherent
with your actual init script name. For example, if your script name
is httpd, you have to use 'httpd' as the filename in your subsys directory.
It is also possible that rpmlint gets this wrong, especially if the init
script contains nontrivial shell variables and/or assignments.  These
cases usually manifest themselves when rpmlint reports that the subsys name
starts a with '$'; in these cases a warning instead of an error is reported
and you should check the script manually.

glusterfs-server.i386: W: incoherent-subsys /etc/init.d/glusterfsd $prog
The filename of your lock file in /var/lock/subsys/ is incoherent
with your actual init script name. For example, if your script name
is httpd, you have to use 'httpd' as the filename in your subsys directory.
It is also possible that rpmlint gets this wrong, especially if the init
script contains nontrivial shell variables and/or assignments.  These
cases usually manifest themselves when rpmlint reports that the subsys name
starts a with '$'; in these cases a warning instead of an error is reported
and you should check the script manually.

glusterfs-server.i386: W: incoherent-init-script-name glusterfsd
The init script name should be the same as the package name in lower case,
or one with 'd' appended if it invokes a process by that name.


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