Re: python3-pysnmp4 forked upstream
On 4/7/22 17:22, Stefano Rivera wrote: > > Sounds like switching to the fork is a good idea. Then I will have a go at it tomorrow. Thanks for the input. Luiz
Re: python3-pysnmp4 forked upstream
Hi Luiz (2022.04.07_11:22:49_+) > It looks like the current upstream[1] of pysnmp has been unmaintained > for a while and got forked [2]. > > FreeBSD has done some adjustments to pysnmp and the related packages > because of that [3][4], as the current version seems broken in Python 3.9. > > What is your opinion on updating these packages to use the forked upstream? Sounds like switching to the fork is a good idea. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: python3-pysnmp4 forked upstream
On Thu, Apr 07, 2022 at 01:22:49PM +0200, Luiz Amaral wrote: > Hello Python Team, > > It looks like the current upstream[1] of pysnmp has been unmaintained > for a while and got forked [2]. > > FreeBSD has done some adjustments to pysnmp and the related packages > because of that [3][4], as the current version seems broken in Python 3.9. > > What is your opinion on updating these packages to use the forked upstream? > > I cced Julien specifically because I saw he was working on pyasn1 > yesterday. > Hi Luiz, Sorry, I've got no knowledge of / interest in pysnmp at the moment. (I only did a drive-by upload of pyasn1-modules yesterday because I was looking at RFC3161 and that was missing in the version in sid.) Cheers, Julien
python3-pysnmp4 forked upstream
Hello Python Team, It looks like the current upstream[1] of pysnmp has been unmaintained for a while and got forked [2]. FreeBSD has done some adjustments to pysnmp and the related packages because of that [3][4], as the current version seems broken in Python 3.9. What is your opinion on updating these packages to use the forked upstream? I cced Julien specifically because I saw he was working on pyasn1 yesterday. Thank you, Luiz. [1] https://github.com/etingof/pysnmp [2] https://github.com/pysnmp/pysnmp [3] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257860 [4] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262906