Greetings,

A new daily build of CHIRP is available.  This includes changes made
directly to the tree yesterday, and may include additional features,
bug fixes, and/or bugs.  If you are interested in trying it, grab it
from the following location:

  http://trac.chirp.danplanet.com/chirp_daily/daily-20220822


A list of the changes included in this build (since the last daily)
follows:

Changes for Build #695
[Dan Smith <[email protected]>] Merge pull request #29 
from goldstar611/snap_updates

snapcraft.yaml Updates

[Tony Fuller <[email protected]>] [snapcraft.yml] rsync shared files from 
$SNAP/share/ to $SNAP/usr/share/

It appears that CHIRP is being installed with a `prefix=/` instead of 
`prefix=/usr`
Rather than move a bunch of files around and change the entire snap, I'm 
rsync'ing $SNAP/share to $SNAP/usr/share

Open question at: https://forum.snapcraft.io/t/python-install-prefix/31248
What I believe is the python plugin handling the CHIRP install: 
https://github.com/snapcore/snapcraft/blob/main/snapcraft_legacy/plugins/v2/python.py
In response to: #1

[Tony Fuller <[email protected]>] [snapcraft.yml] Set in app version to 
be the date of build

[Dan Smith <[email protected]>] Fix style issues in previous commit

The de32861943bdc9c69313bf92a92728001d71f59b commit had long lines,
which this fixes.

[Ran Katz <[email protected]>] [tg_uv2p] (revised) Dont set a priority channel 
if empty or Broadcast-FM. Fixes fifth issue in #9939
Per Dan's suggestion changed implementation to a validation function and an 
exception to notify user of wrong input

[Ran Katz <[email protected]>] [TG-UV2+] adding missing log messages in 
set_settings()


_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to [email protected] at [email protected]
To unsubscribe, send an email to [email protected]
To report this email as off-topic, please email 
[email protected]
Searchable archive: 
https://www.mail-archive.com/[email protected]

Reply via email to