My attempt is here: Comparing ublue-os:main...karypid:addnix · ublue-os/bluefin · GitHub
I added a script to create the mount point, made it executable and finally then edited the build-dx.sh script to make it get called.
Building the “addnix” branch in my repo does not seem to pick up the change though:
Step 11 invokes the build-dx.sh script but it runs as if it does not have my edit to invoke the new 08-nix.sh script…
Stupid question: Will the ARM64 image run on a Raspberry Pi CM4 (8GB/32GB EMMC)?
You would probably get better response if you start a new thread.
Not particularly sure about this, we dont include any special hardware support at all, so maybe? Maybe not? No one tested it.
The team has decided to not pursue a Bluefin LTS. I’ve closed all the other LTS threads but will leave this one open for discussion so it’s not spread out over multiple threads.
It won’t be going out of beta. The repository is up for adoption if you want to adopt it. We will continue to publish builds for a while (since it’s basically automated it doesn’t cost us anything), but I recommend moving off of it over the course of the summer.
Thanks to all of you who helped participate in testing!
That’s a shame. It was working well for me on a small work-related VM use case, and at lunchtime today I spun up a new VM to try out GNOME 48.
Is there a technical reason behind the decision, or was it due to lack of interest or maintainer time?
Not a technical decision.
Just not tenable at this time.
Aurora LTS will be doing the same. The repo is here if you would like to fork or adopt.
Your contributions and interest are well appreciated.
I was wondering about that …
I am willing to bet that the knowledge gained from the experiment was well worth it though.
Good call - to pursue, and fail fast.
Way to go @j0rge !
Ok new thread, thanks everyone!
