Rebuild libsasl2 against libdb4.1

[Debian Bug Importer]

Automatically imported from Debian bug report #187043 http://bugs.debian.org/187043

[Henrique de Moraes Holschuh (hmh)]

On Mon, 31 Mar 2003, Stephen Frost wrote:
> Please recompile libsasl2 against libdb4.1, it's been out and available

Please don't. libdb3.2 is far more stable, and SASL does NOT use anything
in the new libdb releases at all... Also, libdb3.2 has a smaller memory
footprint.

Unless Stephen has some very compeling reasons to switch? Stephen?

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[Stephen Frost (sfrost)]

* Henrique de Moraes Holschuh (<email address hidden>) wrote:
> On Mon, 31 Mar 2003, Stephen Frost wrote:
> > Please recompile libsasl2 against libdb4.1, it's been out and available
>
> Please don't. libdb3.2 is far more stable, and SASL does NOT use anything
> in the new libdb releases at all... Also, libdb3.2 has a smaller memory
> footprint.
>
> Unless Stephen has some very compeling reasons to switch? Stephen?

Recent versions of OpenLDAP 2.1 require libdb4.1 and while libdb may be
able to handle multiple versions being linked into one process (I think
it can anyway) I'd prefer to avoid it anyway unless there's good reason
for it. I've yet to see any problem with libdb4.1 and OpenLDAP 2.1
though I don't do very stressful things. Obviously if there are
specific things you know about libdb4.1 it'd be great to have bugs
against them opened in the BTS...

 Stephen

[Henrique de Moraes Holschuh (hmh)]

On Mon, 31 Mar 2003, Stephen Frost wrote:
> * Henrique de Moraes Holschuh (<email address hidden>) wrote:
> > On Mon, 31 Mar 2003, Stephen Frost wrote:
> > > Please recompile libsasl2 against libdb4.1, it's been out and available
> >
> > Please don't. libdb3.2 is far more stable, and SASL does NOT use anything
> > in the new libdb releases at all... Also, libdb3.2 has a smaller memory
> > footprint.
> >
> > Unless Stephen has some very compeling reasons to switch? Stephen?
>
> Recent versions of OpenLDAP 2.1 require libdb4.1 and while libdb may be
> able to handle multiple versions being linked into one process (I think

It has to, otherwise SASL would make NSS segfault, and thus crash the entire
system.

> it can anyway) I'd prefer to avoid it anyway unless there's good reason
> for it. I've yet to see any problem with libdb4.1 and OpenLDAP 2.1

Well, libdb4.1 and Cyrus teached me not to trust libdb at all. People
complain of database errors, corruption, and lock contention...

Thus, I am holding cyrus back from libdb4.1 since we don't use any of the
new features anyway. Maybe openldap does, but SASL doesn't either. Nor does
sendmail, postfix, and most of everything else...

But we absolutely *have* to use symbol versioning and allow just about every
libdb under the sun linked to the same executable, or hell breaks loose, so
I am not very concerned by SASL using one DB, and LDAP using another...

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[Stephen Frost (sfrost)]

* Henrique de Moraes Holschuh (<email address hidden>) wrote:
> On Mon, 31 Mar 2003, Stephen Frost wrote:
> > it can anyway) I'd prefer to avoid it anyway unless there's good reason
> > for it. I've yet to see any problem with libdb4.1 and OpenLDAP 2.1
>
> Well, libdb4.1 and Cyrus teached me not to trust libdb at all. People
> complain of database errors, corruption, and lock contention...

I hope these reports have some teeth to them and that work is being done
to fix the problems. Perhaps I should go join the libdb lists, assuming
there are any.

> Thus, I am holding cyrus back from libdb4.1 since we don't use any of the
> new features anyway. Maybe openldap does, but SASL doesn't either. Nor does
> sendmail, postfix, and most of everything else...

I'm not sure that OpenLDAP actually uses the new features but I do know
that they had reports of database problems under 4.0 and so put in a
requirement of >= 4.1 in their configure scripts. Of course, it's
certainly possible they do use the new features.

> But we absolutely *have* to use symbol versioning and allow just about every
> libdb under the sun linked to the same executable, or hell breaks loose, so
> I am not very concerned by SASL using one DB, and LDAP using another...

I'm all for symbol versioning. Linking new packages against old libs
when new ones are available I tend to frown on.

 Stephen

[Frank Lichtenheld (djpig)]

severity 187043 serious
merge 187043 258607

[Frank Lichtenheld (djpig)]

reassign 187043 cyrus-sasl2
merge 187043 258607

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #187043 http://bugs.debian.org/187043

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 31 Mar 2003 14:23:56 -0500
From: Stephen Frost <email address hidden>
To: <email address hidden>
Subject: Rebuild libsasl2 against libdb4.1

--uWKIjLx9zRJNHvcs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: libsasl2-modules
Version: 2.1.12-1
Severity: Wishlist

Please recompile libsasl2 against libdb4.1, it's been out and available
for a while now.. (I had thought you were going to use it when you
packaged 2.1.12...? Was there a problem with it?)

 Thanks,

  Stephen

--uWKIjLx9zRJNHvcs
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE+iJXMrzgMPqB3kigRAiFFAJ49Ro2PpkS2Ma5JEI0VQpLOPaAuRgCfW0Ge
6RHPSaf+Bg7KkMiNpnhVdsQ=
=Xij8
-----END PGP SIGNATURE-----

--uWKIjLx9zRJNHvcs--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 31 Mar 2003 16:49:34 -0300
From: Henrique de Moraes Holschuh <email address hidden>
To: Stephen Frost <email address hidden>, <email address hidden>
Subject: Re: Bug#187043: Rebuild libsasl2 against libdb4.1

On Mon, 31 Mar 2003, Stephen Frost wrote:
> Please recompile libsasl2 against libdb4.1, it's been out and available

Please don't. libdb3.2 is far more stable, and SASL does NOT use anything
in the new libdb releases at all... Also, libdb3.2 has a smaller memory
footprint.

Unless Stephen has some very compeling reasons to switch? Stephen?

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 31 Mar 2003 14:56:20 -0500
From: Stephen Frost <email address hidden>
To: Henrique de Moraes Holschuh <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#187043: Rebuild libsasl2 against libdb4.1

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

* Henrique de Moraes Holschuh (<email address hidden>) wrote:
> On Mon, 31 Mar 2003, Stephen Frost wrote:
> > Please recompile libsasl2 against libdb4.1, it's been out and available
>=20
> Please don't. libdb3.2 is far more stable, and SASL does NOT use anything
> in the new libdb releases at all... Also, libdb3.2 has a smaller memory
> footprint.
>=20
> Unless Stephen has some very compeling reasons to switch? Stephen?

Recent versions of OpenLDAP 2.1 require libdb4.1 and while libdb may be
able to handle multiple versions being linked into one process (I think
it can anyway) I'd prefer to avoid it anyway unless there's good reason
for it. I've yet to see any problem with libdb4.1 and OpenLDAP 2.1
though I don't do very stressful things. Obviously if there are
specific things you know about libdb4.1 it'd be great to have bugs
against them opened in the BTS...

 Stephen

--eaV5P3cR6+S+P6qN
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE+iJ1jrzgMPqB3kigRApASAJ0dOcBV/jm/S9ZDQ2MfIJIdN0yVIwCcDPN2
2Q7IwdlqXGosghbIDTEBUbM=
=YFbj
-----END PGP SIGNATURE-----

--eaV5P3cR6+S+P6qN--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 31 Mar 2003 17:27:19 -0300
From: Henrique de Moraes Holschuh <email address hidden>
To: Stephen Frost <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#187043: Rebuild libsasl2 against libdb4.1

On Mon, 31 Mar 2003, Stephen Frost wrote:
> * Henrique de Moraes Holschuh (<email address hidden>) wrote:
> > On Mon, 31 Mar 2003, Stephen Frost wrote:
> > > Please recompile libsasl2 against libdb4.1, it's been out and available
> >
> > Please don't. libdb3.2 is far more stable, and SASL does NOT use anything
> > in the new libdb releases at all... Also, libdb3.2 has a smaller memory
> > footprint.
> >
> > Unless Stephen has some very compeling reasons to switch? Stephen?
>
> Recent versions of OpenLDAP 2.1 require libdb4.1 and while libdb may be
> able to handle multiple versions being linked into one process (I think

It has to, otherwise SASL would make NSS segfault, and thus crash the entire
system.

> it can anyway) I'd prefer to avoid it anyway unless there's good reason
> for it. I've yet to see any problem with libdb4.1 and OpenLDAP 2.1

Well, libdb4.1 and Cyrus teached me not to trust libdb at all. People
complain of database errors, corruption, and lock contention...

Thus, I am holding cyrus back from libdb4.1 since we don't use any of the
new features anyway. Maybe openldap does, but SASL doesn't either. Nor does
sendmail, postfix, and most of everything else...

But we absolutely *have* to use symbol versioning and allow just about every
libdb under the sun linked to the same executable, or hell breaks loose, so
I am not very concerned by SASL using one DB, and LDAP using another...

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 31 Mar 2003 16:09:33 -0500
From: Stephen Frost <email address hidden>
To: Henrique de Moraes Holschuh <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#187043: Rebuild libsasl2 against libdb4.1

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

* Henrique de Moraes Holschuh (<email address hidden>) wrote:
> On Mon, 31 Mar 2003, Stephen Frost wrote:
> > it can anyway) I'd prefer to avoid it anyway unless there's good reason
> > for it. I've yet to see any problem with libdb4.1 and OpenLDAP 2.1
>=20
> Well, libdb4.1 and Cyrus teached me not to trust libdb at all. People
> complain of database errors, corruption, and lock contention...

I hope these reports have some teeth to them and that work is being done
to fix the problems. Perhaps I should go join the libdb lists, assuming
there are any.

> Thus, I am holding cyrus back from libdb4.1 since we don't use any of the
> new features anyway. Maybe openldap does, but SASL doesn't either. Nor d=
oes
> sendmail, postfix, and most of everything else...

I'm not sure that OpenLDAP actually uses the new features but I do know
that they had reports of database problems under 4.0 and so put in a
requirement of >=3D 4.1 in their configure scripts. Of course, it's
certainly possible they do use the new features.

> But we absolutely *have* to use symbol versioning and allow just about ev=
ery
> libdb under the sun linked to the same executable, or hell breaks loose, =
so
> I am not very concerned by SASL using one DB, and LDAP using another...

I'm all for symbol versioning. Linking new packages against old libs
when new ones are available I tend to frown on.

 Stephen

--6ti9qQdT93fLKTkp
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE+iK6NrzgMPqB3kigRAraUAJ9n7iHksDLkgvN4L53OfZ1K8cWasgCeJvqw
EJoLJ/zyUUyKSESlA5qb58Q=
=Eu+c
-----END PGP SIGNATURE-----

--6ti9qQdT93fLKTkp--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 21 Jul 2004 13:00:06 +0200
From: Frank Lichtenheld <email address hidden>
To: <email address hidden>
Subject: severity of 187043 is serious, merging 187043 258607

severity 187043 serious
merge 187043 258607

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 21 Jul 2004 13:26:34 +0200
From: Frank Lichtenheld <email address hidden>
To: <email address hidden>
Subject: reassign 187043 to cyrus-sasl2, merging 187043 258607

reassign 187043 cyrus-sasl2
merge 187043 258607

[Debian Bug Importer (debzilla)]

*** Bug 6819 has been marked as a duplicate of this bug. ***

[Dima Barsky (dima)]

Source: cyrus-sasl2
Source-Version: 2.1.19-1

We believe that the bug you reported is fixed in the latest version of
cyrus-sasl2, which is due to be installed in the Debian FTP archive:

cyrus-sasl2_2.1.19-1.diff.gz
  to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.19-1.diff.gz
cyrus-sasl2_2.1.19-1.dsc
  to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.19-1.dsc
cyrus-sasl2_2.1.19.orig.tar.gz
  to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.19.orig.tar.gz
