Re: cvsup

From: Michael Sharp (mds@ec.rr.com)
Date: 02/28/02 

From: Michael Sharp <mds@ec.rr.com>
To: security@FreeBSD.ORG
Date: Wed, 27 Feb 2002 18:18:02 -0500

God forbide, I sent to the wrong list. ppl are more concerned about a posting
to a list than putting out something via announcements, ports, errata, smoke
signals or something. I'll figure it out myself

On Wednesday 27 February 2002 06:03 pm, you wrote:
> This is actually more of a -ports question...
>
> On Wed, Feb 27, 2002 at 05:51:50PM -0500, Michael Sharp wrote:
> > I ran cvsup on ports 20 minutes ago and noticed that new Makefiles were
> > pulled down for mod_php3 and mod_php4. I then ran portsdb -U to update
> > the INDEX file, but portversion shows that the new Makefiles didnt change
> > the version number.
> >
> > So my question is this... was this the fix for the PHP issue, and all I
> > need to do new is cd to the mod_php4 directory and run 'make deinstall
> > distclean', then do a 'make install' in mod_php4 to rebuild with the new
> > changes?
>
> I committed an update earlier marking the ports as FORBIDDEN due to
> the security issue until the maintainer update the ports. The
> maintainer updated the ports to the non-vulnerable versions about
> 1/2 hour ago. Chances are you only received the FORBIDDEN update
> and may have to way up to another 1/2 hour until the newer changes
> have propagated.
>
> To check, see if the ports are marked with a FORBIDDEN line. You may
> also use cvsweb:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/mod_php3/
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/mod_php4/
>
> to see if the Makefile in your ports tree matches the newest version
> in the repository.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: cvsup
    ... but portversion shows that the new Makefiles didnt change ... >> the security issue until the maintainer update the ports. ... > God forbide, I sent to the wrong list. ... This sentence would be seven words long if it were six words shorter. ...
    (FreeBSD-Security)
  • Re: cvsup
    ... but portversion shows that the new Makefiles didnt change the ... I committed an update earlier marking the ports as FORBIDDEN due to ... the security issue until the maintainer update the ports. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: Found a problem in the clamav-port when updating
    ... it's indeed easy to run clamav as any user you want. ... Amavis supports dozens ... I did not yet consider the Makefiles *that* important. ... tell me "Look at the Makefile" or "man 7 ports"? ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Newbie problem
    ... Ports updates are often a while before someone takes the time to create ... binary packages for the new port. ... > Makefiles to BSD makefiles? ... but many makefiles work better with gmake than they do ...
    (comp.unix.bsd.freebsd.misc)
  • Re: setting CFLAGS in /etc/make.conf
    ... >>makefiles, and those Makefile.m4 files were already adding a bunch ... I think it would be easy to generalize, although for most ports ... >>on setting CFLAGS. ...
    (freebsd-current)