Your message dated Fri, 21 Dec 2007 00:52:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line All fix_ldif code has now been dropped
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.2.23-3
Severity: minor
Testing with an LDIF that I knew would require the use of fix_ldif, I
got the following curious error:
Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.1.30-3... done.
Updating config access directives... done.
Moving old database directories to /var/backups:
- directory dc=netexpress,dc=net... done.
Loading from /var/backups/slapd-2.1.30-3:
- directory dc=netexpress,dc=net... fixing, failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
slapadd: could not parse entry (line=326)
The error message being printed was surprising, since that line
pointed to the dn that I knew needed fixing, and that fix_ldif should
have fixed correctly. It turns out that fix_ldif *did* in fact fix it,
but an unrelated bug in fix_ldif caused a failure later on:
slapadd: dn="uid=mumble,ou=People,dc=netexpress,dc=net"
(line=315300): (65) object class 'posixAccount' requires attribute 'cn'
I've fixed this error in fix_ldif, but I'm confused why I had to rerun
fix_ldif by hand to get the error reported to me. Seems to be a bug in
capture_diagnostics/release_diagnostics?
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages slapd depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii debconf 1.4.48 Debian configuration management sy
ii fileutils 5.2.1-2 The GNU file management utilities
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [
ii libiodbc2 3.52.2-3 iODBC Driver Manager
ii libldap-2.2-7 2.2.23-3 OpenLDAP libraries
ii libltdl3 1.5.6-6 A system independent dlopen wrappe
ii libperl5.8 5.8.4-8 Shared Perl library
ii libsasl2 2.1.19-1.5 Authentication abstraction library
ii libslp1 1.0.11a-1 OpenSLP libraries
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii perl [libmime-base64-perl] 5.8.4-8 Larry Wall's Practical Extraction
ii psmisc 21.6-1 Utilities that use the proc filesy
-- debconf information excluded
--- End Message ---
--- Begin Message ---
It's been years since strict schema checking was added and it's always
enforced for the version released with etch. It's unlikely that anyone
will still be trying to upgrade from an LDAP database that doesn't pass
schema checking and for which fix_ldif would be useful.
We're therefore dropping all fix_ldif code from the slapd package and
closing any remaining bugs open against it.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--- End Message ---
