From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Jérémy ROSEN" <jeremy.rosen@smile.fr>
Cc: buildroot@busybox.net, Pascal de Bruijn <p.debruijn@unilogic.nl>
Subject: Re: [Buildroot] [PATCH] package/php: select SYSTEMD_TMPFILES for PHP_SAPI_FPM
Date: Thu, 5 Aug 2021 21:51:29 +0200 [thread overview]
Message-ID: <20210805215129.02980925@windsurf> (raw)
In-Reply-To: <CAFvCimX4eYVpcRqAFinCcU65qn3F8a-vE0O+1D1uzw0nPQMNMA@mail.gmail.com>
Hello Jérémy,
On Wed, 4 Dec 2019 09:53:53 +0100
Jérémy ROSEN <jeremy.rosen@smile.fr> wrote:
> Ok, for the special case of PHP, this has been fixed upstream with
>
> https://github.com/systemd/systemd/pull/14207
>
> The official word from upstream is "yes tmpfiles is optional but it should
> always be here except for really tiny embedded systems"
>
> So we are good (tmpfile's default is activated)
>
> Ideally, we should backport that PR until upstream adds it to
> systemd-stable.
It's been a while ago, but if I understand correctly what you said,
because PR14207 has been merged upstream, we no longer need absolutely
need tmpfiles support in systemd for PHP's FPM interface to work. We're
now using a much newer systemd version in Buildroot, which must have
PR14207 applied.
So I've marked this patch as Rejected. Pascal, if you disagree and
still see a problem, do not hesitate to resubmit the patch.
Thanks a lot,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-05 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 9:39 [Buildroot] [PATCH] package/php: select SYSTEMD_TMPFILES for PHP_SAPI_FPM Pascal de Bruijn
2019-11-25 21:10 ` Thomas Petazzoni
2019-11-26 17:45 ` Jérémy ROSEN
2019-12-04 8:53 ` Jérémy ROSEN
2021-08-05 19:51 ` Thomas Petazzoni [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=20210805215129.02980925@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=jeremy.rosen@smile.fr \
--cc=p.debruijn@unilogic.nl \
/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