Hmm. . . Well, I figured the failed tests may have had something to do with the larger problem, which is this:
Every time I try to run the program 'smbldap-useradd alex' I get the following message:


[EMAIL PROTECTED]:~# smbldap-useradd alex
Can't locate object method "new" via package "Net::LDAP" (perhaps you forgot to load "Net::LDAP"?) at /usr/local/sbin//smbldap_tools.pm line 175.


Even though perl-ldap appears to be installed correctly, any ideas what might be causing that? Any idea why gpg wouldn't be able to fetch the public key, is there a way that I can fix it, or some resources you could point me to that explain a bit about it? Thanks. :-)

Graham Barr wrote:


On 29 Jun 2004, at 22:28, Alex Laughlin-Dendy wrote:

who can help me with an install of perl-ldap 0.31?

I'm having two problems in the testing phase of the installation, one is the gpg signature appears to be broken, it dies with this error:

PERL_DL_NONLAZY=1 /usr/bin/perl5.8.3 "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/0-signature.....gpg: Signature made Thu Jan 1 05:44:36 2004 EST using DSA key ID 06D8C374
gpg: Can't check signature: public key not found
==> BAD/TAMPERED signature detected! <==


Looks like your gpg cannot fetch my public key. But it is there, see
http://pgp.mit.edu:11371/pks/lookup?search=0x06D8C374&op=index

#     Failed test (t/0-signature.t at line 18)
# Looks like you failed 1 tests of 1.
t/0-signature.....dubious
       Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 1
       Failed 1/1 tests, 0.00% okay


Also, all of the tests that require an ldap server are skipped, even though slapd is running. What would be causing this, and how should I fix it? Here's the output from those tests:


Running tests against a live server is a very bad idea. If you setup values in test.cfg then each test will create a server, load it, run tests, then kill the server. But there is no real requirement that you have to run these tests before installing.

Graham.

Reply via email to