On 2022-01-06 10:41 a.m., Roy J. Tellason, Sr. wrote: > On Thursday 06 January 2022 07:20:43 am Greg Wooledge wrote: >> On Thu, Jan 06, 2022 at 01:01:07AM -0500, Roy J. Tellason, Sr. wrote: >>> So I downloaded the current version of the program. This gets incremental >>> upgrades all the time, and the latest one is chirp20220103, which I >>> downloaded. When I went to invoke it directly, there was an error about >>> some missing python bit. Going into synaptic, I didn't see chirp listed at >>> all, though it did show up when I did a search, and installing that package >>> got me a version from 2018! (Why the repository can't be more up to date >>> than that I don't know.) This also provided the missing python bit. So I >>> edited the application menu entry to point to the new version, and it now >>> works. >> Debian goal is to be stable, not the latest version available. Also, running Debian version 8 or 9 (9 being old-old-stable or Stretch) when we are now at 11 is doing two things : 1st - it disallow you any type of complaint regarding having old software, because you have made such situation and supported it for many years from now. 2nd - it prevent you from getting updates when they get out. >> Going by the version number, that looks like it's from 2020. Are you >> not running the current stable release of Debian? > > No, I'm not. I had been updating packages from time to time using synaptic, under the mistaken impression that this would keep things current, and then I found that not to be the case. I did an upgrade from 8 -> 9, and that's where things are sitting at the moment. I've been encouraged to get with current stable, which is what, 11 at this point? I'll get there, but slowly, so I can see what's changed at each step of the process and fix that which ends up broken> Stuff won't be broken if you take a day to create a backup of you data, do a complete installation of Buster / Bullseye. And restore your data. You can use a spare partition to save your data, mounting later and copy those data. You are creating a messed up hell by using the path you choose. You'll end up with risking many problem of software having older configuration (all the ones you manually modified the files in /etc). It's time to make the jump (and not from a bridge). >> As far as running your chirp20220103 version, seeing the errors might be >> helpful. I'm not a python expert myself, but I'd be willing to bet that >> someone on this list would be able to advise you if we could see the >> actual error message. > > It was missing the python-serial package, which installing the older version in synaptic got me, so it's working now. But the version that synaptic installed was from 2018! That one isn't going to support this radio, which is a tri-bander, hence my move to the current version... You are mostly causing your self most of the problem you will get. You repeated many time "I don't know" and this seems to support a "I'm looking into trying to understand why". But even worse, you are mixing software version from outside source (like what you seem to be doing with python-serial) and the one supplied by Debian. You are only creating a messed up system that no one will understand, except yourself (and I wouldn't bet on this one). > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature