zyli

I now understand that you prefer PureOS because it's "Pure." I was surprised that you were interested in flatpak – on the one hand, "Pure" and on the other, flatpak – but let's leave that aside. Just because Pure hasn't released an updated ISO image for two and a half years doesn't mean they're not doing anything. I looked at their repositories: https://repo.pureos.net/pureos/pool/main/ You can see that they're releasing newer packages there: https://repo.pureos.net/pureos/pool/main/b/base-files/ There's also 0ad: https://repo.pureos.net/pureos/pool/main/0/0ad/ Therefore, I suspect you didn't read the PureOS documentation about how to update releases. PureOS is based on Debian, and I suspect it also uses Debian release codenames. You're probably stuck on Bullseye – hence the version 0.23.0 available. https://packages.debian.org/bullseye/0ad I would try this: I would check the entries in the '/etc/apt/sources.list' file – if the word 'bullseye' is there, that's the cause. In that case, you should update sequentially: bullseye -> bookworm -> trixie, rather than straight to trixie. But to be sure, I would read the PureOS documentation. If this update were successful, I would download three files: 0ad, 0ad-data, and 0ad-data-common (version 0.27.1-3 from Debian trixie-backports): https://packages.debian.org/trixie-backports/0ad and I would install them manually (dpkg -i file.deb). I would then have the latest 0ad for PureOS – but this is just my guess, as I've never used PureOS. In summary – first, issue the following commands: cat /etc/os-release cat /etc/apt/sources.list Regarding your question, I believe there are currently no Linux distributions that meet Richard Stallman's rules. Which distribution doesn't use proprietary firmware? Best regards Postscriptum --------------- PureOS does not use Debian's code names, but its own: Amber, Byzantium, Crimson, and Dawn. https://repo.pureos.net/pureos/dists/ Dawn is probably the equivalent of Debian's sid (perpetually unstable). So you need to read up on it. My guess: you have Amber, but you should have Crimson. Check it out.

According to https://en.wikipedia.org/wiki/PureOS In my opinion, it's time to choose something else. This is what the 0ad versions supported by Linux distributions look like. https://repology.org/project/0ad/versions I suggest stable Debian 13.1 Trixie: https://cdimage.debian.org/cdimage/release/13.1.0/amd64/iso-dvd/ https://packages.debian.org/trixie-backports/0ad Regards.

Thank you for the information. Regards.

I'm compiling 0ad on Debian ('svn update' commands, etc.). The version hasn't changed for a while now (October 18th?). I see: According to '0ad/trunk/build/build_version/build_version.txt': Similarly, in '~/.local/state/0ad/log/userreport_hwdetect.txt'. However, on the website https://gitea.wildfiregames.com/0ad/0ad, there are new commits almost daily (last one: cb58116270). I also found this: https://gitea.wildfiregames.com/0ad/0ad/src/branch/release-0.28.0 Hence my questions: Does this mean that version 0.28.0 will be released soon? But the numbering was supposed to be different – 28.0?

Replay2025-07-13_0001.zip

Compilation: 0 A.D.0.27.1-rc2, Debian 12.11 Bookworm (+rustup) To me, everything works as expected, only "Petra" informs: Regards

What version of Ubuntu do you have? Secondly: building from source is not that scary – you just have to write it down in steps. Best regards. PS. I would avoid Flatpak.

1. Zram? In my opinion, this invention should be gotten rid of. It may be the cause of delays. The Linux kernel has everything it needs. Now, memories are fast - why waste time on additional compression and decompression? This whole zram is an illusion - if someone has too little RAM, it is better to add physical memory. If anything - 'tmpfs' is more necessary. 2. Compiling 0ad is not difficult. I recommend compiling ver. 0.27.1 rc: https://releases.wildfiregames.com/rc/ But on Debian Bookworm (12.11) you will not compile this version, because the requirements for 'rust' have been raised (Bookworm has ver. 1.63, and a minimum of 1.66 is required). There is a way to do this: https://wildfiregames.com/forum/topic/127464-debian-bookworm-129-rustup-successful-compilation-of-0270-rc2/#comment-592272 If you are afraid that the compilation will clutter your system with various unnecessary packages, you can always compile on Debian Live https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/ You have to remember that directories on Live are created in RAM, and compiling 0ad requires a lot of space, so you have to attach external memory and create a compilation directory on it. But be careful - this memory must have a Linux file system (e.g. ext4), because fat32, exfat do not support symlinks and compilation will fail. After compilation is complete, we move the 'binaries' directory with the 'data' and 'system' subdirectories to the target location. The remaining compilation directories are unnecessary. Best regards

Today's build (2025-03-23) – 28, nightly build, ver. 186, f3948fb9db. Map: Elephantine, 1 + 3. The files 'interestinglog.html' and 'mainlog.html' reached a size of 6.0 GiB (each 6!). I have never had such large files (so many errors). Since the error (Petra) occurred, the game slowed down significantly (to about 3 fps) and it stayed that way until the very end. Best regards. logs_0ad_28_f3948fb9db_6GB.7z

It is already in Debian Sid: https://tracker.debian.org/pkg/0ad https://incoming.debian.org/debian-buildd/pool/main/0/0ad/ https://incoming.debian.org/debian-buildd/pool/main/0/0ad-data/ In Debian Bokworm will not be available: If you want to have 0ad 0.27.0 in Debian Bookworm, you have to compile it yourself using 'rustup' - tested - it works: https://wildfiregames.com/forum/topic/127464-debian-bookworm-129-rustup-successful-compilation-of-0270-rc2/ Regards

I understand that: 0ad-0.27.0-rc3 = L"release-a27, 8c69bb026d" Because in the archive '0ad-0.27.0-rc3-unix-build.tar.xz' I found the above number in the file: '/0ad-0.27.0/build/build_version/build_version.txt' And also the latest file: '/0ad-0.27.0/source/renderer/backend/gl/Device.cpp'

Debian Trixie + Nvidia + proprietary drivers nightly-build - Revision 143 U source/renderer/backend/gl/Device.cpp grep build_version ~/.config/0ad/logs/userreport_hwdetect.txt "build_version": "release-a27, 8c69bb026d", "build_version": "2.30.11", "build_version": 20100, I see that OpenGL ARB has been fixed. It works fine for me. Regards. PS. Debian Trixie Live + 'nouveau' driver Also works correctly, i.e.: OpenGl ARB and Open GL +GPU Skinning

After compiling on Debian Trixie + proprietary NVidia driver in case of 'OpenGL ARB' it is the same. There is probably no need to run Trixie Live with 'nouveau'? grep build_version ~/.config/0ad/logs/userreport_hwdetect.txt "build_version": "release-a27, 8f8d08b9f3", "build_version": "2.30.11", "build_version": 20100, logs.zip

Debian Trixie Live + driver 'nouveau' + 0.27.0-RC2 + OpenGL ARB PS. After pressing the 'Suppress' key twice, the game starts in a window. 'Alt+ Enter' switches to full screen. After selecting the game - 'Start game' - the game loads and suddenly - 0ad disappears. logs.zip

After unchecking (disabling) 'GPU skinning' the strange shadows disappeared.