ports/70428: Maintainer-Update: net/trafshow broken -- Back out upgrade

[Ryan Thompson]

>Number:         70428
>Category:       ports
>Synopsis:       Maintainer-Update: net/trafshow broken -- Back out upgrade
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 13 20:20:24 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Ryan Thompson <ryan at sasknow.com>
>Release:        FreeBSD 4.9-RELEASE-p11 i386
>Organization:
SaskNow Technologies
>Environment:
System: FreeBSD drizzle.sasknow.net 4.9-RELEASE-p11 FreeBSD 4.9-RELEASE-p11 #1: Thu Jul 8 15:15:17 CST 2004 crayz at earl.sasknow.net:/usr/obj/usr/src/sys/DRIZZLE i386


        
>Description:

Since upgrading trafshow to the author's release of 4.0, numerous FreeBSD
users have reported problems with traffic aggregation, to the point that the
4.0 version of the port is not useful. It initially tested okay for me in my
simple installation, but numerous users on freebsd-ports@ have had issues.

As yet, I haven't found an easy solution. As an interim solution until I can
coordinate efforts with the trafshow author, or patch locally, I need a
committer to back out last week's maintainer-update and revert to 3.1_4.

Better yet, maybe we should do a repo copy of the current 4.0 port to
net/trafshow4, and keep the 3.1_4 as net/trafshow, and eventually retire it
once 4.0 has been adopted and is considered to be stable. Keep in mind that
trafshow 3.1 wasn't updated since 1996, IIRC, so it is *extremely* well
entrenched and should probably stick around for a while.

>How-To-Repeat:
        
>Fix:

See my suggestions in the Description. Essentially:

First, repo-copy net/trafshow -> net/trafshow4
Then, back out ports/70152 for net/trafshow
>Release-Note:
>Audit-Trail:
>Unformatted: