[chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Fred

28 Mar 2020 28 Mar '20

4:41 p.m.

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

After the upgrade, Chirp and a Solitary game which is written in Python no longer worked so I upgraded to the new beta version Fedora 32. This morning, the developers released an update which included many Python changes which fixed the Solitary game but sadly, not Chirp.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

[fred@m5a97r2 chirp-daily]$ ./chirpw -v Traceback (most recent call last): File "./chirpw", line 20, in <module> from chirp import chirp_common File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979 except errors.InvalidDataError, e: ^ SyntaxError: invalid syntax [fred@m5a97r2 chirp-daily]$

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

A bit of an aside: Is this a Python issue in Chirp or a missing Python 2 file in Fedora 32? I notice that when the command "dnf list --installed | grep python" there is a python3.x86_64, but the python2 file is named python27.x86_64. There is no python2.x86_64 file but there is in Fedora 30 a file python2.x86_64. Although, the which command shows both a /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There are several link files in /usr/bin/ with python names that seem to be new additions and probably sort all that out though.

Thanks for the help.

Fred

Show replies by date

Tony Fuller

28 Mar 28 Mar

4:51 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

I am testing Ubuntu 20.04 (Focal Fossa) and although python2 is not installed by default, I can still get it by running apt install python2. Well just have to see if that still works next month when Canonical releases.

Tony ________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Fred fredferickson@gmail.com Sent: Saturday, March 28, 2020 6:41:37 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

Thanks for the help.

________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Fred fredferickson@gmail.com Sent: Saturday, March 28, 2020 6:41:37 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

Thanks for the help.

Fred _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com ________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Fred fredferickson@gmail.com Sent: Saturday, March 28, 2020 6:41:37 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

Thanks for the help.

Richard Shaw

5:08 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

Chirp definitely won't work on Fedora 32 but should on Fedora 31, which is what I'm running (and I'm the maintainer).

I would guess that perhaps you have some packages that didn't upgrade properly?

What does "dnf distro-sync" show?

Thanks, Richard KF5OIM

Darrell & Sandy

5:51 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

I do not have Linux I have Windows 10! Should I have not installed that build? And what can I do to get rib of it? Because it said Windows Install was recommended. On Saturday, March 28, 2020, 08:09:15 PM EDT, Richard Shaw hobbes1069@gmail.com wrote:

Chirp definitely won't work on Fedora 32 but should on Fedora 31, which is what I'm running (and I'm the maintainer). I would guess that perhaps you have some packages that didn't upgrade properly? What does "dnf distro-sync" show? Thanks,RichardKF5OIM_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Darrell Christopher at onebodyus@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Fred

5:53 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Sat, 28 Mar 2020 19:08:50 -0500 Richard Shaw hobbes1069@gmail.com wrote:

...

Chirp definitely won't work on Fedora 32 but should on Fedora 31, which is what I'm running (and I'm the maintainer).

I would guess that perhaps you have some packages that didn't upgrade properly?

What does "dnf distro-sync" show?

Thanks, Richard KF5OIM

[fred@m5a97r2 ~]$ sudo dnf distro-sync Last metadata expiration check: 2:11:05 ago on Sat 28 Mar 2020 02:40:56 PM AKDT. Dependencies resolved. Nothing to do. Complete! [fred@m5a97r2 ~]$

Fred

5:58 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Sat, 28 Mar 2020 19:08:50 -0500 Richard Shaw hobbes1069@gmail.com wrote:

...

Chirp definitely won't work on Fedora 32 but should on Fedora 31, which is what I'm running (and I'm the maintainer).

I would guess that perhaps you have some packages that didn't upgrade properly?

What does "dnf distro-sync" show?

Thanks, Richard KF5OIM

[fred@m5a97r2 ~]$ sudo dnf distro-sync Last metadata expiration check: 2:11:05 ago on Sat 28 Mar 2020 02:40:56 PM AKDT. Dependencies resolved. Nothing to do. Complete! [fred@m5a97r2 ~]$

Hit send by mistake.

Thank you Richard. I knew a maintainer for Fedora was here but couldn't remember you name.

Fred

Richard Shaw

6:17 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Sat, Mar 28, 2020 at 7:58 PM Fred fredferickson@gmail.com wrote:

...

On Sat, 28 Mar 2020 19:08:50 -0500 Richard Shaw hobbes1069@gmail.com wrote:

...
Chirp definitely won't work on Fedora 32 but should on Fedora 31, which is what I'm running (and I'm the maintainer).

I would guess that perhaps you have some packages that didn't upgrade properly?

[fred@m5a97r2 ~]$ sudo dnf distro-sync Last metadata expiration check: 2:11:05 ago on Sat 28 Mar 2020 02:40:56 PM AKDT. Dependencies resolved. Nothing to do. Complete!

Hit send by mistake.

Thank you Richard. I knew a maintainer for Fedora was here but couldn't remember you name.

Not sure what the problem is without more info then. It should work on Fedora 31. It works for me. Perhaps try a:

# dnf reinstall chirp

Thanks, RIchard KF5OIM

Fred

9 Apr 9 Apr

8:33 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Sat, 28 Mar 2020 20:17:49 -0500 Richard Shaw hobbes1069@gmail.com wrote:

...

On Sat, Mar 28, 2020 at 7:58 PM Fred fredferickson@gmail.com wrote:

...
On Sat, 28 Mar 2020 19:08:50 -0500 Richard Shaw hobbes1069@gmail.com wrote:

...
Chirp definitely won't work on Fedora 32 but should on Fedora 31, which is what I'm running (and I'm the maintainer).

I would guess that perhaps you have some packages that didn't upgrade properly?

[fred@m5a97r2 ~]$ sudo dnf distro-sync Last metadata expiration check: 2:11:05 ago on Sat 28 Mar 2020 02:40:56 PM AKDT. Dependencies resolved. Nothing to do. Complete!

Hit send by mistake.

Thank you Richard. I knew a maintainer for Fedora was here but couldn't remember you name.

Not sure what the problem is without more info then. It should work on Fedora 31. It works for me. Perhaps try a:

# dnf reinstall chirp

Thanks, RIchard KF5OIM

Sorry to have taken so long to reply. Had some issues come up that required my attention so couldn't spend any time on the computer...

I don't "install" Chirp. I use this wget command from a directory named chirp - changing the date to match the latest daily build:

wget https://trac.chirp.danplanet.com/chirp_daily/LATEST/chirp-daily-20200409.tar...

Then I un-tar the file and run the script file chirpw.

I've done this for several years in Fedora. Think I'll just wait for F32 to be officially released, then get serious about solving the problem (if it still exists). I have another machine available if I need to run Chrip.

Thanks for the help.

Fred, KL7FE

Richard Shaw

10 Apr 10 Apr

5:22 a.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Thu, Apr 9, 2020 at 10:34 PM Fred fredferickson@gmail.com wrote:

...

I don't "install" Chirp. I use this wget command from a directory named chirp - changing the date to match the latest daily build:

wget https://trac.chirp.danplanet.com/chirp_daily/LATEST/chirp-daily-20200409.tar...

Then I un-tar the file and run the script file chirpw.

Perhaps you're just missing a python dependency then? You could install the package just to see if any additional packages are pulled in.

Thanks, Richard

Joe Osborne

28 Mar 28 Mar

9:59 p.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Sat, Mar 28, 2020 at 15:52 Tony Fuller goldstar611@hotmail.com wrote:

...

I fully believe it is your latter guess, that Fedora 32 is missing python2, but I am not a Fedora user and am not familiar with their packaging. If you search the list archive you will see mails about Fedora (and other distros) removing python2 by default.

I am testing Ubuntu 20.04 (Focal Fossa) and although python2 is not installed by default, I can still get it by running apt install python2. Well just have to see if that still works next month when Canonical releases.

Tony

*From:* chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> on behalf of Fred < fredferickson@gmail.com> *Sent:* Saturday, March 28, 2020 6:41:37 PM *To:* chirp_users@intrepid.danplanet.com < chirp_users@intrepid.danplanet.com> *Subject:* [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

After the upgrade, Chirp and a Solitary game which is written in Python no longer worked so I upgraded to the new beta version Fedora 32. This morning, the developers released an update which included many Python changes which fixed the Solitary game but sadly, not Chirp.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

[fred@m5a97r2 chirp-daily]$ ./chirpw -v Traceback (most recent call last): File "./chirpw", line 20, in <module> from chirp import chirp_common File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979 except errors.InvalidDataError, e: ^ SyntaxError: invalid syntax [fred@m5a97r2 chirp-daily]$

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

A bit of an aside: Is this a Python issue in Chirp or a missing Python 2 file in Fedora 32? I notice that when the command "dnf list --installed | grep python" there is a python3.x86_64, but the python2 file is named python27.x86_64. There is no python2.x86_64 file but there is in Fedora 30 a file python2.x86_64. Although, the which command shows both a /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There are several link files in /usr/bin/ with python names that seem to be new additions and probably sort all that out though.

Thanks for the help.

Fred _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

*From:* chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> on behalf of Fred < fredferickson@gmail.com> *Sent:* Saturday, March 28, 2020 6:41:37 PM *To:* chirp_users@intrepid.danplanet.com < chirp_users@intrepid.danplanet.com> *Subject:* [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

After the upgrade, Chirp and a Solitary game which is written in Python no longer worked so I upgraded to the new beta version Fedora 32. This morning, the developers released an update which included many Python changes which fixed the Solitary game but sadly, not Chirp.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

[fred@m5a97r2 chirp-daily]$ ./chirpw -v Traceback (most recent call last): File "./chirpw", line 20, in <module> from chirp import chirp_common File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979 except errors.InvalidDataError, e: ^ SyntaxError: invalid syntax [fred@m5a97r2 chirp-daily]$

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

A bit of an aside: Is this a Python issue in Chirp or a missing Python 2 file in Fedora 32? I notice that when the command "dnf list --installed | grep python" there is a python3.x86_64, but the python2 file is named python27.x86_64. There is no python2.x86_64 file but there is in Fedora 30 a file python2.x86_64. Although, the which command shows both a /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There are several link files in /usr/bin/ with python names that seem to be new additions and probably sort all that out though.

Thanks for the help.

Fred _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

*From:* chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> on behalf of Fred < fredferickson@gmail.com> *Sent:* Saturday, March 28, 2020 6:41:37 PM *To:* chirp_users@intrepid.danplanet.com < chirp_users@intrepid.danplanet.com> *Subject:* [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30

Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

After the upgrade, Chirp and a Solitary game which is written in Python no longer worked so I upgraded to the new beta version Fedora 32. This morning, the developers released an update which included many Python changes which fixed the Solitary game but sadly, not Chirp.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

[fred@m5a97r2 chirp-daily]$ ./chirpw -v Traceback (most recent call last): File "./chirpw", line 20, in <module> from chirp import chirp_common File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979 except errors.InvalidDataError, e: ^ SyntaxError: invalid syntax [fred@m5a97r2 chirp-daily]$

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

A bit of an aside: Is this a Python issue in Chirp or a missing Python 2 file in Fedora 32? I notice that when the command "dnf list --installed | grep python" there is a python3.x86_64, but the python2 file is named python27.x86_64. There is no python2.x86_64 file but there is in Fedora 30 a file python2.x86_64. Although, the which command shows both a /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There are several link files in /usr/bin/ with python names that seem to be new additions and probably sort all that out though.

Thanks for the help.

Fred _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to godzilla49 at godzilla49@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

-- "*Proverbs don't get to be proverbs by being wrong*" - Me

Darrell & Sandy

29 Mar 29 Mar

10:03 a.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

But I a not running Linux, I have Windows 10, so how do get rid of the build from my Baofeng? On Sunday, March 29, 2020, 01:00:06 AM EDT, Joe Osborne godzilla49@gmail.com wrote:

On Sat, Mar 28, 2020 at 15:52 Tony Fuller goldstar611@hotmail.com wrote:

I fully believe it is your latter guess, that Fedora 32 is missing python2, but I am not a Fedora user and am not familiar with their packaging. If you search the list archive you will see mails about Fedora (and other distros) removing python2 by default. I am testing Ubuntu 20.04 (Focal Fossa) and although python2 is not installed by default, I can still get it by running apt install python2. Well just have to see if that still works next month when Canonical releases. Tony From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Fred fredferickson@gmail.com Sent: Saturday, March 28, 2020 6:41:37 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30 Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

Thanks for the help.

From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Fred fredferickson@gmail.com Sent: Saturday, March 28, 2020 6:41:37 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30 Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

Thanks for the help.

Fred _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Fred fredferickson@gmail.com Sent: Saturday, March 28, 2020 6:41:37 PM To: chirp_users@intrepid.danplanet.com chirp_users@intrepid.danplanet.com Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30 Since I am mostly confined to home due to the restrictions caused by the virus outbreak, I decided to up grade my Linux system from Fedora 30 to the current version which is Fedora 31.

So, maybe the Chirp developers will have the answer. Here is the output of starting the 20200227 Chirp version with -v:

The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a Chirp run before upgrading from Fedora 30.

Thanks for the help.

Fred _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to godzilla49 at godzilla49@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

-- "Proverbs don't get to be proverbs by being wrong" - Me _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Darrell Christopher at onebodyus@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Richard Shaw

10:05 a.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

On Sun, Mar 29, 2020 at 12:04 PM Darrell & Sandy via chirp_users < chirp_users@intrepid.danplanet.com> wrote:

...

But I a not running Linux, I have Windows 10, so how do get rid of the build from my Baofeng?

Please note the subject of this thread, which is "Chirp will not start in Fedora 31 nor 32"

If you have a question about chip and windows 10 I would recommend starting a new thread, not hijacking an existing thread.

Thanks, Richard KF5OIM

Nigel A. Gunn G8IFF/W8IFF

10:07 a.m.

New subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 b

Chirp is functionally identical on all operating systems. The programming of your Baofeng will be the same on all versions.

...

On 29 March 2020 at 13:03 Darrell & Sandy via chirp_users chirp_users@intrepid.danplanet.com wrote:

But I a not running Linux, I have Windows 10, so how do get rid of the build from my Baofeng?


On Sunday, March 29, 2020, 01:00:06 AM EDT, Joe Osborne <godzilla49@gmail.com> wrote:




On Sat, Mar 28, 2020 at 15:52 Tony Fuller < goldstar611@hotmail.com mailto:goldstar611@hotmail.com > wrote:

    > >

...

    I fully believe it is your latter guess, that Fedora 32 is missing python2, but I am not a Fedora user and am not familiar with their packaging. If you search the list archive you will see mails about Fedora (and other distros) removing python2 by default.

    I am testing Ubuntu 20.04 (Focal Fossa) and although python2 is not installed by default, I can still get it by running apt install python2. Well just have to see if that still works next month when Canonical releases.

    Tony 

    ---------------------------------------------
    From: chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com > on behalf of Fred <fredferickson@gmail.com mailto:fredferickson@gmail.com >
    Sent: Saturday, March 28, 2020 6:41:37 PM
    To: chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com >
    Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30


    Since I am mostly confined to home due to the restrictions caused by
    the virus outbreak, I decided to up grade my Linux system from Fedora
    30 to the current version which is Fedora 31.

    After the upgrade, Chirp and a Solitary game which is written in Python
    no longer worked so I upgraded to the new beta version Fedora 32. This
    morning, the developers released an update which included many Python
    changes which fixed the Solitary game but sadly, not Chirp.

    So, maybe the Chirp developers will have the answer. Here is the output
    of starting the 20200227 Chirp version with -v:

    [fred@m5a97r2 chirp-daily]$ ./chirpw -v
    Traceback (most recent call last):
      File "./chirpw", line 20, in <module>
        from chirp import chirp_common
      File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979
        except errors.InvalidDataError, e:
                                      ^
    SyntaxError: invalid syntax
    [fred@m5a97r2 chirp-daily]$

    The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a
    Chirp run before upgrading from Fedora 30.

    A bit of an aside:
    Is this a Python issue in Chirp or a missing Python 2 file in Fedora
    32? I notice that when the command "dnf list --installed | grep python"
    there is a python3.x86_64, but the python2 file is named
    python27.x86_64. There is no python2.x86_64 file but there is in Fedora
    30 a file python2.x86_64. Although, the which command shows both a
    /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There
    are several link files in /usr/bin/ with python names that seem to be
    new additions and probably sort all that out though.

    Thanks for the help.

    Fred
    _______________________________________________
    chirp_users mailing list
    chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
    http://intrepid.danplanet.com/mailman/listinfo/chirp_users
    This message was sent to Tony F at goldstar611@hotmail.com mailto:goldstar611@hotmail.com
    To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com


    ---------------------------------------------
    From: chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com > on behalf of Fred <fredferickson@gmail.com mailto:fredferickson@gmail.com >
    Sent: Saturday, March 28, 2020 6:41:37 PM
    To: chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com >
    Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30


    Since I am mostly confined to home due to the restrictions caused by
    the virus outbreak, I decided to up grade my Linux system from Fedora
    30 to the current version which is Fedora 31.

    After the upgrade, Chirp and a Solitary game which is written in Python
    no longer worked so I upgraded to the new beta version Fedora 32. This
    morning, the developers released an update which included many Python
    changes which fixed the Solitary game but sadly, not Chirp.

    So, maybe the Chirp developers will have the answer. Here is the output
    of starting the 20200227 Chirp version with -v:

    [fred@m5a97r2 chirp-daily]$ ./chirpw -v
    Traceback (most recent call last):
      File "./chirpw", line 20, in <module>
        from chirp import chirp_common
      File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979
        except errors.InvalidDataError, e:
                                      ^
    SyntaxError: invalid syntax
    [fred@m5a97r2 chirp-daily]$

    The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a
    Chirp run before upgrading from Fedora 30.

    A bit of an aside:
    Is this a Python issue in Chirp or a missing Python 2 file in Fedora
    32? I notice that when the command "dnf list --installed | grep python"
    there is a python3.x86_64, but the python2 file is named
    python27.x86_64. There is no python2.x86_64 file but there is in Fedora
    30 a file python2.x86_64. Although, the which command shows both a
    /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There
    are several link files in /usr/bin/ with python names that seem to be
    new additions and probably sort all that out though.

    Thanks for the help.

    Fred
    _______________________________________________
    chirp_users mailing list
    chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
    http://intrepid.danplanet.com/mailman/listinfo/chirp_users
    This message was sent to Tony F at goldstar611@hotmail.com mailto:goldstar611@hotmail.com
    To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com

    ---------------------------------------------
    From: chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com > on behalf of Fred <fredferickson@gmail.com mailto:fredferickson@gmail.com >
    Sent: Saturday, March 28, 2020 6:41:37 PM
    To: chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com >
    Subject: [chirp_users] Chirp will not start in Fedora 31 nor 32 beta. Works fine in 30


    Since I am mostly confined to home due to the restrictions caused by
    the virus outbreak, I decided to up grade my Linux system from Fedora
    30 to the current version which is Fedora 31.

    After the upgrade, Chirp and a Solitary game which is written in Python
    no longer worked so I upgraded to the new beta version Fedora 32. This
    morning, the developers released an update which included many Python
    changes which fixed the Solitary game but sadly, not Chirp.

    So, maybe the Chirp developers will have the answer. Here is the output
    of starting the 20200227 Chirp version with -v:

    [fred@m5a97r2 chirp-daily]$ ./chirpw -v
    Traceback (most recent call last):
      File "./chirpw", line 20, in <module>
        from chirp import chirp_common
      File "/home/fred/chirp/chirp-daily/chirp/chirp_common.py", line 979
        except errors.InvalidDataError, e:
                                      ^
    SyntaxError: invalid syntax
    [fred@m5a97r2 chirp-daily]$

    The ~/.chirp/debug.log entries are dated 2020-03-14 which are from a
    Chirp run before upgrading from Fedora 30.

    A bit of an aside:
    Is this a Python issue in Chirp or a missing Python 2 file in Fedora
    32? I notice that when the command "dnf list --installed | grep python"
    there is a python3.x86_64, but the python2 file is named
    python27.x86_64. There is no python2.x86_64 file but there is in Fedora
    30 a file python2.x86_64. Although, the which command shows both a
    /usr/bin/python3 and a /usr/bin/python2 file exist in Fedora 32. There
    are several link files in /usr/bin/ with python names that seem to be
    new additions and probably sort all that out though.

    Thanks for the help.

    Fred
    _______________________________________________
    chirp_users mailing list
    chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
    http://intrepid.danplanet.com/mailman/listinfo/chirp_users
    This message was sent to Tony F at goldstar611@hotmail.com mailto:goldstar611@hotmail.com
    To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
    _______________________________________________
    chirp_users mailing list
    chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
    http://intrepid.danplanet.com/mailman/listinfo/chirp_users
    This message was sent to godzilla49 at godzilla49@gmail.com mailto:godzilla49@gmail.com
    To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com

>     --

" Proverbs don't get to be proverbs by being wrong " - Me

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Darrell Christopher at onebodyus@yahoo.com mailto:onebodyus@yahoo.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1 937 825 5032 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net

1741

Age (days ago)

1754

Last active (days ago)

List overview

Download

12 comments

6 participants

tags (0)

participants (6)

Darrell & Sandy
Fred
Joe Osborne
Nigel A. Gunn G8IFF/W8IFF
Richard Shaw
Tony Fuller