Replying to my own email here and it seems this has already been done *but* it seems that new effort in "Sid" (not Testing") is having an issue of it's own. I wonder if there could be an updated version submitted for both branches so some form of working Chirp can be provided from Debian's standard repos?
--David KI6ZHD
-------- Forwarded Message -------- Subject: Bug#1012538: knocked out usability - module 'collections' has no attribute 'Callable' Resent-Date: Wed, 08 Jun 2022 21:00:02 +0000 Resent-From: Arnaldo Pirrone it9exm@gmail.com Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: it9exm@gmail.com, Debian Hamradio Maintainers debian-hams@lists.debian.org Date: Wed, 08 Jun 2022 22:57:12 +0200 From: Arnaldo Pirrone it9exm@gmail.com Reply-To: Arnaldo Pirrone it9exm@gmail.com, 1012538@bugs.debian.org To: Debian Bug Tracking System submit@bugs.debian.org
Package: chirp
Version: 1:20200227+py3+20200213-3 Severity: grave X-Debbugs-Cc: it9exm@gmail.com
Just tried using this software to program my radio and found out it stopped working. I remember it was everything fine a few months ago. Probably this is caused by changes in Python 3.10.5
-- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386
Kernel: Linux 5.17.13-xanmod1 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Versions of packages chirp depends on: ii python3 3.10.4-1+b1 ii python3-future 0.18.2-6 ii python3-serial 3.5-1 ii python3-six 1.16.0-3 ii python3-wxgtk4.0 4.0.7+dfsg-13
chirp recommends no packages.
chirp suggests no packages.
-- no debconf information
On 06/08/2022 10:05 AM, David Ranch via chirp_devel wrote:
I saw the following deprecation come in from the Debian packaging system. I'm curious if any of the Python3 efforts might be stable enough (even if they just have CLI support for now) to be submitted to replace this original source code?
--David KI6ZHD
-------- Forwarded Message -------- Subject: chirp is marked for autoremoval from testing Resent-Date: Wed, 8 Jun 2022 04:57:21 +0000 (UTC) Resent-From: debian-hams@lists.debian.org Date: Wed, 08 Jun 2022 04:39:08 +0000 From: Debian testing autoremoval watch noreply@release.debian.org To: chirp@packages.debian.org
chirp 1:20200227+py3+20200213-3 is marked for autoremoval from testing on 2022-06-23
It (build-)depends on packages with these RC bugs: 1010820: pypdf2, src:bookletimposer: pypdf2 breaks bookletimposer autopkgtest: Can't get Fields array https://bugs.debian.org/1010820 1010821: pypdf2, src:xml2rfc: pypdf2 breaks xml2rfc autopkgtest: lxml.etree.XMLSyntaxError: PCDATA invalid Char value 1 https://bugs.debian.org/1010821 1011697: wxpython4.0: FTBFS: ImportError: cannot import name 'parse' from 'sipbuild.code_generator' (/usr/lib/python3/dist-packages/sipbuild/code_generator.abi3.so) https://bugs.debian.org/1011697
This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mai...
Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gathe...
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers