public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Josh Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hoffie@gentoo.org
Subject: Re: [gentoo-dev] Upcoming masking of dev-lang/php-4* and packages depending on it
Date: Wed, 10 Oct 2007 22:44:54 -0700	[thread overview]
Message-ID: <470DB856.3090004@gentoo.org> (raw)
In-Reply-To: <20071007151349.21aed58b@tux.home>

[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]

Christian Hoffmann wrote:
> Heya,
> 
> I'm going to p.mask =dev-lang/php-4* and all packages explicitly
> depending on this version of php (i.e. the whole dev-php4/ category
> (36 packages) and one webapp, www-apps/knowledgetree, bug 194894 [1])
> next weekend (around Oct 14th). This step is necessary as there is
> hardly any upstream activity anymore.
> 
> The last official version of php-4, 4.4.7, dates back to May 3rd and is
> in the same state as php-5.2.2 security-wise (and we all know how many
> issues php-5 had in the past, just have a look at the recently published
> GLSA 200710-02 [2]).
> 
> All those security problems, which were fixed in the 5.2 branch,
> possibly apply to the 4.4 branch as well, yet there are no (backported)
> fixes in upstream CVS and there is no sign of an upcoming release
> either.
> This means, if we were to continue php-4 support we would have to do
> the upstream work and compile a list of issues + patches. Upstream
> developers seem to see it the same way -- "if you really want to get it
> done - do it" was one reply when I asked what's up with php-4. Noone
> from our PHP team has the time and motiviation to do that work, and as
> such we are going to mask it (unless someone volunteers to do the work
> and/or upstream becomes active again).
> 
> We will still keep php-4 (and all related packages) in the tree until at
> least the end of the year (this is the date where official upstream
> "support" ends) and bump it if (and not "when"...) there are any
> releases.
> 
> We advise all users of of php-4 to upgrade to php-5 as soon as possible.
> 
> [1] https://bugs.gentoo.org/show_bug.cgi?id=194894
> [2] http://www.gentoo.org/security/en/glsa/glsa-200710-02.xml

Since you're doing the masking, can you please help out the GDP by
reviewing a few of our documents for any potential changes that must be
made? Grepping for "php4" shows that there are references in the
following docs:

1. http://www.gentoo.org/doc/en/jffnms.xml
2. http://www.gentoo.org/doc/en/apache-troubleshooting.xml
3. http://www.gentoo.org/doc/en/qmail-howto.xml
4. http://www.gentoo.org/doc/en/handbook/hb-working-rcscripts.xml


Thanks,

Josh


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-10-11  5:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07 13:13 [gentoo-dev] Upcoming masking of dev-lang/php-4* and packages depending on it Christian Hoffmann
2007-10-11  4:29 ` Marius Mauch
2007-10-11  5:58   ` [gentoo-dev] " Christian Faulhammer
2007-10-11 14:43     ` Christian Hoffmann
2007-10-11  5:44 ` Josh Saddler [this message]
2007-10-11 15:00   ` [gentoo-dev] " Christian Hoffmann
2007-10-11 18:51     ` Josh Saddler
2007-10-11 20:29       ` Josh Saddler

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=470DB856.3090004@gentoo.org \
    --to=nightmorph@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hoffie@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