Bump Flatpak runtime versions for new projects

[rmartin16]

Changes

• Bump Flatpak runtime versions
  • org.freedesktop.Platform: 22.08 -> 23.08
  • org.kde.Platform: 6.4 -> 6.6
  • org.gnome.Platform: 44 -> 45

Notes

org.gnome.Platform==45, org.kde.Platform==6.6, and org.freedesktop.Platform==23.08 do not have libcrypt.so.1 and Flatpak builds are failing because Standalone Python is still looking for it.... I was under the impression that Standalone Python was dropping its dependency on this ancient library....but maybe I misunderstood something....

libcrypt.so was dropped for Python 3.10, 3.9, and 3.8 with indygreg/python-build-standalone@80cd87f and released in 20240107.

Dependencies

• Python 3.8, 3.9, and 3.10 link libcrypt.so.1 unexpectedy in releases 20230726 and later indygreg/python-build-standalone#197
• Bump Python from 20231002 to 20240107 briefcase-linux-flatpak-template#32

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[rmartin16]

I've narrowed this down to being a problem for Python 3.8, 3.9, and 3.10; when using Python 3.11 and 3.12, the dependency on libcrypt.so.1 is absent. This is true for both releases 20231002 and 20230826.

❯ ldd ./build/flatpaktest/linux/flatpak/support/python/bin/python3.11
	linux-vdso.so.1 (0x00007ffeda74f000)
	/home/user/tmp/beeware/flatpaktest/./build/flatpaktest/linux/flatpak/support/python/bin/../lib/libpython3.11.so.1.0 (0x00007f6859c00000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f685b42f000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f685b42a000)
	libutil.so.1 => /lib64/libutil.so.1 (0x00007f685b425000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f6859b1f000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f685b41e000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f685993d000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f685b44f000)

❯ ldd ./build/flatpaktest/linux/flatpak/support/python/bin/python3.10
	linux-vdso.so.1 (0x00007ffe1c6ef000)
	/home/user/tmp/beeware/flatpaktest/./build/flatpaktest/linux/flatpak/support/python/bin/../lib/libpython3.10.so.1.0 (0x00007ffad6800000)
	libcrypt.so.1 => not found
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ffad7e9a000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007ffad7e95000)
	libutil.so.1 => /lib64/libutil.so.1 (0x00007ffad7e90000)
	libm.so.6 => /lib64/libm.so.6 (0x00007ffad7dad000)
	librt.so.1 => /lib64/librt.so.1 (0x00007ffad7da8000)
	libc.so.6 => /lib64/libc.so.6 (0x00007ffad661e000)
	/lib64/ld-linux-x86-64.so.2 (0x00007ffad7eba000)
	libcrypt.so.1 => not found

The development in Standalone Python that claimed to remove this dependency didn't make any carve outs for older Python; so, I'm not sure if this in intentional or what yet.

[rmartin16]

Feedback in indygreg/python-build-standalone#173 (comment) confirms that Python 3.8, 3.9, and 3.10 should not be linking libcrypt.so.1 like this. I created indygreg/python-build-standalone#197 to document this. Elsewhere indygreg commented they won't be able to make another release until Christmas or later (not that I consider that a committed timeline or anything).

As a note, org.kde.Platform==6.4 (the current version used in the template) is EOL; 6.5 doesn't have this issue....but I also can't find the EOL schedule for the KDE runtimes...

[freakboy3742]

I've clarified the specific versions in the release note; but otherwise 👍