• PySNMP asyncio backend unusable in Debian 12 (needs stable update?)

    From Adam Cecile@21:1/5 to All on Tue Sep 12 18:00:01 2023
    This is a multi-part message in MIME format.
    Hello,


    Package python3-pysnmp4 is partially unusable in Debian 12 because its
    asyncio backend is using @asyncio.coroutine decorator that has been
    removed from Python 3.11.

    It is, imho, quite a serious issue, as any code using PySNMP4 on a
    machine will stop working after upgrading from Debian 11 to Debian 12
    (my case).

    I'm not aware of how Debian stable updates work, but I think we should
    consider making an exception for that.

    I prepared a patched package version using backported patch from new
    upstream (previous maintainer passed away) and had to deal with an
    upstream bug too. Now it works again and I added all information to the
    Debian bug report: https://bugs.debian.org/1051774

    The fix is quite safe as it impacts only asyncio backend, and current
    version is not importable at all so I do not see how it could lead to
    any regression.

    What is your opinion about this ?


    Best regards, Adam.


    <html>
    <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <p>Hello,</p>
    <p><br>
    </p>
    <p>Package python3-pysnmp4 is partially unusable in Debian 12
    because its asyncio backend is using @asyncio.coroutine decorator
    that has been removed from Python 3.11.</p>
    <p>It is, imho, quite a serious issue, as any code using PySNMP4 on
    a machine will stop working after upgrading from Debian 11 to
    Debian 12 (my case).</p>
    <p>I'm not aware of how Debian stable updates work, but I think we
    should consider making an exception for that.</p>
    <p>I prepared a patched package version using backported patch from
    new upstream (previous maintainer passed away) and had to deal
    with an upstream bug too. Now it works again and I added all
    information to the Debian bug report:
    <a class="moz-txt-link-freetext" href="https://bugs.debian.org/1051774">https://bugs.debian.org/1051774</a></p>
    <p>The fix is quite safe as it impacts only asyncio backend, and
    current version is not importable at all so I do not see how it
    could lead to any regression.</p>
    <p>What is your opinion about this ?</p>
    <p><br>
    </p>
    <p>Best regards, Adam.<br>
    </p>
    <p><br>
    </p>
    <div id="grammalecte_menu_main_button_shadow_host" style="width:
    0px; height: 0px;"></div>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Cecile@21:1/5 to thomas@goirand.fr on Tue Sep 12 18:20:01 2023
    This is a multi-part message in MIME format.
    Hello,

    No hurry, I think we might want to wait for upstream to respond to my PR regarding double awaitable fix.
    It is indeed lextudio upstream that took over the PySNMP package and all patches are coming from us (except mine ofc).

    Regards, Adam.

    On 9/12/23 18:10, thomas@goirand.fr wrote:
    Hi,

    Quickly from my phone...

    Of course, we can update Stable with targeted patches (only: no new
    upstream release except in very rare cases).

    I can take care of the update tomorrow, though the next point release
    is in a few month from now.

    Also note that I uploaded all 4 pysnmp/asn1 modules from lextudio. Is
    your patch from them ?

    Cheers,

    Thomas Goirand (zigo)


    On Sep 12, 2023 5:52 PM, Adam Cecile <acecile@le-vert.net> wrote:

    Hello,


    Package python3-pysnmp4 is partially unusable in Debian 12 because
    its asyncio backend is using @asyncio.coroutine decorator that has
    been removed from Python 3.11.

    It is, imho, quite a serious issue, as any code using PySNMP4 on a
    machine will stop working after upgrading from Debian 11 to Debian
    12 (my case).

    I'm not aware of how Debian stable updates work, but I think we
    should consider making an exception for that.

    I prepared a patched package version using backported patch from
    new upstream (previous maintainer passed away) and had to deal
    with an upstream bug too. Now it works again and I added all
    information to the Debian bug report: https://bugs.debian.org/1051774

    The fix is quite safe as it impacts only asyncio backend, and
    current version is not importable at all so I do not see how it
    could lead to any regression.

    What is your opinion about this ?


    Best regards, Adam.


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix">Hello,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">No hurry, I think we might want to wait
    for upstream to respond to my PR regarding double awaitable fix.</div>
    <div class="moz-cite-prefix">It is indeed lextudio upstream that
    took over the PySNMP package and all patches are coming from us
    (except mine ofc).</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Regards, Adam.<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 9/12/23 18:10, <a class="moz-txt-link-abbreviated" href="mailto:thomas@goirand.fr">thomas@goirand.fr</a>
    wrote:<br>
    </div>
    <blockquote type="cite"
    cite="mid:cee6daf2-5aff-4fc2-ae6a-23cc057f8320@goirand.fr">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <div dir="ltr"> Hi, </div>
    <br>
    <div dir="ltr"> Quickly from my phone... </div>
    <br>
    <div dir="ltr"> Of course, we can update Stable with targeted
    patches (only: no new upstream release except in very rare
    cases). </div>
    <br>
    <div dir="ltr"> I can take care of the update tomorrow, though the
    next point release is in a few month from now. </div>
    <br>
    <div dir="ltr"> Also note that I uploaded all 4 pysnmp/asn1
    modules from lextudio. Is your patch from them ? </div>
    <br>
    <div dir="ltr"> Cheers, </div>
    <br>
    <div dir="ltr"> Thomas Goirand (zigo) </div>
    <br>
    <br>
    <div class="bx-html">
    <meta http-equiv="content-type" content="text/html;
    charset=UTF-8">
    <div class="bx-body">
    <div class="quote"> On Sep 12, 2023 5:52 PM, Adam Cecile
    <a class="moz-txt-link-rfc2396E" href="mailto:acecile@le-vert.net">&lt;acecile@le-vert.net&gt;</a> wrote:<br type="attribution">
    <blockquote class="quote" style="margin:0 0 0
    .8ex;border-left:1px #ccc solid;padding-left:1ex">
    <p>Hello,</p>
    <p><br>
    </p>
    <p>Package python3-pysnmp4 is partially unusable in Debian
    12 because its asyncio backend is using
    @asyncio.coroutine decorator that has been removed from
    Python 3.11.</p>
    <p>It is, imho, quite a serious issue, as any code using
    PySNMP4 on a machine will stop working after upgrading
    from Debian 11 to Debian 12 (my case).</p>
    <p>I'm not aware of how Debian stable updates work, but I
    think we should consider making an exception for that.</p>
    <p>I prepared a patched package version using backported
    patch from new upstream (previous maintainer passed
    away) and had to deal with an upstream bug too. Now it
    works again and I added all information to the Debian
    bug report: <a class="moz-txt-link-freetext"
    href="https://bugs.debian.org/1051774"
    moz-do-not-send="true">https://bugs.debian.org/1051774</a></p>
    <p>The fix is quite safe as it impacts only asyncio
    backend, and current version is not importable at all so
    I do not see how it could lead to any regression.</p>
    <p>What is your opinion about this ?</p>
    <p><br>
    </p>
    <p>Best regards, Adam.<br>
    </p>
    <p><br>
    </p>
    </blockquote>
    </div>
    </div>
    </div>
    </blockquote>
    <div id="grammalecte_menu_main_button_shadow_host" style="width:
    0px; height: 0px;"></div>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)