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=530684 --- Comment #9 from Jon Ciesla <limb@xxxxxxxxxxxx> 2011-06-27 13:35:29 EDT --- Ok, it builds now. :) rpmlint: nordugrid-arc.src: W: spelling-error %description -l en_US middleware -> middle ware, middle-ware, middleweight The value of this tag appears to be misspelled. Please double-check. nordugrid-arc.src: W: spelling-error %description -l en_US organisation -> organization, organist, sanitation The value of this tag appears to be misspelled. Please double-check. nordugrid-arc.src: W: spelling-error %description -l en_US analyse -> analyses, analyst, analyze The value of this tag appears to be misspelled. Please double-check. Fix 2 and 3, skip 1. nordugrid-arc-aris.noarch: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-aris.noarch: E: subsys-not-used /etc/rc.d/init.d/grid-infosys While your daemon is running, you have to put a lock file in /var/lock/subsys/. To see an example, look at this directory on your machine and examine the corresponding init scripts. nordugrid-arc-aris.noarch: W: incoherent-init-script-name grid-infosys ('nordugrid-arc-aris', 'nordugrid-arc-arisd') 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. nordugrid-arc-ca-utils.noarch: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-gridmap-utils.noarch: W: no-manual-page-for-binary nordugridmap Each executable in standard binary directories should have a man page. nordugrid-arc-ldap-monitor.noarch: E: zero-length /usr/share/arc/ldap-monitor/cache/placeholder nordugrid-arc-ws-monitor.noarch: E: zero-length /usr/share/arc/ws-monitor/cache/placeholder nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-httpsd If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-logger-server If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-nox-charon If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-nox-compiler If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-nox-delegation If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-nox-paul If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-nox-saml2sp If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: obsolete-not-provided nordugrid-arc-nox-slcs If a package is obsoleted by a compatible replacement, the obsoleted package should also be provided in order to not cause unnecessary dependency breakage. If the obsoleting package is not a compatible replacement for the old one, leave out the Provides. nordugrid-arc.x86_64: W: shared-lib-calls-exit /usr/lib64/libarccrypto.so.1.0.0 _exit@GLIBC_2.2.5 This library package calls exit() or _exit(), probably in a non-fork() context. Doing so from a library is strongly discouraged - when a library function calls exit(), it prevents the calling program from handling the error, reporting it to the user, closing files properly, and cleaning up any state that the program has. It is preferred for the library to return an actual error code and let the calling program decide how to handle the situation. nordugrid-arc.x86_64: W: shared-lib-calls-exit /usr/lib64/libarccommon.so.1.0.0 exit@GLIBC_2.2.5 This library package calls exit() or _exit(), probably in a non-fork() context. Doing so from a library is strongly discouraged - when a library function calls exit(), it prevents the calling program from handling the error, reporting it to the user, closing files properly, and cleaning up any state that the program has. It is preferred for the library to return an actual error code and let the calling program decide how to handle the situation. nordugrid-arc.x86_64: E: zero-length /usr/lib64/arc/libmodcredential.apd nordugrid-arc.x86_64: E: zero-length /usr/lib64/arc/libmodcrypto.apd nordugrid-arc-arex.x86_64: W: incoherent-subsys /etc/rc.d/init.d/a-rex $prog-arex 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. nordugrid-arc-arex.x86_64: W: incoherent-init-script-name a-rex ('nordugrid-arc-arex', 'nordugrid-arc-arexd') 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. nordugrid-arc-cache-service.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-cache-service.x86_64: W: incoherent-subsys /etc/rc.d/init.d/cache-service $prog-cache-service 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. nordugrid-arc-cache-service.x86_64: W: incoherent-init-script-name cache-service ('nordugrid-arc-cache-service', 'nordugrid-arc-cache-serviced') 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. nordugrid-arc-chelonia.x86_64: W: no-manual-page-for-binary arcfs Each executable in standard binary directories should have a man page. nordugrid-arc-egiis.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-egiis.x86_64: E: zero-length /usr/lib64/arc/arc-infoindex-slapd-wrapper.apd nordugrid-arc-egiis.x86_64: W: no-manual-page-for-binary arc-infoindex-server Each executable in standard binary directories should have a man page. nordugrid-arc-egiis.x86_64: W: no-manual-page-for-binary arc-infoindex-relay Each executable in standard binary directories should have a man page. nordugrid-arc-gridftpd.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-gridftpd.x86_64: E: zero-length /usr/lib64/arc/fileplugin.apd nordugrid-arc-gridftpd.x86_64: E: zero-length /usr/lib64/arc/gaclplugin.apd nordugrid-arc-gridftpd.x86_64: E: zero-length /usr/lib64/arc/jobplugin.apd nordugrid-arc-gridftpd.x86_64: W: no-manual-page-for-binary gridftpd Each executable in standard binary directories should have a man page. nordugrid-arc-gridftpd.x86_64: W: incoherent-init-script-name gridftpd ('nordugrid-arc-gridftpd', 'nordugrid-arc-gridftpdd') 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. nordugrid-arc-hed.x86_64: W: incoherent-init-script-name arched ('nordugrid-arc-hed', 'nordugrid-arc-hedd') 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. nordugrid-arc-isis.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-java.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-plugins-globus.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. nordugrid-arc-plugins-needed.x86_64: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. I've stripped out the redundant spelling errors. So it looks like most of the problems here relate to doc/man pages and init script names. One suggestion, since as of F-15 we've switched to systemd by default, might you not want to create unit files and not provide the sysv init scripts? -- 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. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review