https://blue-build.org/ logo
using dnf bundles? (@cosmic-desktop-environment)
# questions
w
https://copr.fedorainfracloud.org/coprs/ryanabx/cosmic-epoch/ the "correct" way to use a tagged release of installing the cosmic desktop environment right now is something I'd never heard of before, in a non-ostree environment it'd be
dnf install @cosmic-desktop-environment
a "bundle" of packages I guess? On my first attempt to do this as a plain ol' rpm-ostree package I got
Copy code
× Recipe ./recipes/DX-GTS.yml failed to validate
  ╰─▶ 
        × Failed to deserialize recipe ./recipes/DX-GTS.yml
        ╰─▶ found character that cannot start any token at line 27 column 9,
      while
            scanning for the next token
      
  help: Use `bluebuild validate --all-errors ./recipes/DX-GTS.yml` to view
        more information.
        If you're using a local module, be sure to add `source: local` to the
        module entry
Is this an unsupported feature at the moment? Is it a thing introduced in 41 that isn't quite trickled down to ostree? Sorry if this has been covered, sadly bluebuild has "just worked" for about a year now on my own local gitea instance, and therefore I kinda stepped away from the community. It broke (my local setup, not bluebuild's fault) so I figured moving back to github would be preferrable, and figured I'd update a lot of things too.
a
message has been deleted
g
I don't think rpm-ostree can do bundles, but the error you're seeing might require you to put that string in quotes.
I think the @ symbol is a special character in YAML.
w
Gotcha, running into some other fun build issues right now, for now I pivoted back to the "old way" on the cosmic nightly that doesn't do the bundle. Once I figure out the other stuff I'll loop back and see if it works as a string.
g
The DNF module should be able to handle that. I don't know if this module can. You would need to have a base image that doesn't do a CLI wrap of DNF.
w
Gotcha. My main reason for going bluebuild over just using out of the box bluefin/bazzite is injecting cosmic desktop, and it miggghhhtt be broken right now?
g
Yeah, I just run whatever's in the COPR repo
w
So far I haven't gotten a successful build with adding it as the really only thing other than changing the base image to bluefin-dx gts and attempting to add cosmic
g
I just use this
Copy code
yaml
modules:
  - type: rpm-ostree
    repos:
      - https://copr.fedorainfracloud.org/coprs/ryanabx/cosmic-epoch/repo/fedora-%OS_VERSION%/ryanabx-cosmic-epoch-fedora-%OS_VERSION%.repo
    install:
      - cosmic-desktop
