I suspect the "upstream" coders should fix this, but I don't know if this code is being actively maintained.... anyway: When using BER.pm (part of dev-perl/SNMP_Session-0.92-r1) I get the following: Possible precedence problem on bitwise | operator at /usr/lib/perl5/vendor_perl/5.8.8/BER.pm line 611. Reproducible: Always Steps to Reproduce: 1. use SNMP_util in perl code 2. get warning The fix is well published on TheGoogleNet... change line 611 in BER.pm as follows: $ diff BER.pm.orig BER.pm.new 611c611 < return error ("Sequence expected") unless $result == sequence_tag | constructor_flag; --- > return error ("Sequence expected") unless $result == sequence_tag or constructor_flag;
(In reply to comment #0) > I suspect the "upstream" coders should fix this, but I don't know if this code > is being actively maintained.... It was fixed in a later version. Latest version (1.12) is in the tree now. Thanks for the report.
Thanks for the quick response on this bug. Question for you: you said that the latest version of SNMP_Session (1.12) is now in the tree, but I'm not seeing it after I do an "emerge --sync". How long does it typically take for your change to replicate to the misc mirrors?
(In reply to comment #2) > Thanks for the quick response on this bug. Question for you: you said that the > latest version of SNMP_Session (1.12) is now in the tree, but I'm not seeing it > after I do an "emerge --sync". How long does it typically take for your change > to replicate to the misc mirrors? Typically it takes an hour. Maybe your mirror was out of sync? http://mirrorstats.gentoo.org/rsync/ http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-perl/SNMP_Session/
Hmm, had sync'd before... must have just missed the replication, as the new code is now availble on my system. Thanks again.
Release 1.12 tested OK for me on x86. Do we need to open a new bug request that it marked stable on x86?
Ahh, I revoke my request for stable on x86. There is an issue in v1.12 in the SNMP_util.pm file. Parsing of comments in "sub snmpMIB_to_OID" is incorrect, which leads to issues with parsing of the latest CISCO-PRODUCTS-MIB.my file. I am reporting that bug to the upstream coders (Mike.Mitchell@sas.com).