Your message dated Tue, 21 Feb 2006 19:28:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line slapd: fails upgrade from pre3 to pre4 (openldap2.2)
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-0.pre4
Severity: normal
Tags: experimental

Fails to upgrade from 2.2.23-0.pre3 to 2.2.23-0.pre4
Selecting previously deselected package libldap-2.2-7.
(Reading database ... 27875 files and directories currently installed.)
Unpacking libldap-2.2-7 (from .../libldap-2.2-7_2.2.23-0.pre4_i386.deb) ...
dpkg: error processing /usr/src/slapd//libldap-2.2-7_2.2.23-0.pre4_i386.deb 
(--unpack):
 trying to overwrite `/usr/lib/liblber-2.2.so.7.0.16', which is also in package 
libldap2.2
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Preparing to replace ldap-utils 2.2.23-0.pre3 (using 
.../ldap-utils_2.2.23-0.pre4_i386.deb) ...
Unpacking replacement ldap-utils ...
Preparing to replace slapd 2.2.23-0.pre3 (using 
...//slapd_2.2.23-0.pre4_i386.deb) ...
Stopping OpenLDAP: slapd.
Unpacking replacement slapd ...
Replacing files in old package libldap2 ...
Errors were encountered while processing:
 /usr/src/slapd//libldap-2.2-7_2.2.23-0.pre4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Probably forgotten Replaces.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages slapd depends on:
ii  coreutils [fileutils]      5.2.1-2       The GNU core utilities
ii  debconf                    1.4.30.11     Debian configuration management sy
ii  fileutils                  5.2.1-2       The GNU file management utilities 
ii  libc6                      2.3.2.ds1-20  GNU C Library: Shared libraries an
ii  libdb4.3                   4.3.27-1      Berkeley v4.3 Database Libraries [
ii  libiodbc2                  3.52.2-3      iODBC Driver Manager
ii  libldap-2.2-7              2.2.23-0.pre4 OpenLDAP libraries
ii  libltdl3                   1.5.6-4       A system independent dlopen wrappe
ii  libperl5.8                 5.8.4-6       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-2      SSL shared libraries
ii  libwrap0                   7.6.dbs-6     Wietse Venema's TCP wrappers libra
ii  perl [libmime-base64-perl] 5.8.4-6       Larry Wall's Practical Extraction 
ii  psmisc                     21.5-1        Utilities that use the proc filesy

-- debconf information:
  slapd/password_mismatch:
  slapd/fix_directory: true
  slapd/invalid_config: true
* shared/organization: nodomain
  slapd/upgrade_slapcat_failure:
  slapd/upgrade_slapadd_failure:
  slapd/backend: BDB
* slapd/allow_ldap_v2: true
  slapd/no_configuration: false
  slapd/move_old_database: true
  slapd/suffix_change: false
  slapd/slave_databases_require_updateref:
  slapd/autoconf_modules: true
  slapd/purge_database: false
  slapd/admin:
* slapd/domain: nodomain


--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This bug can be closed now. We don't have a pre3 or pre4 in experimental
and or unstable/testing.

Regards,

Matthijs Mohlmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD+1vj2n1ROIkXqbARAuKAAJ9vhUhbC+IcHxGEbof4bMVX5c9wrgCcDvam
N1L0BPEdO5omsa7srbyGPgk=
=SLpl
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to