Project

General

Profile

Actions

Bug #10391

closed

Install problems: no PPA, incorrect tar file name, dendance on version number

Added by Mark Whitis almost 2 years ago. Updated almost 2 years ago.

Status:
Not a bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/24/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
all
Platform:
Linux
Debug Log:
I read the instructions above:

Description

Chirp filename for linux is chirp-version.tar.gz not chirp-next-version.tar.tz as it says in documentation (https://chirp.danplanet.com/projects/chirp/wiki/ChirpOnLinux) . I thought that would download chirp-obsolete instead. Either fix the filename or fix the documentation. And fixing the name at this point will probably break any scripts people have made (including the one below in this bug report), especially since it has been broken for some time.

Also, a filename that contains a version is highly problematic. the version number in your documentation was out of date. You can't easily have a script to download it automatically that won't break when you get the next version. And that script is only to work around the bug that you can no longer install the program with one or two commands using the native package manager like civilized people do. People have hundreds or thousands of programs to install, often on many different machines, and they don't need to be dealing with this nonsense. And definitely don't need to put up with that when you are an emergency responder at an incident and need to reprogram a radio, which has happened.

Shouldn't need to do hacks like:

sudo bash -c 'version=$(lynx --dump --listonly --nonumbers https://trac.chirp.danplanet.com/chirp_next/ | fgrep "next-" | sort --version-sort | tail -1 | sed -e "s/next-//" | awk '"'"'{print $(NF-1)}'"'"' FS=/ -) ; echo $version; wget https://trac.chirp.danplanet.com/chirp_next/next-$version/chirp-$version.tar.gz; pip3 install chirp-$version.tar.gz'

And this is added to layer upon layer of compounding install bugs. I was only trying to download the file because of all the ways install has been broken.

Also, if you have to sink so low as to use pip3 to install (which historically conflicts with native packages when isntalling system wide), that didn't work when used as one normally would as your files aren't in the repository, you have to manually download them. "pip3 install chirp-next" is all you should have to type. And I certainly don't want to use a snap and deal with a stupid sandbox that prevents you from accessing serial devices and files (including if the files are put in a shared directory) and all the other problems that snap brings. Or flatpak.

And then there was the prior nonsense of having to download missing python files from google drive, which doesn't have

And there shouldn't be any desktop icon install nonsense as part of the instructions, that should be automatic.

there needs to be a chirp-next-daily PPA

At the very least, there needs to be a sequence of commands on the website that will cause the program to be properly installed system wide, unjailed, and won't break when you release a new version, and which will log all parts of the actions performed in the sudo logs.

ubuntu-22.04.x

Actions #1

Updated by Dan Smith almost 2 years ago

  • Status changed from New to Not a bug
Actions

Also available in: Atom PDF