Your message dated Sat, 15 Jul 2006 22:52:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#255993: failed when setup slapd
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: slapd
Version: 2.1.23-1
Severity: normal
when I run apt-get install slapd on one of my machine using testing,
I got this error message:
Setting up slapd (2.1.23-1) ...
Creating initial LDAP directory... slapadd: relocation error:
/usr/lib/ldap/back_bdb.so: undefined symbol: db_version_4001
dpkg: error processing slapd (--configure):
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
slapd
When I try start slapd manually, I also got:
# /usr/sbin/slapd
/usr/sbin/slapd: relocation error: /usr/lib/ldap/back_bdb.so: undefined
symbol: db_version_4001
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-grsec
Locale: LANG=C, LC_CTYPE=C
Versions of packages slapd depends on:
ii coreutils [fileutils] 5.0.91-2 The GNU core utilities
ii debconf 1.4.28 Debian configuration management sy
ii fileutils 5.0.91-2 The GNU file management utilities
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libdb4.1 4.1.25-17 Berkeley v4.1 Database Libraries [
ii libgcrypt1 1.1.12-4 LGPL Crypto library - runtime libr
ii libgnutls7 0.8.12-5 GNU TLS library - runtime library
ii libiodbc2 3.51.2-2 iODBC Driver Manager
ii libldap2 2.1.23-1 OpenLDAP libraries
ii libltdl3 1.5.6-1 A system independent dlopen wrappe
ii libsasl2 2.1.18-4.1 Authentication abstraction library
ii libslp1 1.0.11-7 OpenSLP libraries
ii libtasn1-0 0.1.2-2 Manage ASN.1 structures (runtime)
ii libwrap0 7.6.dbs-4 Wietse Venema's TCP wrappers libra
ii perl [libmime-base64-perl] 5.8.3-3 Larry Wall's Practical Extraction
ii psmisc 21.5-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.1.1-3 compression library - runtime
-- debconf information:
slapd/fix_directory: true
* shared/organization: coe.psu.ac.th
slapd/upgrade_slapcat_failure:
* slapd/allow_ldap_v2: false
slapd/no_configuration: false
slapd/suffix_change: false
slapd/autoconf_modules: true
* slapd/domain: coe.psu.ac.th
slapd/password_mismatch:
slapd/invalid_config: true
slapd/upgrade_slapadd_failure:
slapd/purge_database:
slapd/admin:
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
This bug is rather old and doesn't apply to Sarge anymore. I can't
reproduce this behaviour with 2.2.23-8 or 2.3.24-1. Closing bug report.
Regards,
Matthijs Mohlmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEuVWY2n1ROIkXqbARAtW2AKCwQBwStpx/62vtZ7bEgi9LQzFzfwCgoU5u
7D3HQOKplbFYUQIup4z1GvI=
=CmrR
-----END PGP SIGNATURE-----
--- End Message ---
