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

Steve Langasek vorlon@debian.org
Fri, 27 May 2005 15:16:53 -0700


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

On Thu, May 26, 2005 at 03:48:37PM +0200, Torsten Landschoff wrote:
> On Mon, May 23, 2005 at 08:43:30AM -0700, Steve Langasek wrote:

> > 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 :)

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.

> > > 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 proba=
bly
> > 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.

> > Does that sound reasonable?

> Makes sense.

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. :)

Thanks,
--=20
Steve Langasek
postmodern programmer

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

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

iD8DBQFCl5xUKN6ufymYLloRAvE1AJ9lz6VmnM1oSB4KcCbpbuhp9GOJ8gCgwd98
YUQEElL2YI2RUTz2ahveCmg=
=8T99
-----END PGP SIGNATURE-----

--RD6GsZsdEJvsf78O--