From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/php: security bump to version 7.3.3
Date: Tue, 12 Mar 2019 21:37:54 +0100 [thread overview]
Message-ID: <20190312213754.20f35d52@windsurf> (raw)
In-Reply-To: <20190312151029.24382-1-peter@korsgaard.com>
On Tue, 12 Mar 2019 16:10:29 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> php-7.3.3 fixes a number of security issues (no CVE known, bugtracker issues
> not yet public): https://secure.php.net/ChangeLog-7.php#7.3.3
>
> Drop 0004-OPcache-flock-mechanism-is-obviously-linux-so-force-.patch as the
> flock detection has been removed since commit 9222702633 (Avoid dependency
> on "struct flock" fields order.)
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> ...ch => 0004-Call-apxs-with-correct-prefix.patch} | 0
> ...ck-mechanism-is-obviously-linux-so-force-.patch | 82 ----------------------
> package/php/php.hash | 2 +-
> package/php/php.mk | 2 +-
> 4 files changed, 2 insertions(+), 84 deletions(-)
> rename package/php/{0005-Call-apxs-with-correct-prefix.patch => 0004-Call-apxs-with-correct-prefix.patch} (100%)
> delete mode 100644 package/php/0004-OPcache-flock-mechanism-is-obviously-linux-so-force-.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-12 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:10 [Buildroot] [PATCH] package/php: security bump to version 7.3.3 Peter Korsgaard
2019-03-12 20:37 ` Thomas Petazzoni [this message]
2019-03-25 16:39 ` 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=20190312213754.20f35d52@windsurf \
--to=thomas.petazzoni@bootlin.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