Is it the normal procedure that even security updates are
delayed during the ports freeze for 4.1?
I`ve PHP (5.2 already), Firefox (1.5.0.10) and ClamAV (0.90) in mind
wich do fix security bugs.
I just asked myself if those updates get delayed as well just because
of the Ports-Freeze?
Kind regar
* Sebastian Rother <[EMAIL PROTECTED]> [070226 14:29]:
> Is it the normal procedure that even security updates are
> delayed during the ports freeze for 4.1?
>
> I`ve PHP (5.2 already), Firefox (1.5.0.10) and ClamAV (0.90) in mind
> wich do fix security bugs.
>
> I just asked myself if those upda
Dude you ask this same question every release. How about sending a
patch before the tree locks for a change?
On Mon, Feb 26, 2007 at 08:20:24PM +0100, Sebastian Rother wrote:
> Is it the normal procedure that even security updates are
> delayed during the ports freeze for 4.1?
>
> I`ve PHP (5.2
>If you look at the cvs tree you'll find Firefox is at version 2.0.0.1
>and there's no tag for 4.1 yet. Didn't bother to check the others,
>figured you can look if your interested.
>
>While not answering your question directly, I think it points in the
>direction you should look.
>
>Jim
Well that
On 2007/02/26 20:20, Sebastian Rother wrote:
> Is it the normal procedure that even security updates are
> delayed during the ports freeze for 4.1?
A version upgrade is often security+something else.
Sometimes ports *just* take security fixes from a new version and
nothing else. I'm not saying wh
Stuart Henderson wrote:
> At least we do have Suhosin by default.
Which is cool. However, one question on that subject: Though php core
is patched with Suhosin, what about the Suhosin extension? I've searched
the archives, packages and ports and couldn't find it.
Is anybody having some news (or '
