From: Jaco Kroon <jaco@uls.co.za>
To: gentoo-dev@lists.gentoo.org,
Arthur Zamarin <arthurzam@gentoo.org>,
gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev] Re: Last rites EAPI=6 packages: dev-php/*
Date: Wed, 11 Sep 2024 09:33:10 +0200 [thread overview]
Message-ID: <5babde00-594b-42d6-aeec-9c2398e30a7f@uls.co.za> (raw)
In-Reply-To: <f24f1fdb-c8a7-43f3-9737-d89e9d63ed3a@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Hi,
I missed this announcement, looking specifically for composer again.
If I make the effort of bumping to newest version, is this something
that would be re-added to the tree?
I note there were active security vulnerabilities under very specific
conditions (composer.phar is exposed via http).
Or should I rather just deploy this into a local overlay?
Kind regards,
Jaco
On 2024/06/21 19:20, Arthur Zamarin wrote:
> # Arthur Zamarin<arthurzam@gentoo.org> (2024-06-21)
> # Last dev-php/* EAPI=6 packages, and reverse dependencies of them.
> # composer has active security vulnerabilities. Others are waiting
> # for version bumps, and unbundling of dependencies.
> # Removal on 2024-07-21. Bugs #934666.
> dev-php/phpDocumentor
> dev-php/phpcov
> dev-php/phpdepend
> dev-php/phpdocumentor-reflection-common
> dev-php/phpdocumentor-reflection-docblock
> dev-php/phpdocumentor-type-resolver
> dev-php/stringparser_bbcode
> dev-php/symfony-config
> dev-php/symfony-console
> dev-php/symfony-dependency-injection
> dev-php/symfony-event-dispatcher
> dev-php/symfony-yaml
> dev-php/composer
[-- Attachment #2: Type: text/html, Size: 1930 bytes --]
next prev parent reply other threads:[~2024-09-11 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 17:20 [gentoo-dev] Last rites EAPI=6 packages: dev-php/* Arthur Zamarin
2024-09-11 7:33 ` Jaco Kroon [this message]
2024-09-11 11:26 ` [gentoo-dev] " Michael Orlitzky
2024-09-11 15:23 ` Jaco Kroon
2024-09-13 10:22 ` Michael Orlitzky
2024-09-13 11:53 ` Jaco Kroon
2024-09-13 1:46 ` Duncan
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=5babde00-594b-42d6-aeec-9c2398e30a7f@uls.co.za \
--to=jaco@uls.co.za \
--cc=arthurzam@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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