Mark Andrews said:
>> Thanks a lot for your reply. If I understand things correctly, I need to
>> maintain two cvsup files - one that tracks security issues in the base
>> FreeBSD 5.3 system (tag=RELENG_5_3, src-all) and one for the ports
>> collection (tag=. , ports-all). Then every time I recei
On Wed, 22 Dec 2004 09:52:01 +0800,
Ladislav Bodnar <[EMAIL PROTECTED]> said:
> Thanks a lot for your reply. If I understand things correctly, I need to
> maintain two cvsup files - one that tracks security issues in the base
> FreeBSD 5.3 system (tag=RELENG_5_3, src-all) and one for the
> On Wednesday 22 December 2004 09:06, Mark Andrews wrote:
> > > Hello,
> > >
> > > Due to the recently discovered vulnerability in PHP versions older than
> > > 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it
> > > is a good way to keep the ports collection up-to-date with
On Wednesday 22 December 2004 09:06, Mark Andrews wrote:
> > Hello,
> >
> > Due to the recently discovered vulnerability in PHP versions older than
> > 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it
> > is a good way to keep the ports collection up-to-date with respect to
>
> Hello,
>
> Due to the recently discovered vulnerability in PHP versions older than
> 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it is a
> good way to keep the ports collection up-to-date with respect to security
> issues. I ran cvsup on the security branch (tag=RELEN
Hello,
Due to the recently discovered vulnerability in PHP versions older than
4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it is a
good way to keep the ports collection up-to-date with respect to security
issues. I ran cvsup on the security branch (tag=RELENG_5_3), then
