From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/samba4: bump version to 4.14.2
Date: Sat, 03 Apr 2021 09:37:08 +0200 [thread overview]
Message-ID: <87sg47akez.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87o8ezc01j.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Wed, 31 Mar 2021 08:25:12 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
>> Added patch to fix build error.
>> Removed patch which was applied upstream.
>> Added two options to samba4-cache.txt to fix cross build, values were
>> taken from GnuTLS source:
>> https://gitlab.com/gnutls/gnutls/-/blob/3.6.15/lib/includes/gnutls/gnutls.h.in#L180
>> https://gitlab.com/gnutls/gnutls/-/blob/3.6.15/lib/includes/gnutls/gnutls.h.in#L341
>> host-perl is now mandatory, also host-perl-parse-yapp is needed.
>> Added option to fix build without dbus, this change needed a rework of
>> the shared-modules configure option, due to this upstream commit:
>> https://gitlab.com/samba-team/devel/samba/-/commit/b6805d5e0bcf1716f87e84bcbb2fd8f93c38a8a3
>> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> samba 4.14.2 is a security bump, and the 4.11.x series seems to be EOL
> :/
> For backporting it would have been nicer to only move to 4.12.x first,
> as the 4.11..4.14 changes look a bit scary.
I applied it anyway to 2021.02.x after looking at the
https://wiki.samba.org/index.php/Samba_Release_Planning. 4.12.x will go
EOL in September, so we will most likely need to move to 4.13 / 4.14 anyway.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-04-03 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 9:45 [Buildroot] [PATCH v2 1/1] package/samba4: bump version to 4.14.2 Bernd Kuhls
2021-03-28 19:45 ` Thomas Petazzoni
2021-03-31 6:25 ` Peter Korsgaard
2021-04-03 7:37 ` Peter Korsgaard [this message]
2021-04-03 7:34 ` Peter Korsgaard
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=87sg47akez.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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