Meexin
BBlueBuild
•Created by Meexin on 2/5/2025 in #questions
Issue with default Universal Blue update service (ublue-update.service)
It seems it is failing if you are using non-native universal blue image (for example the one build from blue build template). It is failing with parse error in python.
I found a note here: https://github.com/ublue-os/ublue-update saying:
Note If you are on an image derived from uBlue main, you will need to remove or disable automatic updates with rpm-ostreed, to do this, you need to remove or change this line in the config file: AutomaticUpdatePolicy=stage (set to none if you don't want to remove the line). Anyway tried and no change.
That is only stuff that could be somewhat related, but otherwise found not info or issue related to that. Running manually the update file in bin folder works for user, but with sudo it is failing with the same error.
On the other hand it seems Unversal Blue will switch soon to uupd https://github.com/ublue-os/uupd , so maybe that one will work even with non standard ones?
Mainly wondering, how others solved this and if anybody else has issue with automatic updates?
Running
ujust update manually works and updates everything, just the systemd service is failing.
Thanks a lot for help.4 replies
BBlueBuild
•Created by Meexin on 2/5/2025 in #questions
Correct way to use custom image - rebase or install via ISO - UBlue "after boot" customizations?
Hi,
I built my customized image of Aurora-DX using blue build template. Now wondering, what is the correct / best approach to use this image and/or how to build it?
The point is, that I can install standard Aurora-DX, boot it and rebase to my image. This way I got all aurora flatpaks for example as well as my custom ones from my blue build (from my recipe).
But when I install and boot directly my image ISO, I am missing default Aurora-DX stuff (e.g. their default flatpaks for example) - only my custom ones are installed.
So the question again is, how should I proceed and does this affect only default Aurora flatpaks or I lose this way more standard Aurora-DX "after boot" customizations? (when I am using directly my image without rebase)?
Should I include default aurora flatpaks directly into my recipe as well? That would mitigate the flatpaks issue. But is there more customizations from default Aurora-DX/any Universal Blue image I may be losing? Or is "safer" approach to install default Aurora-DX and rebase to my image (so I get all "after boot" stuff from standard Aurora)?
Thanks a lot!
10 replies
BBlueBuild
•Created by Meexin on 2/5/2025 in #questions
Building ISO from custom Blue Build images based on Aurora - boots as Fedora Base 41
Hi,
I am using Blue Build template to create slightly customized Aurora-DX image (just adding couple of flatpaks, rpm packages and custom justfile). When I build image and rebase to it from standard Aurora-DX (installed via official ISO), it works as expected. I have it as my
ghcr.io/mygithubacc/myaurora package with all standard aurora stuff as well as my custom ones.
But when I build IOS from this as sudo bluebuild generate-iso --iso-name weird-os.iso recipe recipes/recipe.yml (version 0.9.6) , it works, but when I install it and boot this image, it shows as Fedora Base 41 and rpm-ostree status output is quay.io/fedora-desktops/base:41 instead of expected ghcr.io/mygithubacc/myaurora. So updates are not working etc. But on the other hand aurora customizations are in place, my custom packages from myaurora are also there. Just the "source" address is pointing to wrong image. What I am doing wrong with the build?
Thanks a lot!12 replies