ports/139880: security/barnyard2, update to pkg-message file, bump portrevision

[Paul Schmehl]

>Number:         139880
>Category:       ports
>Synopsis:       security/barnyard2, update to pkg-message file, bump portrevision
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 24 04:10:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Paul Schmehl
>Release:        FreeBSD 7.2-STABLE i386
>Organization:
The University of Texas at Dallas
>Environment:
System: FreeBSD hostname.utdallas.edu 7.2-STABLE FreeBSD 7.2-STABLE #13: Thu Sep 24 09:02:53 CDT 2009 root at hostname.utdallas.edu:/usr/obj/usr/src/sys/GENERIC i386


	
>Description:
	I just submitted a new port request, security/barnyard2-devel
	this revision to the existing port adds a warning to the pkg-message
	file so that users can decide which port, this one or the new devel
	port, is appropriate for their use
>How-To-Repeat:
	
>Fix:

	

--- patch-Makefile begins here ---
--- Makefile.orig	2009-10-23 22:57:21.000000000 -0500
+++ Makefile	2009-10-23 22:57:38.000000000 -0500
@@ -7,6 +7,7 @@
 
 PORTNAME=	barnyard2
 PORTVERSION=	1.6
+PORTREVISION=	1
 CATEGORIES=	security
 MASTER_SITES=	http://www.securixlive.com/download/barnyard2/
 
--- patch-Makefile ends here ---

--- patch-pkg-message.in begins here ---
--- files/pkg-message.in.orig	2009-10-23 22:03:50.000000000 -0500
+++ files/pkg-message.in	2009-10-23 22:06:55.000000000 -0500
@@ -1,4 +1,15 @@
 ************************************************************************
+**************************WARNING****WARNING****************************
+**************************WARNING****WARNING****************************
+
+This version of barnyard2 does not correctly parse the waldo file.  As a
+result, each time barnyard2 is restarted, all alerts remaining in the 
+snort log directory will be reinserted into the database.  If this is a
+a problem for you, consider using security/barnyard2-devel, which has
+resolved this problem.
+
+**************************WARNING****WARNING****************************
+**************************WARNING****WARNING****************************
  
 Read the notes in the barnyard2.conf file for how to configure 
 %%PREFIX%%/etc/barnyard2.conf after installation.  For addtional information
--- patch-pkg-message.in ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: