SUGGESTIONS HERE ARE NOT A PROPER FIX, JUST A WORKAROUND TO HELP SOME
FOLKS STUCK.
So, here's a workaround while the maintainers straighten up this package
compilation issue.
Confirmed on my end that some of the past suggestions that have worked
for me about manually running a bdb update and/or simply clearing out
the runtime data files (typically in /var/lib/ldap or /var/lib/slapd)
does NOT work for this case, so do not do this ! in this case the
package was compiled against an 'outdated' libdb, slightly different
that previous cases where the bdb simply was not updated properly. i'm
pretty sure that if you have libdb5.1.29 installed and slapd version
2.4.25* it will fail to start.
A quick fix for me then happened to be simply downgrading my libdb5.1
package. In my case:
dpkg -i /var/cache/apt/archives/libdb5.1_5.1.25-11_amd64.deb
because that version of the needed bdb (5.1.25) happened to be in my apt
cache. I would think that any minor version diff that matched
5.1_5.1.25* would probably work for those who can hunt them down through
local cache files or debian package repositories. in my case the
downgrade of libdb had no dependencies and didn't appear to cause other
major issues on my system, but my system is pretty much dedicated to slapd.
another solution MAY be to downgrade slapd itself to previous version,
but slapd in my case had more affected dependencies than libdb
downgrade. it may actually be the libdb upgrade that pulled in from my
December upgrades that is the culprit in the mismatch as the slapd folks
may have actually compiled against what was current as of the time of
their release. if this is true, i don't know if downgrading slapd would
actually fix anything, i did some initial testing here and it seemed to
fail to start even with downgrades of slapd and dependencies.
as suggested in the above comments, the proper fix is better
communication through (db_config?) digital version files or somehow
directly between slapd and libdb maintainers/devs, and i don't mean to
derail the proper fix, but maybe this can help someone stuck in a bad
situation for a few.
you may also want to put a hold on package 'libdb5.1' if you don't want
future 'apt-get upgrade's/etc to put you right back in the same
situation. if you do so, be sure to remove this hold once this bug is
fixed up.
--
Joseph M. Deming
System Administrator
MATRIX/History
415 Nat Sci Bldg
East Lansing, MI 48824
(517) 884-2472
[email protected]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