libsasl2-dev_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.19-1_i386.deb
libsasl2-modules-gssapi-heimdal_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.19-1_i386.deb
libsasl2-modules-kerberos-heimdal_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules-kerberos-heimdal_2.1.19-1_i386.deb
libsasl2-modules-sql_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.19-1_i386.deb
libsasl2-modules_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.19-1_i386.deb
libsasl2_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2_2.1.19-1_i386.deb
sasl2-bin_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.19-1_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dima Barsky <email address hidden> (supplier of updated cyrus-sasl2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 1 Aug 2004 15:30:24 +0100
Source: cyrus-sasl2
Binary: libsasl2 libsasl2-modules-sql sasl2-bin libsasl2-modules libsasl2-dev libsasl2-modules-gssapi-heimdal libsasl2-modules-kerberos-heimdal
Architecture: source i386
Version: 2.1.19-1
Distribution: unstable
Urgency: medium
Maintainer: Dima Barsky <email address hidden>
Changed-By: Dima Barsky <email address hidden>
Description:
 libsasl2 - Authentication abstraction library
 libsasl2-dev - Development files for authentication abstraction library
 libsasl2-modules - Pluggable Authentication Modules for SASL
 libsasl2-modules-gssapi-heimdal - Pluggable Authentication Modules for SASL
 libsasl2-modules-kerberos-heimdal - Pluggable Authentication Modules for SASL
 libsasl2-modules-sql - Pluggable Authentication Modules for SASL
 sasl2-bin - Programs for manipulating the SASL users database
Closes: 187043 253894 254454 254818 258607 259503 259658 260562
Changes:
 cyrus-sasl2 (2.1.19-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #259503, #259658)
   * Acknowledge the last NMU (closes: #254818)
   * Build against libdb4.2 (closes: #253894, #187043, #258607, #260562)
   * Fixed the path to saslauthd.conf in the saslauthd
     man page (Closes: #254454)
Files:
 0eced22cd6d4f08e86380ab1b2def3b7 1053 devel important cyrus-sasl2_2.1.19-1.dsc
 670f9a0c0a99cf09d679cd5c859a3715 1531667 devel important...

[Thom May (thombot)]

Lamont has fixed this for us as per bug6819 - resolving as fixed.

[Matt Zimmerman (mdz)]

As noted in #59, we still need to autoconvert the databases; LaMont's solution
was a temporary one

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sun, 01 Aug 2004 11:02:07 -0400
From: Dima Barsky <email address hidden>
To: <email address hidden>
Subject: Bug#187043: fixed in cyrus-sasl2 2.1.19-1

Source: cyrus-sasl2
Source-Version: 2.1.19-1

We believe that the bug you reported is fixed in the latest version of
cyrus-sasl2, which is due to be installed in the Debian FTP archive:

cyrus-sasl2_2.1.19-1.diff.gz
  to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.19-1.diff.gz
cyrus-sasl2_2.1.19-1.dsc
  to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.19-1.dsc
cyrus-sasl2_2.1.19.orig.tar.gz
  to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.19.orig.tar.gz
libsasl2-dev_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.19-1_i386.deb
libsasl2-modules-gssapi-heimdal_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.19-1_i386.deb
libsasl2-modules-kerberos-heimdal_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules-kerberos-heimdal_2.1.19-1_i386.deb
libsasl2-modules-sql_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.19-1_i386.deb
libsasl2-modules_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.19-1_i386.deb
libsasl2_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/libsasl2_2.1.19-1_i386.deb
sasl2-bin_2.1.19-1_i386.deb
  to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.19-1_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dima Barsky <email address hidden> (supplier of updated cyrus-sasl2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 1 Aug 2004 15:30:24 +0100
Source: cyrus-sasl2
Binary: libsasl2 libsasl2-modules-sql sasl2-bin libsasl2-modules libsasl2-dev libsasl2-modules-gssapi-heimdal libsasl2-modules-kerberos-heimdal
Architecture: source i386
Version: 2.1.19-1
Distribution: unstable
Urgency: medium
Maintainer: Dima Barsky <email address hidden>
Changed-By: Dima Barsky <email address hidden>
Description:
 libsasl2 - Authentication abstraction library
 libsasl2-dev - Development files for authentication abstraction library
 libsasl2-modules - Pluggable Authentication Modules for SASL
 libsasl2-modules-gssapi-heimdal - Pluggable Authentication Modules for SASL
 libsasl2-modules-kerberos-heimdal - Pluggable Authentication Modules for SASL
 libsasl2-modules-sql - Pluggable Authentication Modules for SASL
 sasl2-bin - Programs for manipulating the SASL users database
Closes: 187043 253894 254454 254818 258607 259503 259658 260562
Changes:
 cyrus-sasl2 (2.1.19-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #259503, #259658)
   * Acknowledge the last NMU (closes: #254818)
   * Build against libdb4.2 (closes: #253894, #187043, #258607, #260562)
   * Fixed the path to...

[Matt Zimmerman (mdz)]

I'm not entirely sure that we want 2.1.19; it seems to have a lot of changes
spanning several months. Please look into backporting the libdb transition bits

[Matt Zimmerman (mdz)]

What's the status of this bug? Did the maintainer implement a proper transition
(which we would want to merge), or punt like we did for Warty?

[Matt Zimmerman (mdz)]

Hello?

[LaMont Jones (lamont)]

Debian left conversion as an exercise for the user (there is a converter program
there, from before 2.1.18-4.1)