From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: PHP 7.4.33, PHP 8.0.25 + pear, PHP 8.1.12 + pear, php.*apcu 5.1.22, php.*igbinary 3.2.9
Date: Thu, 03 Nov 2022 18:06:29 +0100 [thread overview]
Message-ID: <20221103170629.hyDYH98Bcx-xeGA4kaGhn8I_l9Xi7NOSzc-GPycqSvo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39438@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
New comment by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/pull/39438#issuecomment-1302416256
Comment:
Anything holding this up? I think there's at least one CVE that these updates address...
next prev parent reply other threads:[~2022-11-03 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 17:51 [PR PATCH] php8.[01]: add php8.[01]-pear subpackage TinfoilSubmarine
2022-09-26 14:40 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-09-29 13:16 ` TinfoilSubmarine
2022-09-29 13:28 ` TinfoilSubmarine
2022-09-30 13:19 ` TinfoilSubmarine
2022-09-30 13:32 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-10-07 13:12 ` [PR PATCH] [Updated] PHP 7.4.32, PHP 8.0.24 + pear, PHP 8.1.11 + pear TinfoilSubmarine
2022-10-07 13:17 ` [PR PATCH] [Updated] PHP 7.4.32, PHP 8.0.24 + pear, PHP 8.1.11 + pear, php.*apcu 5.1.22 TinfoilSubmarine
2022-10-07 14:12 ` TinfoilSubmarine
2022-10-07 14:14 ` TinfoilSubmarine
2022-10-07 17:25 ` TinfoilSubmarine
2022-10-31 13:02 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-11-03 15:30 ` [PR PATCH] [Updated] PHP 7.4.32, PHP 8.0.25 + pear, PHP 8.1.12 + pear, php.*apcu 5.1.22, php.*igbinary 3.2.9 TinfoilSubmarine
2022-11-03 17:06 ` TinfoilSubmarine [this message]
2022-11-15 14:29 ` [PR PATCH] [Updated] PHP 7.4.33, " TinfoilSubmarine
2022-11-15 14:48 ` [PR PATCH] [Updated] php.*: 7.4.33, 8.0.25 + pear, 8.1.12 + pear, apcu 5.1.22, igbinary 3.2.12 TinfoilSubmarine
2022-11-17 11:51 ` [PR PATCH] [Merged]: " paper42
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=20221103170629.hyDYH98Bcx-xeGA4kaGhn8I_l9Xi7NOSzc-GPycqSvo@z \
--to=tinfoilsubmarine@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).