Nightly flatpak builds

[Atreides]

Woops, too late for that. I managed to rollback the flatpak install to the 20.08 versions and all is fine for now.

By June I'll be upgrading my Debian 9 (updates for it end then) to 10 and that might just fix this for me. I suspect that freedesktop 21.08 and Deb 9 aren't fully compatible (a bug but one that might be moot soon) since I have had problems with the flatpak Firefox that uses 21. (turning off hardware accel in firefox fixed it) I've delayed getting Deb 10 since I should backup my files first and I've been negligent there. With a new PC you don't feel much need to backup... but that is changing.

And please don't get the impression I'm careless about backing up. I have backups going back to 1982. :) Yes it is 2 audio cassettes from my Atari 800.

[Atreides]

Question about the wesnoth-origin server. How was it set up? Asking for a third party that is interested in doing the same for another game.

[loonycyborg]

I followed this guide: https://blogs.gnome.org/alexl/2017/02/1 ... epository/

[Atreides]

I followed this guide: https://blogs.gnome.org/alexl/2017/02/1 ... epository/

Thanks I'll pass it along.

[Atreides]

I just tried to update flatpak to get the latest 1.17 but it gave me a shock saying I need to install 23.08 of freedesktop to run stable (that's 1.16.10 right?) even though the current 1.16.10 runs on 22.08.

Confused.

Why do I need 23.08 when 22.08 works? Sounds contradictory.

I am afraid to install 23.08 because when I installed 22 in debian 9 it broke wesnoth and I had to rollback to 21. I am now on debian 10 (yes still behind but a little less) and 22 works with it. I am worried debian 10 and 23 won't work and it will break wesnoth again.

If it's a choice between breaking 1.16 and having the latest 1.17 I will chose 1.16 of course.

Oh, no need to tell me to upgrade Debian to 11. I will as soon as I can but eh...

[Pentarctagon]

Well, it was updated to 23.08 and then rolled back to 22.08 for now since it turns out the Freedesktop SDK for 23.08 accidentally stopped building SDL2 with webp (and tiff) support. #8040

[Atreides]

I dug into flatpak a little deeper myself and found that 1.17 was still using 22.08! I also learned how to manually update only those I want to so I updated 1.17 and Firefox (which also still uses 22.08). Widelands & Freeorion are actually still using 20.08 and 21.08 (even though they are "unsupported" oh my) so older is as good as newer. : )

Next I'll try and see if flatpak can be configured to freeze something so it doesn't get included in the updates anymore. I'll do that for 1.16.10 if I can, as I am sure that's the last version. I can later unfreeze it when I move to Debian 11.

[Atreides]

I now get this error trying a flatpak update for the master branch:

Looking for updates…
F: Error updating remote metadata for 'wesnoth-origin': GPG signatures found, but none are in trusted keyring
F: Warning: Treating remote fetch error as non-fatal since app/org.wesnoth.Wesnoth/x86_64/master is already installed: Unable to load summary from remote wesnoth-origin: GPG signatures found, but none are in trusted keyring
F: Warning: Can't find app/org.wesnoth.Wesnoth/x86_64/master metadata for dependencies: Unable to load metadata from remote wesnoth-origin: summary fetch error: GPG signatures found, but none are in trusted keyring

keyring? Wot dat?

[loonycyborg]

When gpg key expires I have to extend its lifetime and update GPG entry in http://files.wesnoth.org/wesnoth-nightly.flatpakref (I already updated it). On your end you need to first uninstall and then reinstall from updated .flatpakref . I probably should make key non-expiring. GPG recommends making them expire but flatpak use of it is different than most other GPG use cases..

[Atreides]

Thanks, by the way, will there be a 1.16 branch for flatpak like there is for 1.14?

[loonycyborg]

I'll need to make one on wesnoth.org since flathub doesn't allow making separate branches anymore. See https://github.com/flathub/flathub/issues/5264

[Atreides]

Yikes. The flatpak police are coming for my 1.14 install! Run away! ;- )

[Atreides]

When gpg key expires I have to extend its lifetime and update GPG entry in http://files.wesnoth.org/wesnoth-nightly.flatpakref (I already updated it). On your end you need to first uninstall and then reinstall from updated .flatpakref . I probably should make key non-expiring. GPG recommends making them expire but flatpak use of it is different than most other GPG use cases..

A note for any future searchers with this problem:
I finally fixed this but not by uninstalling, instead I found I can modify the flatpak config to ignore GPG and that appears to work. I only did that for wesnoth-origin which of course only has the one package. : )

This is the command I used:

Code: Select all

flatpak remote-modify --no-gpg-verify wesnoth-origin

Ironically I'm not actually updating master since a long while since the version I have is roughly equivalent to (and works like) 1.17.26 which has to serve me as 1.18 for a while still until I find an alternate way (other than flatpak) to keep 1.16. Compiling (ugh) seems to be my best bet. First and last time I compiled something was around 2005 when I compiled VGA Planets for MS-DOS. The errors make me nervous even though it works. I've never been able to take errors lightly.

[gnombat]

Compiling (ugh) seems to be my best bet. First and last time I compiled something was around 2005 when I compiled VGA Planets for MS-DOS. The errors make me nervous even though it works. I've never been able to take errors lightly.

Compiling things on Linux is usually simpler than compiling on Microsoft platforms like Windows or (shudder) DOS.

[Soliton]

Ironically I'm not actually updating master since a long while since the version I have is roughly equivalent to (and works like) 1.17.26 which has to serve me as 1.18 for a while still until I find an alternate way (other than flatpak) to keep 1.16.

You can just download a flatpak bundle from https://github.com/wesnoth/wesnoth/acti ... 9721362640 for example. (I think you need to be signed in to github though.)