Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #14052 > unrolled thread

python3-pysnmp4 forked upstream

Started byLuiz Amaral <email@luiz.eng.br>
First post2022-04-07 13:30 +0200
Last post2022-04-07 17:50 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.maint.python


Contents

  python3-pysnmp4 forked upstream Luiz Amaral <email@luiz.eng.br> - 2022-04-07 13:30 +0200
    Re: python3-pysnmp4 forked upstream Julien Cristau <jcristau@debian.org> - 2022-04-07 14:10 +0200
    Re: python3-pysnmp4 forked upstream Stefano Rivera <stefanor@debian.org> - 2022-04-07 17:30 +0200
      Re: python3-pysnmp4 forked upstream Luiz Amaral <email@luiz.eng.br> - 2022-04-07 17:50 +0200

#14052 — python3-pysnmp4 forked upstream

FromLuiz Amaral <email@luiz.eng.br>
Date2022-04-07 13:30 +0200
Subjectpython3-pysnmp4 forked upstream
Message-ID<E9yuR-764c-3@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#14053

FromJulien Cristau <jcristau@debian.org>
Date2022-04-07 14:10 +0200
Message-ID<E9z7z-76ws-5@gated-at.bofh.it>
In reply to#14052
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

[toc] | [prev] | [next] | [standalone]


#14055

FromStefano Rivera <stefanor@debian.org>
Date2022-04-07 17:30 +0200
Message-ID<E9Cfc-78pd-7@gated-at.bofh.it>
In reply to#14052
Hi Luiz (2022.04.07_11:22:49_+0000)
> 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

[toc] | [prev] | [next] | [standalone]


#14056

FromLuiz Amaral <email@luiz.eng.br>
Date2022-04-07 17:50 +0200
Message-ID<E9Cyt-78vR-3@gated-at.bofh.it>
In reply to#14055
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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web