Brody Posts - Answer Overflow

Brody

Explore posts from servers

•Created by Brody on 12/11/2024 in #questions

Recipes failing to validate

Hey! I'm trying to adapt my custom image recipes to pass BlueBuild CLI's validation based on the latest blog post and looking at some of the maintainers' own recipes. I'm not sure what I'm doing wrong.

  × Recipe recipes/recipe-toybox.yml failed to validate
  ╰─▶ 
        × 11 errors encountered
          ╭─[./recipes/recipe-common.yml:79:9]
       78 │       # Add these Gnome extentions
       79 │ ╭─▶   - type: gnome-extensions
          · │             ────────┬───────
          · │                     ╰─┤ - "default-flatpaks" was expected
          · │                       │ - "gschema-overrides" was expected
          · │                       │ - "copy" was expected
          · │                       │ - "containerfile" was expected
          · │                       │ - "rpm-ostree" was expected
          · │                       │ - "yafti" was expected
          · │                       │ - "akmods" was expected
          · │                       │ - "script" was expected
          · │                       │ - "brew" was expected
       80 │ │       install:
       82 │ │         - Dash to Dock
          · │           ──────┬─────
          · │                 ╰─┤ - "negativo17" was expected
          · │                   │ - "ublue-update" was expected
          · │                   │ - "gnome-vrr" was expected
          · │                   │ - "1password" was expected
          · │                   │ - "dconf-update-service" was expected
          · │                   │ - "rpmfusion" was expected

  × Recipe recipes/recipe-toybox.yml failed to validate
  ╰─▶ 
        × 11 errors encountered
          ╭─[./recipes/recipe-common.yml:79:9]
       78 │       # Add these Gnome extentions
       79 │ ╭─▶   - type: gnome-extensions
          · │             ────────┬───────
          · │                     ╰─┤ - "default-flatpaks" was expected
          · │                       │ - "gschema-overrides" was expected
          · │                       │ - "copy" was expected
          · │                       │ - "containerfile" was expected
          · │                       │ - "rpm-ostree" was expected
          · │                       │ - "yafti" was expected
          · │                       │ - "akmods" was expected
          · │                       │ - "script" was expected
          · │                       │ - "brew" was expected
       80 │ │       install:
       82 │ │         - Dash to Dock
          · │           ──────┬─────
          · │                 ╰─┤ - "negativo17" was expected
          · │                   │ - "ublue-update" was expected
          · │                   │ - "gnome-vrr" was expected
          · │                   │ - "1password" was expected
          · │                   │ - "dconf-update-service" was expected
          · │                   │ - "rpmfusion" was expected

https://github.com/BrodyB/ublue-brody/tree/main/recipes

8 replies

UBUniversal Blue

•Created by Brody on 12/11/2024 in #🛟bazzite-help

All Extensions Disabled after Update

7 replies

UBUniversal Blue

•Created by Brody on 11/2/2024 in #🛟bazzite-help

Bazzite-Gnome shows unnecessary NVIDIA update prompt

10 replies

UBUniversal Blue

•Created by Brody on 10/2/2024 in #🛟bazzite-help

Ryujinx - Not detecting any controllers

13 replies

BBlueBuild

•Created by Brody on 9/12/2024 in #questions

Gschema overrides not reliably sticking?

Something I've noticed (particularly with making images off of Bazzite) is that only about half of the gschemas I define (using BlueBuild's gschema module) seem to actually stick. My assumption here is that there's a race condition happening and I need to somehow push my settings lower down the chain of events. What's the best way to do that? Should I just rename my gschema files like zz50-whatever or something as opposed to zz1-?

9 replies

BBlueBuild

•Created by Brody on 8/15/2024 in #questions

BlueBuild failing to run scripts on local rebase

Just started to encounter an issue when trying to build an image locally using bluebuild CLI. Whenever I run the scripts module, the build fails when it tries to run a specified script. I have two scripts, and they both suddenly have this issue. I haven't changed these scripts in a while, but perhaps I missed a note that they need to be relocated? The error I'm getting:

oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => ================================================ Start 'script' Module ================================================
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => Running script removeBluefinWallpapers.sh
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => /usr/bin/env: 'bash\r': No such file or directory
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => /usr/bin/env: use -[v]S to pass options in shebang lines
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => Error: building at STEP "RUN --mount=type=bind,from=stage-files,src=/files,dst=/tmp/files,rw --mount=type=bind,from=stage-modules,src=/modules,dst=/tmp/modules,rw --mount=type=bind,from=ghcr.io/blue-build/cli:3ecb0d3d939b127fa47460ea07008bc6621e4fa5-build-scripts,src=/scripts/,dst=/tmp/scripts/ --mount=type=cache,dst=/var/cache/rpm-ostree,id=rpm-ostree-cache-ublue-brody-apollo-latest,sharing=locked /tmp/scripts/run_module.sh 'script' '{"type":"script","scripts":["removeBluefinWallpapers.sh"]}'   && ostree container commit": while running runtime: exit status 127

oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => ================================================ Start 'script' Module ================================================
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => Running script removeBluefinWallpapers.sh
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => /usr/bin/env: 'bash\r': No such file or directory
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => /usr/bin/env: use -[v]S to pass options in shebang lines
oci-archive:/etc/bluebuild/ublue-brody-apollo.tar.gz => Error: building at STEP "RUN --mount=type=bind,from=stage-files,src=/files,dst=/tmp/files,rw --mount=type=bind,from=stage-modules,src=/modules,dst=/tmp/modules,rw --mount=type=bind,from=ghcr.io/blue-build/cli:3ecb0d3d939b127fa47460ea07008bc6621e4fa5-build-scripts,src=/scripts/,dst=/tmp/scripts/ --mount=type=cache,dst=/var/cache/rpm-ostree,id=rpm-ostree-cache-ublue-brody-apollo-latest,sharing=locked /tmp/scripts/run_module.sh 'script' '{"type":"script","scripts":["removeBluefinWallpapers.sh"]}'   && ostree container commit": while running runtime: exit status 127

And one of the scripts it's happening with: https://github.com/BrodyB/ublue-brody/blob/main/files/scripts/removeBluefinWallpapers.sh

10 replies

BBlueBuild

•Created by Brody on 7/26/2024 in #questions

Failed to open ./config/recipe.yml

I've been refactoring my repo based on the recent change to files/. When I try testing my new setup in Bluebuild CLI, I get hit with the error message:

WARN => Use of ./config for recipes is deprecated, please move your recipe files to ./recipes
ERROR => Failed to open ./config/recipe-common.yml

WARN => Use of ./config for recipes is deprecated, please move your recipe files to ./recipes
ERROR => Failed to open ./config/recipe-common.yml

This is obviously coming from my main recipe's use of the - from-file: recipe-common.yml but I never changed this syntax. Is this something I missed from the migration? https://github.com/BrodyB/ublue-brody/blob/refactor/recipes/recipe-framework.yml

4 replies

Gaming

Programming