Groups > linux.debian.maint.python > #15187

Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem

Path	csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From	Scott Kitterman <debian@kitterman.com>
Newsgroups	linux.debian.maint.python
Subject	Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem
Date	Sat, 16 Sep 2023 19:10:01 +0200
Message-ID	<HeGXT-9pKl-1@gated-at.bofh.it> (permalink)
References	<HebAJ-96Dm-5@gated-at.bofh.it> <HefO1-99ga-7@gated-at.bofh.it> <HeGEx-9poH-5@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Sat Sep 16 17:05:12 2023
Old-Return-Path	<debian@kitterman.com>
X-Amavis-Spam-Status	No, score=-9.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5.5
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	quoted-printable
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/21118
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/9C65766D-0C5A-4687-B27F-A58C676DAE90@kitterman.com
Approved	robomod@news.nic.it
Lines	36
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Sat, 16 Sep 2023 17:04:14 +0000
X-Original-Message-ID	<9C65766D-0C5A-4687-B27F-A58C676DAE90@kitterman.com>
X-Original-References	<13aae4ad-229f-9f2d-0767-16d18a069dc1@debian.org> <4965668.a2WUb4uf8B@localhost> <f0cef55c-ed1c-2789-6c33-d0a0cf1b0a05@debian.org>
Xref	csiph.com linux.debian.maint.python:15187

Show key headers only | View raw

On September 16, 2023 4:48:46 PM UTC, Thomas Goirand <zigo@debian.org> wrote:
>On 9/15/23 14:03, Scott Kitterman wrote:
>> Why did you hijack this from the Python team instead of just working with the
>> existing maintainers to update the existing packages from the new upstream
>> location?
>> 
>> Scott K
>
>Thanks for replying to the original question ... :)
>
>If the current maintainer was interested, they had plenty of time to work on this (it's been nearly a year that lextudio took over). It doesn't seem to be the case unfortunately.
>
>If someone wants to take over my work, please do (and write in this thread saying you're working on it...), it's not too late. I take care of too many packages already, I'd love if someone stepped in.
>

It's pretty relevant to your question.  If you had instead updated the existing packages from the new upstream, no transition would be needed.

Did you check with the existing maintainers to see what they thought?  Were they even aware of the new upstream work (it's happened to me before that I was unaware of such a switch)?

As is usually the case in Debian, I think the answer is you work with the maintainers to figure out the best solution.  Ignoring them and hijacking the packages is not the right answer.

Scott K

Thread

Transitionning to the lextudio pysnmp / pyasn1 ecosystem Thomas Goirand <zigo@debian.org> - 2023-09-15 09:40 +0200
  Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem Scott Kitterman <debian@kitterman.com> - 2023-09-15 14:10 +0200
    Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem Thomas Goirand <zigo@debian.org> - 2023-09-16 18:50 +0200
      Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem Scott Kitterman <debian@kitterman.com> - 2023-09-16 19:10 +0200
        Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem Thomas Goirand <zigo@debian.org> - 2023-09-17 23:50 +0200
          Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem Scott Kitterman <debian@kitterman.com> - 2023-09-18 00:20 +0200
  Re: Transitionning to the lextudio pysnmp / pyasn1 ecosystem Adam Cécile <acecile@le-vert.net> - 2023-09-19 08:10 +0200

csiph-web