But I use bazzite as a base
I can't use the locked alpha version cause of my KVM. It crashes the compositor whenever I switch
w
That's what I had, more or less, it blew up.
g
That sucks
w
FWIW, it hasn't worked since I made any meaningful change to the base recipe
so I'm unsure if its cosmic or something else
g
What's the error you get?
Copy code
[17:18:52 g.i/w/wafflosagus:latest] => ERROR: failed to solve: process "/bin/sh -c /tmp/scripts/run_module.sh 'rpm-ostree' '{\"type\":\"rpm-ostree\",\"repos\":[\"https://copr.fedorainfracloud.org/coprs/atim/starship/repo/fedora-%OS_VERSION%/atim-starship-fedora-%OS_VERSION%.repo\",\"https://copr.fedorainfracloud.org/coprs/ryanabx/cosmic-epoch/repo/fedora-%OS_VERSION%/ryanabx-cosmic-epoch-fedora-%OS_VERSION%.repo\"],\"install\":[\"micro\",\"starship\",\"tldr\",\"cosmic-desktop\"]}'   && ostree container commit" did not complete successfully: exit code: 1
[17:18:52 ERROR] => Failed:
g
You'll have to show more than that line. That's just docker saying that command failed
w
Cause I'm a dummy and didn't realize till you said that if I scrolled up I'd get way more information 😅
Copy code
[17:18:52 g.i/w/wafflosagus:latest] => 16.52 rpm-md repo 'updates'; generated: 2024-12-20T12:33:13Z solvables: 32099
[17:18:52 g.i/w/wafflosagus:latest] => 16.52 rpm-md repo 'fedora'; generated: 2024-04-14T18:51:11Z solvables: 74881
[17:18:52 g.i/w/wafflosagus:latest] => 16.52 rpm-md repo 'updates-archive'; generated: 2024-12-20T13:18:41Z solvables: 62859
[17:18:52 g.i/w/wafflosagus:latest] => 16.69 Resolving dependencies...done
[17:18:52 g.i/w/wafflosagus:latest] => 16.72 error: Could not depsolve transaction; 1 problem detected:
[17:18:52 g.i/w/wafflosagus:latest] => 16.72  Problem: package cosmic-desktop-1.0.0~alpha.3^20241205-1.fc40.noarch from copr:copr.fedorainfracloud.org:ryanabx:cosmic-epoch requires cosmic-session, but none of the providers can be installed
[17:18:52 g.i/w/wafflosagus:latest] => 16.72   - conflicting requests
[17:18:52 g.i/w/wafflosagus:latest] => 16.72   - nothing provides cosmic-idle >= 1.0.0~alpha.4 needed by cosmic-session-1.0.0~alpha.4^git20241206.78316ba-1.fc40.x86_64 from copr:copr.fedorainfracloud.org:ryanabx:cosmic-epoch
[17:18:52 g.i/w/wafflosagus:latest] => 16.72   - nothing provides cosmic-idle >= 1.0.0~alpha.4 needed by cosmic-session-1.0.0~alpha.4^git20241217.0a3b9f5-1.fc40.x86_64 from copr:copr.fedorainfracloud.org:ryanabx:cosmic-epoch
Interesting
w
oh interesting, you stood it all up on gitlab?
makes notes to ask about later
g
Yup that was the first CI I supported when I started writing the CLI
w
gotta get it working in the first place before trying to in-house it
g
The CLI README has a basic
.gitlab-ci.yml
that should work for you
w
Oh gitlab is too heavy for what I wanna do, I was doing it in gitea for a good while
all my "in house" issues were I think with the runners themselves
and like, docker socket permissions
g
Gotcha
w
problems for future Waffle
ok, yea, removing cosmic it worked
ugh
Copy code
- type: rpm-ostree
    repos:
      - https://copr.fedorainfracloud.org/coprs/atim/starship/repo/fedora-%OS_VERSION%/atim-starship-fedora-%OS_VERSION%.repo

    install:
      - micro
      - starship
      - "@cosmic-desktop-environment"
      - tldr
