-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've recently discovered a problem report for the mod_fastcgi (2.4.2)
port: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/79774. The report
seems to indicate that the port was fixed shortly after the PR was sent
(May 31), yet I just did a cvsup and the buggy port still shows up.
I have made the fix to my copy of the port and it does work, but why isn't
the fixed version available via cvsup? My cvsup log (run just this
morning) shows that the fastcgi Makefile was checked out, yet its date is
still early on May 31, apparently just before the fix was done, according
to the PR.
Anyone know what might be going on? Since the fastcgi port is called by
the rt-3.4.2 port (which is my real interest), keeping my fixed version of
the former around under a different name is not really a good option, in
case I need to update RT.
Thanks.
Mike
_____________________________________________________________________
Mike Friedman System and Network Security
[EMAIL PROTECTED] 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu
_____________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBQuZ1jq0bf1iNr4mCEQIOfACgk8PCCvxZ63wS8fNRkVFo63RYUP8AoJZ1
pYE15oKcDbAnKtDVMKrcBzVi
=r/OJ
-----END PGP SIGNATURE-----
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
