-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.3.0 #7
Conversation
olof-nord
commented
Jun 22, 2022
- Update axolotl version to 1.3.0
- Update Electron to 18.0.1
- re-generate axolotl, axolotl-web and crayfish sources
- Update flatpak-builder-tools git submodule
Started test build 97115 |
* Update axolotl version to 1.3.0 * Update Electron to 18.0.1 * re-generate axolotl, axolotl-web and crayfish sources * Update flatpak-builder-tools
Build 97115 failed |
…, ignore https certificates. The path is git+https://github.com/NikolaBalaban/mic-recorder-to-mp3.git The error message is: The authenticity of host 'github.com (140.82.114.4)' can't be established. ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. This key is not known by any other names
bot, build |
Queued test build for org.nanuc.Axolotl. |
Started test build 97146 |
Build 97146 failed |
Started test build 97196 |
bot, build |
Queued test build for org.nanuc.Axolotl. |
Started test build 97198 |
Build 97196 failed |
Build 97198 failed |
Any progress on this? The 1.2.0 Flatpak does not work at all on my PinePhone:
and hence I would like to try out 1.3.0. (And there is no native package for Manjaro ARM, so the Flatpak is the only supported option.) |
Hello @kkofler, In theory the release was an easy one, but the axolotl frontend got a new dependency which was using a direct git repository as a source - this didnt work with the Flathub Node tooling. I know nanu-c has done some work to fix this recently, but on my side as I am on holiday I haven't given Axolotl as much time. The exact issue with the npm dependency is that the Flathub Node tooling unfortunately only supports a subset of the native npm dependency references. https+ssh or git@ etc. I have had a look into the python source code as to understand it better, its written in the top section in one of the main files. The main difficulty is effectively how long a flathub build takes, with an average time probably closer to 30 minutes, this makes each iteration drag on. |
See this issue for all details: |
The CAPTCHA issue you're describing was one of the issues solved with the 1.3.0 release, in this case its the packaging which is left to do. |
If you're comfortable building your own Flatpak build on your own, there is a "dev" Flatpak manifest set up in the axolotl repo, in the doc which also is in the axolotl repo you'll find info how to do it. From my experience doing it on a PinePhone it does take a very long time though. |
Upstream has now released 1.3.1 with the fix for Flatpak builds, when can we expect an update in Flathub? |
Returning from holiday, I believe once we have axolotl-chat/axolotl#874 merged, I can move on with a new Flathub release. Note that this PR is superseded by the 1.5.0 release in another branch. I do suspect that will end up being release 1.5.1 due to the needed adjustments though. |
Closing this PR in favour of the 1.5.1 release. |