#148 Can't locate Bastille/API/HPSpecific.pm in @INC

[paul barnes]

Thank you for the response on the previous 'item'.

Same install, on the same machine.

I symlinked /usr/lib64/Bastille on /usr/lib/Bastille and relauch the command, it is a little better but i have now the following pb (see below)
Thank you in advance if you have any hint!

dhcp0421:/ # bastille -x
NOTE: Using Tk user interface module.
NOTE: Only displaying questions relevant to the current configuration.
Can't locate Bastille/API/HPSpecific.pm in @INC (@INC contains: /usr/lib /usr/lib/perl5/site_perl//5.8.8/i586-linux-thread-multi /usr/lib/perl5/site_perl//5.8.8 /usr/lib/perl5/site_perl/ /usr/lib/Bastille /opt/sec_mgmt/bastille/lib /opt/sec_mgmt/bastille/lib/API /usr/lib/perl5/site_perl/5.8.8/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/5.8.8/i586-linux-thread-multi /usr/lib/perl5/5.8.8 /usr/lib/perl5/vendor_perl/5.8.8/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl) at /usr/lib/Bastille/IOLoader.pm line 8.
BEGIN failed--compilation aborted at /usr/lib/Bastille/IOLoader.pm line 8.
Compilation failed in require at /usr/sbin/InteractiveBastille line 414.
dhcp0421:/ # ls -als /opt/sec_mgmt/bastille/lib /opt/sec_mgmt/bastille/lib/API
/bin/ls: /opt/sec_mgmt/bastille/lib: No such file or directory
/bin/ls: /opt/sec_mgmt/bastille/lib/API: No such file or directory

[Jim Keir]

Same here. Many of the source modules refer to 'API/HPSpecific.pm', 'API/FileContent.pm' and others. However, neither the RPM nor the tarball contain a folder called 'API', or any of the modules which are supposed to be under it.

The only other available release, from 2005, doesn't refer to these modules.

[Bent]

I was able to get the files from the SCM repository:
http://bastille-linux.cvs.sourceforge.net/viewvc/bastille-linux/dev/working_tree/Bastille/Bastille/API/

Why the files aren't in the tarball or the RPM is anyone's guess...

Hopefully, this helps.

[Nobody/Anonymous]

I have the same problem on Centos (March 2009). Both the rpm and the source package lack an 'API' folder.