BDII status in EPEL

Status of BDII packages in EPEL

Package name	EPEL status	Comments
bdii	v. 5.2.22-1
glue-schema	v. 2.0.10-1
glite-info-provider-service	pending review	956243 Owned by Laurence, to be reviewed by Maria
glue-validator	v.1.0.2-3
glue-validator-cron	no	This should be a sub package of the validator
glite-info-provider-ldap	pending review	956210 Owned by Laurence, to be reviewed by Maria
glite-yaim-bdii	no	yaim not to be released in EPEL.
bdii-config-site	pending review	956204
glite-info-site	pending review	956249
glite-info-static	pending review	956250
bdii-config-top	pending review	956205
glite-info-plugin-fcr	pending review	956207
glite-info-update-endpoints	pending review	956255
glite-info-plugin-delayed-delete-status	pending review	996497
emi-resource-information-service	no	metapackages are not to be released in EPEL.
emi-bdii-site	no	metapackages are not to be released in EPEL.
emi-bdii-top	no	metapackages are not to be released in EPEL.
nagios-plugins-bdii	v. 1.0.14-1

rpmlint accepted errors for packages released in EPEL

The following errors are false positives for BDII related packages already released in EPEL and accepted by EPEL reviewers. The table below explains why:

package name	rpmlint error	description	comments
bdii	non-readable /etc/bdii/bdii-top-slapd.conf 0640	The file can't be read by everybody. If this is expected (for security reasons), contact your rpmlint distributor to get it added to the list of exceptions for your distro (or add it to your local configuration if you installed rpmlint from the source tarball).	This file contains a password and hence should not be readable for every one.
	non-readable /etc/bdii/bdii-slapd.conf 0640	Same as above.	This file contains a password and hence should not be readable for every one.
	incoherent-subsys /etc/rc.d/init.d/bdii bdii-update	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.	The bdii init.d script creates two process, slapd and bdii-update. Thi lock is for the update process.
	incoherent-subsys /etc/rc.d/init.d/bdii bdii-slapd	Same as above.	The bdii init.d script creates two process, slapd and bdii-update. This lock is for the slapd process.
glue-schema	no-dependency-on locales-doc		This error will be fixed in a future update. See BUG #96598
glue-validator	no-dependency-on python-base 2.4		This error will be fixed in a future update. See BUG #96598

EPEL bugs

Bugzilla bug	Description	Comments	Associated Savannah bug
843594	init script fails	Problems with dependencies on lsb-base and lsb-release packages	None yet

-- MariaALANDESPRADILLO - 06-Aug-2012