Bug 634922

Description of problem:
rpmlint shows errors and warnings


Version-Release number of selected component (if applicable):
rusers-server-0.17-59.el6.x86_64.rpm

How reproducible:
Always

Steps to Reproduce:
1. run rpmlint -i rusers-server-0.17-59.el6.x86_64.rpm
2.
3.
  
Actual results (as shown by rpmlint):
rusers-server.x86_64: I: enchant-dictionary-not-found en_US
A dictionary for the Enchant spell checking library is not available for the
language given in the info message.  Spell checking will proceed with
rpmlint's built-in implementation for localized tags in this language.

rusers-server.x86_64: W: summary-ended-with-dot C Server for the rusers protocol.
Summary ends with a dot.

rusers-server.x86_64: W: no-url-tag
The URL tag is missing.

rusers-server.x86_64: W: conffile-without-noreplace-flag /etc/rc.d/init.d/rusersd
A configuration file is stored in your package without the noreplace flag. A
way to resolve this is to put the following in your SPEC file:
%config(noreplace) /etc/your_config_file_here

rusers-server.x86_64: W: conffile-without-noreplace-flag /etc/rc.d/init.d/rstatd
A configuration file is stored in your package without the noreplace flag. A
way to resolve this is to put the following in your SPEC file:
%config(noreplace) /etc/your_config_file_here

rusers-server.x86_64: E: executable-marked-as-config-file /etc/rc.d/init.d/rusersd
Executables must not be marked as config files because that may prevent
upgrades from working correctly. If you need to be able to customize an
executable, make it for example read a config file in /etc/sysconfig.

rusers-server.x86_64: E: executable-marked-as-config-file /etc/rc.d/init.d/rstatd
Executables must not be marked as config files because that may prevent
upgrades from working correctly. If you need to be able to customize an
executable, make it for example read a config file in /etc/sysconfig.

rusers-server.x86_64: E: unknown-key (MD5
The package was signed, but with an unknown key. See the rpm --import option
for more information.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rusersd rpc.rusersd
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.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rusersd rpc.rusersd
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.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rstatd rpc.rstatd
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.

rusers-server.x86_64: E: incoherent-subsys /etc/rc.d/init.d/rstatd rpc.rstatd
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.

1 packages and 0 specfiles checked; 7 errors, 4 warnings.