Update blue-build from 1.6 to 1.8.
Hi there. Sorry for such a "lazy" question, but I'm a bit overwhelmed with my Phd courses right now and I can't find the time to troubleshoot my issue.
Can anyone take a look at the following PR and give me a brief explanation why it doesn't work? I thought I had completed the migration steps about a month ago.
https://github.com/ptinopedila/ptinopedila/pull/37
...
Solution:
i'll elaborate on that; dependabot is technically an outside contributor to your project, so it does not have access to the signing secrets needed for a successful build
default-flatpaks subsets
Is there any way to set a subset, like
verified, for a flatpak remote (called repo in bluebuild) in the default-flatpaks module?Fonts module no longer working
I recently updated the BlueBuild action version in my repository and fonts are no longer being installed by the fonts module.
Module config:
```yaml
- type: fonts # install JetBrainsMono NF...
error: Could not depsolve transaction; 1 problem detected
Hello, I've been getting this message after trying to make a custom image: https://github.com/MrQvest/my-atomic/
Example of a bad Github Action: https://github.com/MrQvest/my-atomic/actions/runs/12144458198
It says there is a problem, but it doesn't specify where or what is wrong:
[17:02:33 g.i/m/my-kinoite-nvidia:latest] => 13.88 error: Could not depsolve transaction; 1 problem detected:...
how to integrate ublue-update?
I am in the process of trying to figure out how to have automatic updates along with myOS
I'd like to have the notification enabled as well, just can't figure it out. Any help is appreciated...
Solution:
should be in bling iirc
Ollama tips?
There are several ways to install ollama for local LLM use. Here is my experience so far:
1) Using brew
Pros: Brew module keeps packages up to date, and since ollama gets updated quite frequently it makes using it a breeze
Cons: ...
Gnome extensions module stopped working
Hi everyone, I'm using the gnome extensions module but for some reason it stopped working yesterday. This was the first broken build: https://github.com/jonerrr/os-image/actions/runs/12035664576/job/33555161752. I tried building it locally with the blue-build cli and it worked, but then I upgraded the CLI and it broke (sorry i'm not sure what version i was on before). I can't seem to find any messages on why it failed. Any help debugging is appreciated.
Build fails on extensions module, but works if re-run
Weird issue, my automatic builds are consistently failing on the gnome extensions module. However, if i run the build manually right after, it builds. So what’s the issue?
Solution:
Nothing, except trying to install extension manually from github/gitlab with a script if you're really impatient.
Weirdly enough, I didn't have any build failure related to
gnome-extensions recently...Failed to parse version from metadata for ghcr.io/ublue-os/aurora-dx:41
For whatever reason, it is failing to pull any aurora images. I have tried with aurora:41, aurora:latest, and its dx counterparts. It hangs on this step for a while, tripling the total build time. It had not done this before. The build that fails is recipe-plasma.yml. Repo: https://github.com/arcbarkzap/supernova/
Solution:
This is a problem with Ublue changing the
org.opencontainers.image.version label on the image from the upstream version that Fedora sets
Has anyone made a custom image based on Bazzite for their gaming handheld (like the SteamDeck)?
The title pretty much says it all. It's mostly installing flatpaks and other software that I'd like to have, just by making another variant of my image using the same flatpak module file and whatnot. I would just like to know if someone has done this before hand and if they have hit any roadblocks
Solution:
Well, after testing my steamdeck with my image I can say:
- system-flatpaks does install my flatpaks, on top of the iso ones. I perused the logs and it just recognizes that the fedora repos have already been removed and installs everything.
- My own rpm packages being there work like normal...
Build failing after upgrade to f41?
Hi all,
Since upgrading to f41 I get a failure to build at the rpm module. Error logs are usually really informative but infortunately not in this case..
Full log attached, full recipe here: https://github.com/mecattaf/zen/blob/main/recipes/recipe.yml
I know for a fact that it's the
rpm-ostree module that's not working but no idea why.....Setting priority of COPR repos
Is it possible to set the priority of COPR repos installed with the
rpm-ostree moduleSolution:
so a script needs to be used for this
Help with Chezmoi module
Hello all, I'm so grateful for all the work that has been done on this project and my experience so far has been fantastic.
I'm trying to set up the chezmoi module and for the life of me can't seem to get it to play ball. This is in my recipe.yml:
- type: chezmoi
repository: "https://github.com/sgbonney/dotfiles"...
Can we `brew install` after using the brew module?
To install brew packages into the image?
Solution:
it's a runtime module, like
default-flatpaks is, so it's not possible to directly integrate brew packages into the imagePin current version then pull latest
After running
sudo ostree admin pin 2, if I run ujust update will my pin still be respected or will a reboot send me back to the latest update?Solution:
So doing pin just makes it so that particular image stays on your machine so you can roll back to it.
I keep getting an ISO based on Fedora 39 and not 41 when building an ISO on silverblue image.
The Repo : https://github.com/ZoeTheTransHoe/zoeys-first-image
Im trying to make my own silverblue spin. I want to base it off of Fedora 41, but despite adding
, going to then build an ISO from that repo makes it use Fedora SB 39 as the base, and not 41 as specified. Using latest instead of 41 doesnt fix my issue either.
Im using podman but I can replicate the same issue with docker. The command Im using to build the ISO is:...
base-image: ghcr.io/ublue-os/silverblue-main
image-version: 41
base-image: ghcr.io/ublue-os/silverblue-main
image-version: 41
Is there a way to run Pull Request builds?
Sort of like how bluefin does it, where uploads and signing are disabled, but everything else runs
How is the best way to design and test my system?
In NixOs i saw that is possible to rebuild and use the changes in realtime, is or is planned something simalr? When i am configuring my system is a bit annoying waiting for the whole gh action to succeed and then reboot the system
Solution:
If the GitHub Action is too slow for you, though, you could try building locally with the bluebuild cli
Cannot Rebase to Local Image
Running
sudo bluebuild rebase ./recipes/recipe.yml results in the following error.
Rebasing onto images built via the github workflow work just fine.
```...How to rebase back to normal fedora atomic?
Is this just a matter of rpm-ostree reset and then rebase to vanilla fedora?
Solution:
Pretty much. I'm unsure of where fedora keeps there public keys so if you can't find that, you might have to rebase to an unsigned image