From: Changqing Li <changqing.li@windriver.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/6] Upgrade 5 packages build with waf
Date: Mon, 1 Jul 2019 10:29:14 +0800 [thread overview]
Message-ID: <2d0ef380-ec48-eadc-a4e0-84ddb90ac254@windriver.com> (raw)
In-Reply-To: <20190628094332.GA18526@localhost>
On 6/28/19 5:43 PM, Adrian Bunk wrote:
> On Fri, Jun 28, 2019 at 09:48:04AM +0800, changqing.li@windriver.com wrote:
>> ...
>> Changqing Li (6):
>> ...
>> libldb: upgrade 1.4.1 -> 1.6.3
>> ...
>> samba: upgrade 4.8.12 -> 4.10.5
>> ...
> It was a mistake that required workarounds in both libldb and samba
> when libldb was upgraded to 1.4.1 (which doesn't work with samba 4.8).
>
> Now that samba gets upgraded, all these workarounds should be removed
> and samba should use the external libldb again.
>
> For samba 4.10 this also means that libldb has to be upgraded to 1.5,
> not to 1.6.
>
> cu
> Adrian
Thanks, I will check this.
>
--
BRs
Sandy(Li Changqing)
prev parent reply other threads:[~2019-07-01 2:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 1:48 [PATCH 0/6] Upgrade 5 packages build with waf changqing.li
2019-06-28 1:48 ` [meta-networking][PATCH 1/6] waf-samba: switch to python3 changqing.li
2019-06-28 1:48 ` [meta-networking][PATCH 2/6] libldb: upgrade 1.4.1 -> 1.6.3 changqing.li
2019-06-28 1:48 ` [meta-networking][PATCH 3/6] libtevent: upgrade 0.9.37 -> 0.10.0 changqing.li
2019-06-28 1:48 ` [meta-networking][PATCH 4/6] libtdb: upgrade 1.3.17 -> 1.4.0 changqing.li
2019-06-28 1:48 ` [meta-networking][PATCH 5/6] libtalloc: upgrade 2.1.14 -> 2.2.0 changqing.li
2019-06-28 1:48 ` [meta-networking][PATCH 6/6] samba: upgrade 4.8.12 -> 4.10.5 changqing.li
2019-06-28 9:43 ` [PATCH 0/6] Upgrade 5 packages build with waf Adrian Bunk
2019-07-01 2:29 ` Changqing Li [this message]
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=2d0ef380-ec48-eadc-a4e0-84ddb90ac254@windriver.com \
--to=changqing.li@windriver.com \
--cc=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox