Re: "Lagrange 1.18.2 released, mobile builds updated"

In: s/Lagrange

what is the simplest way to update from older versions on debian and ubuntu?

👻 naf

2024-10-13 · 2 years ago

5 Later Comments ↓

🌆 skyjake [OP/mod...] · 2024-10-14 at 04:32:

How did you install it previously?

🌆 skyjake [OP/mod...] · 2024-10-14 at 06:55:

There is a quick v1.18.3 release available due to a problem in the TUI builds with background colors when not using a 256 color palette.

— v1.18.3 on git.skyjake.fi

🐉 gyaradong · 2024-10-14 at 08:55:

Definitely fixed something for me. Haven't been able to Lagrange on Mobile for a few months now.

👻 naf · 2024-10-14 at 12:31:

I used the app Image. I downloaded now the new app Image and replaced the old. Maybe there would be an automatic way to update it when you make new releases. BTW thanks for the hardwork and great application.

🌆 skyjake [OP/mod...] · 2024-10-14 at 14:19:

@naf Updating AppImages can be automated with a tool called AppImageUpdate:

— https://github.com/AppImageCommunity/AppImageUpdate/releases/tag/2.0.0-alpha-1-20230526

You can find GUI and CLI versions of it there on GitHub. I tested upgrading the clagrange v1.18.0 AppImage to v1.18.3 and it worked well:

$ ./appimageupdatetool-x86_64.AppImage ./clagrange-1.18.0-x86_64.AppImage

🌒 s/Lagrange

🌆 skyjake: [mod...]

— v1.18.2 on git.skyjake.fi

Lagrange 1.18.2 released, mobile builds updated — I've done the whole gamut of builds tonight: desktop, terminal, and mobile. The changes are listed below. All platforms Misfin: URI format has changed to "misfin:address?message" instead of the previously used "misfin://address". The optional query string ("message") is used as the initial message contents if the upload dialog's text editor is empty....

💬 7 comments · 6 likes · 2024-10-13 · 2 years ago · #release