579102 – sys-libs/ldb should force a rebuild of net-fs/samba when it is updated

Bug 579102 - sys-libs/ldb should force a rebuild of net-fs/samba when it is updated

Summary: sys-libs/ldb should force a rebuild of net-fs/samba when it is updated

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo's SAMBA Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-04-05 17:28 UTC by Alan Hodgson
Modified:	2024-04-17 16:52 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alan Hodgson 2016-04-05 17:28:29 UTC

sys-libs/ldb updated for me yesterday and afterwards samba 4.2.9 wouldn't restart. Errors like:

pr  5 09:56:48 achilles samba[7743]: Copyright Andrew Tridgell and the Samba Team 1992-2014
Apr  5 09:56:48 achilles samba[7743]: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.1.26 module_version=1.1.24
Apr  5 09:56:48 achilles samba[7743]: ldb: failed to initialise module /usr/lib64/samba/ldb/acl.so : Unavailable
Apr  5 09:56:48 achilles samba[7743]: ldb: Unable to find backend for '/var/lib/samba/private/privilege.ldb' - do you need to set LDB_MODULES_PATH?

.. etc.

Rebuilding samba fixed it.

Reproducible: Always

Steps to Reproduce:
1. update ldb
2. restart samba
3. samba fails
Actual Results:  
Samba no longer working after restart.

Expected Results:  
Samba works normally.

Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev

2016-04-05 17:35:33 UTC

Alternatively, sys-libs/ldb needs to use symbol versioning to retian the proper api calls for older versions.

Comment 2 Ben Kohler gentoo-dev

2024-04-17 16:49:33 UTC

Is this still an issue? Samba seems to lock down the ldb version pretty specifically, does this actually break between (eg) ldb-2.5.2 & ldb-2.5.3?