All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Armin Kuster <akuster808@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-security][PATCH 2/5] libldb: work around samba libldb packaging issues
Date: Fri, 29 Mar 2019 14:58:07 +0200	[thread overview]
Message-ID: <20190329125807.GA11351@localhost> (raw)
In-Reply-To: <20190329065014.GA26574@localhost>

On Fri, Mar 29, 2019 at 08:50:14AM +0200, Adrian Bunk wrote:
> On Thu, Mar 28, 2019 at 10:28:18PM -0700, Armin Kuster wrote:
> > Samba and libldb overlap in a few places. This is the simplest fix for
> > now.
> 
> Adding a quick hack for interaction problems between two packages
> that are both in meta-openembedded by adding a .bbappend in 
> meta-security creates a technical debt while not even helping
> users who are not using meta-security.
> 
> The proper solution is likely to make samba use the external libldb 
> instead of an internal copy.
>...

commit a001e465293b36c03d4ca4500857fe0a67d13e20
Date:   Fri Jul 27 14:09:10 2018 -0700

    samba: Update to 4.8.3
    
    LDB 1.4.0 breaks Samba < 4.9 therefore use internal version


So the root cause is that last summer LDB in meta-openembedded was 
updated to a version not compatible with with the Samba version in 
meta-openembedded.

As workaround Samba was changed to use the internal version
of the library.

What is now proposed is a workaround to fix a regression caused
by the first workaround.

The best way forward would be to upgrade Samba to 4.9 or 4.10 and
use the external LDB again.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-03-29 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29  5:28 [meta-security][PATCH 1/5] Revert "sssd: fix libcrypto version used" Armin Kuster
2019-03-29  5:28 ` [meta-security][PATCH 2/5] libldb: work around samba libldb packaging issues Armin Kuster
2019-03-29  6:50   ` Adrian Bunk
2019-03-29 12:58     ` Adrian Bunk [this message]
2019-03-29 17:45     ` akuster
2019-03-29  5:28 ` [meta-security][PATCH 3/5] sssd: fix a few runtime issues Armin Kuster
2019-03-29  6:51   ` Adrian Bunk
2019-03-29 17:45     ` akuster
2019-03-29  5:28 ` [meta-security][PATCH 4/5] sssd: update to 1.16.4 Armin Kuster
2019-03-29  7:10   ` Adrian Bunk
2019-03-29 17:46     ` akuster
2019-03-29  5:28 ` [meta-security][PATCH 5/5] sssd: Add basic runtime test Armin Kuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190329125807.GA11351@localhost \
    --to=bunk@stusta.de \
    --cc=akuster808@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.