So the above should, hypothetically, work assuming ostree handles bundles?
(with the assumption that it doesn't handle bundles)
g
Yeah
w
since the tip of the git spear is busted for me
I'd honestly like to just use the tagged ones at this point anyway.
g
I'm running my build locally to see if it's busted for me too
w
damn your repo is fancy
with all these common build branches and the like
g
Lol yeah I like to chunk things out as much as I can
w
I may wanna do some amount of that since I'm building a GTS and a stable build of the same packages on dx
gotta get a working one first though >.>
[17:45:54 g.i/w/wafflosagus:latest] => 16.45 error: Packages not found: @cosmic-desktop-environment
ugh
Cosmic is like half the reason I am in the bluebuild rabbit hole.
g
The COPR repo seemed to work for me
w
weird
g
Maybe it's something with bluefin
w
are you on a different base?
g
ghcr.io/ublue-os/bazzite-nvidia
w
hm, bazzite never did a dx did they?
otherwise I'd just be on that full time
I swap between dx and bazzite normally.
g
I setup my own dev tools
I don't like other dictating the tools I use
I'm fine with them setting up all the game stuff though
w
I'm a simple man, realistically the main reason I went dx is the side projects use containers that worked out of the box with docker but not with podman
I went with "well this seemed to work quickly" and didn't dig further
g
If you want docker, you can crib my docker recipe module file I have in my repo
w
yea, I could probably just add docker to bazzite and be done with it.
Although I may end up adding vscode proper too
but that's simple enough
g
Copy code
yaml
modules:
- type: rpm-ostree
  repos:
    - https://download.docker.com/linux/fedora/docker-ce.repo
  install:
    - docker-ce
    - docker-ce-cli
    - containerd.io
    - docker-buildx-plugin 
    - docker-compose-plugin
- type: systemd
  system:
    enabled:
    - docker.service
w
mostly I live in jetbrains things, and that's outside of bluebuild
the little toolbox things lives in /home
erm, /var/home/ you get my point
g
Yeah you don't even have to put that in your image
I'm a terminal developer so I don't really use IDEs anymore
Alacritty, tmux, and helix
w
I've been training vim motions in jetbrains to build up the muscle memory
g
Plus Cosmic makes it so that I rarely have to use the mouse
w
ok, going to bazzite, added docker in one go. I should poke around and see if anything else I need out of dx right now...
I don't know of any?
g
¯\_(ツ)_/¯
w
yea, that's a waffle question for sure.
g
Looks like I was able to install cosmic with bluefin-dx-nvidia as my base
w
weeeeiiirrrdddd...
g
No idea what's up with yours
Oh well I did use
stable
Not `gts
w
ah, if gts is the problem imma be salty
I wanted gts for stability, and if its more unstable...
g
Hmmm looks like they also don't use the correct version label on the bluefin image...
g
Seemed fine on the nvidia image
w
building bazzite + docker as well as a stable dx image.
yea, I'm 100% AMD in this household
well, actually, wife's laptop, my old work laptop, has nvidia, but she's on windows...
g
My card is leftover from when I was running Windows
Steam Deck came out and I JUMPED at the opportunity to switch to Linux
w
ironically I bought my main GPU, a 6900xt, before my recent linux jump, it was just the most powerful card for the money when I bought it, then about a month later went all in on linux. I am quite happy in hindsight cause linux compatibility wasn't even on my radar
"recent" being... like, june of last year?
longer?
g
I will say though, Nvidia support has gotten WAY better recently for wayland
w
I don't remember
for sure!
Then when the framework 16 was announced as an all AMD machine I signed up pretty much instantly
g
Ok yeah running your recipes, it seems GTS is the one that fails with installing cosmic
w
I think it worked with bluefin-dx-stable... and I'm a bit pissy now (well, ok, I'm really happy its working, but also salty)
yea
g
The FW16 is so gooood
w
Mine has some issues with the macropad that I need to update the firmware on my machine, and had a support ticket open but I'm real bad about following through on report tickets... I should do that today!
g

https://tenor.com/vXTveNpNRO4.gif▾

w
Man, life is busy these days. The fact that I can just remove the macropad and have a working machine took precedence
g
Lol I totally get you
w
My selfhosted build broke a while ago, like I think I'm on an image from the 1st of this month
my selfhosted, when it worked, was on like version 1.1 of your action cause it was the only one I could get working
g
😬
w
yesterday and today were the "Well instead of getting it working on my local gitea, Imma just go back to github to make it work"
you're on... 1.8?
g
Uhhh
Maybe?
I'm on Gitlab so there is no action lol
w
(You are, I have the build open now)
The 1.1 was working because I think you moved from running podman in the runner image to just running on the host
and that didn't jive well with my permissions on my unraid NAS
g
Ah ok
w
It was way faster, but in general, once I got a stable image, I don't care if it takes 2 hours to build
(it didn't)
I'll return to that one day... maybe
for now having my configuration avaliable on github ain't a big deal
I was being super private, but have since been shown that there is some value in having stuff be public
g
Yeah just don't put secrets in there
w
I don't think I did even in my private repo
that said, I do put secrets in the private repo for other things 😛
g
There is an issue open to allow setting docker/podman secrets if needed, but ideally you would put those in the settings for you repo like the signing key
And I would make extra sure that they wouldn't get printed out anywhere
w
its really nice to be kinda sloppy, my gitea instance has some things just in the repo that are secrets, but since its on a very private network, I just don't care. And then I build images to private projects as public repos in that so when I deploy them, as long as the VPS is on my tailnet (tailscale is rad) it can pull the images without having git keys
g
Tailscale is so awesome
w
Eh, its a gitea instance that doesn't exist on the public internet. It exists only behind my tailnet, so I admit I'm kinda sloppy with it
Thanks for your help @gmpinder, even if it was just "Bluefin GTS broked" I'll make a new thread if I run into any other issues, but I think we solved this one (and I have a build that works on github)
well, I'm rebasing now, I guess we'll see if it works proper
And I am definitely taking your idea of slowly just "DIY-ing" my own bazzite-dx
g
Glad I could help!