[Pkg-openldap-devel] Recommendation for ldbm to bdb

[Torsten Landschoff]

--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Steve,=20

On Fri, May 27, 2005 at 03:16:53PM -0700, Steve Langasek wrote:
> > I am speaking of external sources like the meta, ldap or perl backend. I
> > do not care that much about LDBM currently :)
>=20
> Well, LDBM is the only case that needs to be handled in the *current*
> maintainer scripts for sarge, because it's the only one that seems to be
> irredeemably broken.

Sorry, wrong context, I was referring to the other patch for running
db_recover. And the comment was flawed anyway to just forget about it.

> > > I think converting should be the default, and the question should pro=
bably
> > > be of medium priority.  If we're worried that users should know what's
> > > happened, then perhaps a high-priority debconf note should be display=
ed
> > > *after* the change is made.
>=20
> > > Does that sound reasonable?
>=20
> > Makes sense.
>=20
> Ok.  How's the patching going?  Do you think you would have the necessary
> fixes committed this weekend, and could upload by Monday?  Otherwise, we'=
re
> cutting things very close in terms of the release schedule; I'd hate for =
the
> release to be held up for slapd alone. :)  (I'd also hate to be scrambling
> to help you get this done at the last minute. :)

I think I can upload a patch for changing LDBM to BDB up to monday. I
committed already that db_recover thingy but I am not sure if I want to
release it like it is. I think we should at least check if another slapd
is running before running db_recover.

Greetings

	Torsten

--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCmXeodQgHtVUb5EcRAtvwAJ9IEjc0LGJQjsDK2FoZgkhI3ZZazACeNu2U
IiAgaUz1mBYMoJ8CdEGH8PM=
=OBPe
-----END PGP SIGNATURE-----

--3MwIy2ne0vdjdPXF--