search

goldstar611 / chirp

CHIRP mirror. Please open CHIRP-snap issues here!
https://github.com/goldstar611/chirp/issues
GNU General Public License v3.0
1 stars 1 forks source link

Chirp-Snap Updates #3

Closed tpalmatier closed 1 year ago

tpalmatier commented 1 year ago

This snap updated on 02/10/23. There have been updates since then but the snap is not updating

goldstar611 commented 1 year ago

Hey Terry, I don't know exactly when snaps will update on users computers but you can always open up a terminal and run snap refresh to force an update of your installed snaps.

There are two "channels" that can be chosen when you install from the snap store, stable vs edge. edge will always be more up to date than stable at the moment because I have to go into the snap interface and manually "promote" builds from edge to stable. I plan on writing a script to do this so I won't have to worry about it but I haven't got to it yet.

Let me know if the snap refresh command works for you.

Tony

goldstar611 commented 1 year ago

Linking this here so I can refer back to it later: https://snapcraft.io/docs/release-management

tpalmatier commented 1 year ago

Thanks for the update Tony (no pun intended).

Using the snap refresh command in the CLI is how I always do it. I guess I didn't know there was any other way to do it.

Your hard work it greatly appreciated.

Terry AC8NR

From: Tony F @.> Sent: Monday, February 13, 2023 10:09 AM To: goldstar611/chirp @.> Cc: tpalmatier @.>; Author @.> Subject: Re: [goldstar611/chirp] Chirp-Snap Updates (Issue #3)

Hey Terry, I don't know exactly when snaps will update on users computers but you can always open up a terminal and run snap refresh to force an update of your installed snaps.

There are two "channels" that can be chosen when you install from the snap store, stable vs edge. edge will always be more up to date than stable at the moment because I have to go into the snap interface and manually "promote" builds from edge to stable. I plan on writing a script to do this so I won't have to worry about it but I haven't got to it yet.

Let me know if the snap refresh command works for you.

Tony

— Reply to this email directly, view it on GitHubhttps://github.com/goldstar611/chirp/issues/3#issuecomment-1428105373, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALWPCIGWYK75LOV3RI3WAPTWXJFEFANCNFSM6AAAAAAUZX6Z2U. You are receiving this because you authored the thread.Message ID: @.***>

goldstar611 commented 1 year ago

Using the snap refresh command in the CLI is how I always do it. I guess I didn't know there was any other way to do it.

Sounds like you're doing it the right way. How many versions behind is your installation of CHIRP?

snap refresh should put you on either revision 518, 519 or 520 aka "snap-20230213+5ceff61d" depending on your CPU architecture. Those snap revisions correspond to tarballs for CHIRP-next-20230213

tpalmatier commented 1 year ago

It is up to date as of today. Thanks.

Terry AC8NR

From: Tony F @.> Sent: Monday, February 13, 2023 3:25 PM To: goldstar611/chirp @.> Cc: tpalmatier @.>; Author @.> Subject: Re: [goldstar611/chirp] Chirp-Snap Updates (Issue #3)

Using the snap refresh command in the CLI is how I always do it. I guess I didn't know there was any other way to do it.

Sounds like you're doing it the right way. How many versions behind is your installation of CHIRP?

snap refresh should put you on either revision 518, 519 or 520 aka "snap-20230213+5ceff61d" depending on your CPU architecture. Those snap revisions correspond to tarballs for CHIRP-next-20230213

— Reply to this email directly, view it on GitHubhttps://github.com/goldstar611/chirp/issues/3#issuecomment-1428632405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALWPCIGNPXAKOOXOF4JALVTWXKKFDANCNFSM6AAAAAAUZX6Z2U. You are receiving this because you authored the thread.Message ID: @.***>