[chirp_devel] Fwd: Bug#936299: marked as done (chirp: Python2 removal in sid/bullseye)

[David Ranch]

<sigh>  Sorry for the spam but it seems like people are already on it 
and this quickly followed the last email!

--David
KI6ZHD




-------- Forwarded Message --------
Subject: 	chirp_20200227+py3+20200213-1_source.changes ACCEPTED into 
unstable
Resent-Date: 	Thu, 6 Aug 2020 21:36:19 +0000 (UTC)
Resent-From: 	debian-hams at lists.debian.org
Date: 	Thu, 06 Aug 2020 21:18:33 +0000
From: 	Debian FTP Masters <ftpmaster at ftp-master.debian.org>
To: 	Debian Hamradio Maintainers <debian-hams at lists.debian.org>, 
Christoph Berg <myon at debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 06 Aug 2020 22:59:46 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams at lists.debian.org>
Changed-By: Christoph Berg <myon at debian.org>
Closes: 885265 936299
Changes:
  chirp (1:20200227+py3+20200213-1) unstable; urgency=medium
  .
    * Switch to upstream py3 branch based on python3-wxgtk4.0.
      (Closes: #885265, #936299)
    * Lots of python3 porting missing, tested so far: Baofeng UV-5R.
Checksums-Sha1:
  89e008df68c1376761b8a2549a21bc35efd8b7b4 2193 chirp_20200227+py3+20200213-1.dsc
  aeba1b24682bc62765386988fca317a7a7a0a5ee 1198525 chirp_20200227+py3+20200213.orig.tar.gz
  e81437a37e483eb7970153020f025c34eac18140 11760 chirp_20200227+py3+20200213-1.debian.tar.xz
Checksums-Sha256:
  18e70711e5489de4ca75aa580a6e95eab811ce10886cd44ee45ede66ba2395d5 2193 chirp_20200227+py3+20200213-1.dsc
  898bc3359716dad537ef2f74c3e08c07ddf83c4ce325a33dfc1b45abcd991628 1198525 chirp_20200227+py3+20200213.orig.tar.gz
  be493d1babc0ea6bf72399fedaf331b8692ffa88573686009235b953eefcf6b7 11760 chirp_20200227+py3+20200213-1.debian.tar.xz
Files:
  a4adfb0ec790927a42e1520c126bbb66 2193 hamradio optional chirp_20200227+py3+20200213-1.dsc
  d3b68c04be9b401d629352f77a6835be 1198525 hamradio optional chirp_20200227+py3+20200213.orig.tar.gz
  ea204a4426b0d1a5b3dff8aec0286073 11760 hamradio optional chirp_20200227+py3+20200213-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl8scRMACgkQTFprqxLS
p64Wvg//a1RMcgo6hV/u+CxYzMu0W/KX7WTogvgWzRdiVyPto+zoFpTY34UOQEfj
+161D8+qwljnu2rGXkWtNk09uC+BP/gXTwm/gauBvLt0Nayc1dLcT/My8eqrpVM2
rVl2m+Sdp4sW91XSKkfToW4/1MlBshAp6earrviI3fUH7bhotIP2KTqA7jJN3McD
84P/E9QUwaHsHKY4sDTCdwHtUa2aZAzEZ2dD3P7zA9QLrBBrjgFzKEraMO5FS5LV
vOakC9rYI5MuxcRXtrRGVqhcWnmrP1bjPn1yM+NFmYL2A/NLFRkjW/4Hn9wuGfgY
g1+T2qHBkjQAbjiJ5QePsNkM847okR8Ida3/zK/SsvYauj/VSAS7PDNyVjliEue3
KSOGDz5N7Bz4zKsOxUuMr/HdZFK9tZfvmYPK46g75zjipcD8irTPE1YBEfu1LRLC
TMntdMZq8dDxDVQ4hgE0k69Mv85pN7Xjm/E9ODIzk9V43ZRiDWLMmuRWm7vKrIbi
z2XYIMDO+DN0BCjSz2/jw1mCY9lWJwAcW/+tBgyJsMzUrDTtaC/4awo4NN3S+6hd
1+DIovoMSC/1cBh0gUhzJ6ySLRLcjI3AF0okPbR6iMNKm9aUY9S4fCM7kjf0vmD+
AmOrL4h61iM1omm3spmHzmnpFP4JNmV5yjfEKbbNcs4ZBQ1tcR4=
=mq0M
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.





On 08/06/2020 02:42 PM, David Ranch via chirp_devel wrote:
>
> 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 at lists.debian.org
> Date: 	Thu, 06 Aug 2020 21:21:05 +0000
> From: 	Debian Bug Tracking System <owner at bugs.debian.org>
> Reply-To: 	936299 at bugs.debian.org
> To: 	Christoph Berg <myon at debian.org>
>
>
>
> Your message dated Thu, 06 Aug 2020 21:18:33 +0000
> with message-id<E1k3nHV-000C4v-Ev at 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 contactowner at bugs.debian.org
> immediately.)
>
>
> -- 
> 936299:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936299
> Debian Bug Tracking System
> Contactowner at bugs.debian.org  with problems
>
>
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20200806/6a2a9f1d/attachment-0001.html