Oolite Bulletins

...So do not hope the linter will change anytime soon. New release here: https://github.com/mcarans/oolite/releases I use the appdata.xml name for appimage. Appimage lint is included in the build and all lint errors are now fixed. Let me know if that fixes things in AppImageHub or if there is anyth...

Yes, archlinux switched to llvm 22.1.x on march 14 . I may have time to prepare local packages compiled with clang for gnustep-base & gnustep-make later this week, but until those are ready I can only build oolite with gcc. What version/commit of gnustep code are you using ? Latest master - the...

Actually we could add this linter to our build process - just before the AppImage is getting created. Then we'd have first hand feedback. Good idea. This would mirror the flatpak build which calls flatpak-builder-lint manifest "$MANIFEST" Marvellous! :-) If you are busy with your lot of c...

hiran wrote: ↑Mon Mar 16, 2026 7:52 pm

Actually we could add this linter to our build process - just before the AppImage is getting created. Then we'd have first hand feedback.

Good idea. This would mirror the flatpak build which calls flatpak-builder-lint manifest "$MANIFEST"

Working in a bug fix branch for point updates is normal development practice. If I developed this in the master branch, it will be released in 1.93 at some much later date. By treating it as as a bug fix, it can be worked on in the 1.92-maintenance branch. Usually that method is only used for bugs ...

Working in a bug fix branch for point updates is normal development practice. If I developed this in the master branch, it will be released in 1.93 at some much later date. By treating it as as a bug fix, it can be worked on in the 1.92-maintenance branch. What I think we need to do is make the bui...

Are you able to switch the appimagehub to use the 1.92-maintenance branch instead of master? 1.92.1 will be released from that branch not master (which is for 1.93). Sounds odd to me. We are trying to fix the release before development? But let's see. [...] How to submit AppImages to the catalog Cr...

Github does support self-hosted runners, mcarans has setup atleast 2 : fedora & archlinux . adding debian stable should not be hard. Great mcarans achieved this. I do not question that self-hosted runners can be created. But someone needs to host them. Otherwise the support will have to be drop...

Have a look at the appimages here: https://github.com/mcarans/oolite/actions/runs/23101780478. I have fixed the naming and added to them the required metadata. Are they ok? The flatpak and appimage share a build step and metadata. Sounds good. Yet to test them I'd have not only to download them but...

Note : continuation of https://bb.oolite.space/viewtopic.php?p=304418#p304418 in new thread Speaking of compilers being trickier, the arch source build just started failing with an error building gnustep-base that I've not seen before: https://github.com/mcarans/oolite/actions/runs/23101631215/job/...

I'll try to contact someone on their side. Not yet real contact, but additional investigation showed the successful build was due to some changes on a specific branch in their repo. Two commits seem to relax their linter: - Allow empty DESKTOP_COMMENT - Do not error when no license is found Somehow...

We choose a point in time, focus on known good installations and use those to establish the baseline. as starting point I suggest oolite 1.92 as that was released 5 weeks ago. As far as I know no critical bugs have been reported since then. The downloads page shows 1 windows download, a linux flatp...

I expect I could design/compose a few specific usecases to clarify the lddtree + LD_PRELOAD approach using manual commands/actions . Will that do ? Note : I'd like this thread to focus on the concept so would post that in another thread in the linux forum area. ...Then I'd like to move towards sugg...

I have not yet read/verified the full xml you presented. Appimagehub has some linter that goes through that all. IIRC it checked the prerelease, so changing the master branch is sufficient for me to test again. Once that passes we can think of backporting to the release. I think that like FlatHub o...

<release version="1.92" date="2026-02-03"> <description> <p>First Flatpak release of Oolite.</p> </description> </release> Is this description OK for upload to the AppImage repo? Maybe not mentioning Flatpak would be better but up to you. I'm refactoring to make a shared metadat...