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

[Torsten Landschoff]

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

Hi Steve,=20

On Mon, May 23, 2005 at 08:43:30AM -0700, Steve Langasek wrote:
=20
> Do you consider this a prerequisite for getting this fixed for sarge?
> Please keep in mind that LDBM usage in 2.2 is currently associated with an
> RC bug, #304735.  I don't think generalizing the code buys us anything for
> sarge.

I am speaking of external sources like the meta, ldap or perl backend. I
do not care that much about LDBM currently :)
=20
> > Given that we had only problems with people running ldbm I think we
> > should even enforce changing the backend during upgrade. Comments?
>=20
> I think converting should be the default, and the question should probably
> be of medium priority.  If we're worried that users should know what's
> happened, then perhaps a high-priority debconf note should be displayed
> *after* the change is made.
>=20
> Does that sound reasonable?

Makes sense.

Greetings

	Torsten

--+HP7ph2BbKc20aGI
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)

iD8DBQFCldO1dQgHtVUb5EcRAjERAJsEeypoxNHNBsq0v6kF2QjQMvfDUgCePy1y
j1GxaROcxm7fmjSQ4hvvC+Y=
=OBwD
-----END PGP SIGNATURE-----

--+HP7ph2BbKc20aGI--