Date: Wed, 2 Jun 2010 18:33:37 GMT From: Rob Bloodgood <rob@exitexchange.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/147336: p5-POE-Component-SNMP is out of date Message-ID: <201006021833.o52IXbcf080179@www.freebsd.org> Resent-Message-ID: <201006021840.o52Ie6Hx006556@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 147336 >Category: ports >Synopsis: p5-POE-Component-SNMP is out of date >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Wed Jun 02 18:40:05 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Rob Bloodgood >Release: 9.0 >Organization: >Environment: >Description: I'm the author of the Perl module POE::Component::SNMP. I was surprised and pleased that somebody added it to the Ports collection, but the current version (1.0005) has serious problems with the current 6.0 version of the Net::SNMP (p5-Net-SNMP) perl module. The bug is fixed in 1.0006 but hasn't reached ports yet. .. a quick look shows that the current version of Net::SNMP in ports is 5.2.0, which doesn't demonstrate the problem with 1.0005. version 1.0006 is compatible with both Net::SNMP v5 and v6. Can this be updated? Thanks in advance, Rob >How-To-Repeat: run "make test" with PoCo::SNMP 1.0005 and Net::SNMP 6.0 >Fix: update to POE::Component::SNMP 1.0006 >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006021833.o52IXbcf080179>