Fyi, maybe the new Chirp Python3 branch might be good enough to keep something in the Debian ecosystem.  If not, Chirp will drop out of the Debian repos but maybe that's not a major concern.

--David
KI6ZHD


-------- Forwarded Message --------
Subject: Bug#936299: marked as done (chirp: Python2 removal in sid/bullseye)
Resent-Date: Thu, 6 Aug 2020 21:21:28 +0000 (UTC)
Resent-From: debian-hams@lists.debian.org
Date: Thu, 06 Aug 2020 21:21:05 +0000
From: Debian Bug Tracking System <owner@bugs.debian.org>
Reply-To: 936299@bugs.debian.org
To: Christoph Berg <myon@debian.org>


Your message dated Thu, 06 Aug 2020 21:18:33 +0000
with message-id <E1k3nHV-000C4v-Ev@fasolo.debian.org>
and subject line Bug#936299: fixed in chirp 1:20200227+py3+20200213-1
has caused the Debian Bug report #936299,
regarding chirp: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
936299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936299
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems