Universal Blue•8mo ago

Bazzite Build failed

FYI, most recent build of Bazzite failed. Same error I'm getting on my most recent build. Gonna try and troubleshoot for a bit this morning.

49 Replies

Noel•8mo ago

@Bazzite Maintainer Here is what I've gathered so far: 1. bmi323 isn't showing up in the list of RPMs from akmods. 2. Kernel differences when trying to install any of the kmod RPMs

error: Could not depsolve transaction; 1 problem detected:
 Problem: package kmod-openrazer-6.6.12-201.fsync.fc39.x86_64-100.0.0.git.530.886f986d-1.fc39.x86_64 from @commandline requires kernel-uname-r = 6.6.12-201.fsync.fc39.x86_64, but none of the providers can be installed
  - cannot install both kernel-uki-virt-6.6.12-201.fsync.fc39.x86_64 from copr:copr.fedorainfracloud.org:sentry:kernel-fsync and kernel-uki-virt-6.6.14-201.fsync.fc39.x86_64 from @System
  - cannot install both kernel-core-6.6.12-201.fsync.fc39.x86_64 from copr:copr.fedorainfracloud.org:sentry:kernel-fsync and kernel-core-6.6.14-201.fsync.fc39.x86_64 from @System
  - conflicting requests
Error: building at STEP "RUN sed -i 's@enabled=0@enabled=1@g' /etc/yum.repos.d/_copr_ublue-os-akmods.repo &&     wget https://negativo17.org/repos/fedora-multimedia.repo -O /etc/yum.repos.d/negativo17-fedora-multimedia.repo &&     rpm-ostree install         /tmp/akmods-rpms/kmods/*openrazer*.rpm &&     sed -i 's@enabled=1@enabled=0@g' /etc/yum.repos.d/negativo17-fedora-multimedia.repo": while running runtime: exit status 1

error: Could not depsolve transaction; 1 problem detected:
 Problem: package kmod-openrazer-6.6.12-201.fsync.fc39.x86_64-100.0.0.git.530.886f986d-1.fc39.x86_64 from @commandline requires kernel-uname-r = 6.6.12-201.fsync.fc39.x86_64, but none of the providers can be installed
  - cannot install both kernel-uki-virt-6.6.12-201.fsync.fc39.x86_64 from copr:copr.fedorainfracloud.org:sentry:kernel-fsync and kernel-uki-virt-6.6.14-201.fsync.fc39.x86_64 from @System
  - cannot install both kernel-core-6.6.12-201.fsync.fc39.x86_64 from copr:copr.fedorainfracloud.org:sentry:kernel-fsync and kernel-core-6.6.14-201.fsync.fc39.x86_64 from @System
  - conflicting requests
Error: building at STEP "RUN sed -i 's@enabled=0@enabled=1@g' /etc/yum.repos.d/_copr_ublue-os-akmods.repo &&     wget https://negativo17.org/repos/fedora-multimedia.repo -O /etc/yum.repos.d/negativo17-fedora-multimedia.repo &&     rpm-ostree install         /tmp/akmods-rpms/kmods/*openrazer*.rpm &&     sed -i 's@enabled=1@enabled=0@g' /etc/yum.repos.d/negativo17-fedora-multimedia.repo": while running runtime: exit status 1

Got the above error message when just trying to install just openrazer and nothing else. OK, so I tried building my container without kmods and we get the same error as the original build failure:

error: Could not depsolve transaction; 1 problem detected:
 Problem: package mesa-va-drivers-freeworld-23.3.3-1.fc39.x86_64 from @System requires mesa-filesystem(x86-64) = 23.3.3, but none of the providers can be installed
  - cannot install both mesa-filesystem-23.3.4-100.bazzite.0.0.git.2622.12136b49.x86_64 from copr:copr.fedorainfracloud.org:kylegospo:bazzite-multilib and mesa-filesystem-23.3.3-1.fc39.x86_64 from @System
  - cannot install both mesa-filesystem-23.3.3-1.fc39.x86_64 from updates-archive and mesa-filesystem-23.3.4-100.bazzite.0.0.git.2622.12136b49.x86_64 from copr:copr.fedorainfracloud.org:kylegospo:bazzite-multilib
  - conflicting requests
Error: building at STEP "RUN rpm-ostree override replace     --experimental     --from repo=copr:copr.fedorainfracloud.org:kylegospo:bazzite-multilib         mesa-filesystem         mesa-dri-drivers         mesa-libEGL         mesa-libgbm         mesa-libGL         mesa-libglapi         mesa-vulkan-drivers         mesa-libOSMesa         pipewire         pipewire-alsa         pipewire-gstreamer         pipewire-jack-audio-connection-kit         pipewire-jack-audio-connection-kit-libs         pipewire-libs         pipewire-pulseaudio         pipewire-utils": while running runtime: exit status 1

error: Could not depsolve transaction; 1 problem detected:
 Problem: package mesa-va-drivers-freeworld-23.3.3-1.fc39.x86_64 from @System requires mesa-filesystem(x86-64) = 23.3.3, but none of the providers can be installed
  - cannot install both mesa-filesystem-23.3.4-100.bazzite.0.0.git.2622.12136b49.x86_64 from copr:copr.fedorainfracloud.org:kylegospo:bazzite-multilib and mesa-filesystem-23.3.3-1.fc39.x86_64 from @System
  - cannot install both mesa-filesystem-23.3.3-1.fc39.x86_64 from updates-archive and mesa-filesystem-23.3.4-100.bazzite.0.0.git.2622.12136b49.x86_64 from copr:copr.fedorainfracloud.org:kylegospo:bazzite-multilib
  - conflicting requests
Error: building at STEP "RUN rpm-ostree override replace     --experimental     --from repo=copr:copr.fedorainfracloud.org:kylegospo:bazzite-multilib         mesa-filesystem         mesa-dri-drivers         mesa-libEGL         mesa-libgbm         mesa-libGL         mesa-libglapi         mesa-vulkan-drivers         mesa-libOSMesa         pipewire         pipewire-alsa         pipewire-gstreamer         pipewire-jack-audio-connection-kit         pipewire-jack-audio-connection-kit-libs         pipewire-libs         pipewire-pulseaudio         pipewire-utils": while running runtime: exit status 1

EyeCantCU•8mo ago

Is this from CI or a local image build?

Noel•8mo ago

local image build. been making sure to do --no-cache each time to do a brand new container build.

EyeCantCU•8mo ago

Usually this happens when the kmods built for fsync are misaligned with the latest kernel version in the copr. Akmods likely needs a rebuild As for missing bmi233, I will have to take a closer look here in a bit Mesa may need an update on our end

Noel•8mo ago

akmods was built about an hour ago: https://github.com/ublue-os/akmods/actions/runs/7727228072

HikariKnight•8mo ago

i havent done anything with the kmod and akmod stuff so i know literally nothing on that side, but willing to help with what i can while i still have power and/or internet (currently there is a hurricane here that is as strong as the strongest one recorded previously in norway so there is expected to be infrastructure issues, especially for me as im in the red zone)

Noel•8mo ago

for sure! I just wanted to get visibility on this. I feel bad for DMing Kyle so early in the morning 😛

HikariKnight•8mo ago

it happens and im sure he kinda expect it to happen once in a while. especially if youre a mod in a discord server

Kyle Gospo•8mo ago

Have to wait for rpmfusion to update Their mesa freeworld package is behind fedora again

Noel•8mo ago

sounds good. Any thoughts on the akmods failures?

Kyle Gospo•8mo ago

That one I'm not sure on, let me peek

Noel•8mo ago

just confirmed:

[nomiller@fedora][~/workspace]$ yum provides mesa-va-drivers-freeworld
Last metadata expiration check: 0:06:03 ago on Wed 31 Jan 2024 09:52:11 AM CST.
mesa-va-drivers-freeworld-23.2.1-2.fc39.i686 : Mesa-based VA-API drivers
Repo        : rpmfusion-free
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.2.1-2.fc39

mesa-va-drivers-freeworld-23.2.1-2.fc39.x86_64 : Mesa-based VA-API drivers
Repo        : rpmfusion-free
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.2.1-2.fc39

mesa-va-drivers-freeworld-23.3.3-1.fc39.i686 : Mesa-based VA-API drivers
Repo        : rpmfusion-free-updates
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.3.3-1.fc39

mesa-va-drivers-freeworld-23.3.3-1.fc39.x86_64 : Mesa-based VA-API drivers
Repo        : @System
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.3.3-1.fc39

mesa-va-drivers-freeworld-23.3.3-1.fc39.x86_64 : Mesa-based VA-API drivers
Repo        : rpmfusion-free-updates
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.3.3-1.fc39

[nomiller@fedora][~/workspace]$ yum provides mesa-va-drivers-freeworld
Last metadata expiration check: 0:06:03 ago on Wed 31 Jan 2024 09:52:11 AM CST.
mesa-va-drivers-freeworld-23.2.1-2.fc39.i686 : Mesa-based VA-API drivers
Repo        : rpmfusion-free
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.2.1-2.fc39

mesa-va-drivers-freeworld-23.2.1-2.fc39.x86_64 : Mesa-based VA-API drivers
Repo        : rpmfusion-free
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.2.1-2.fc39

mesa-va-drivers-freeworld-23.3.3-1.fc39.i686 : Mesa-based VA-API drivers
Repo        : rpmfusion-free-updates
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.3.3-1.fc39

mesa-va-drivers-freeworld-23.3.3-1.fc39.x86_64 : Mesa-based VA-API drivers
Repo        : @System
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.3.3-1.fc39

mesa-va-drivers-freeworld-23.3.3-1.fc39.x86_64 : Mesa-based VA-API drivers
Repo        : rpmfusion-free-updates
Matched from:
Provide    : mesa-va-drivers-freeworld = 23.3.3-1.fc39

Kyle Gospo•8mo ago

If you're installing bmi233 It's bmi323

Noel•8mo ago

sorry, I meant to say 323 when I checked this morning, 323 wasn't showing up in the list of RPMs confirmed using this container file:

ARG SOURCE_IMAGE="kinoite"
ARG SOURCE_SUFFIX="main"
ARG FEDORA_VERSION="39"

FROM ghcr.io/ublue-os/${SOURCE_IMAGE}-${SOURCE_SUFFIX}:${FEDORA_VERSION} AS isengard

ARG IMAGE_NAME="${IMAGE_NAME:-isengard}"
ARG IMAGE_VENDOR="${IMAGE_VENDOR:-noelmiller}"
ARG IMAGE_FLAVOR="${IMAGE_FLAVOR:-main}"
ARG AKMODS_FLAVOR="${AKMODS_FLAVOR:-fsync}"
ARG IMAGE_BRANCH="${IMAGE_BRANCH:-main}"
ARG BASE_IMAGE_NAME="${BASE_IMAGE_NAME:-kinoite}"
ARG FEDORA_MAJOR_VERSION="${FEDORA_MAJOR_VERSION:-39}"

COPY --from=ghcr.io/ublue-os/akmods:fsync-39 /rpms/ /tmp/rpms
RUN ls /tmp/rpms/kmods | grep bmi

ARG SOURCE_IMAGE="kinoite"
ARG SOURCE_SUFFIX="main"
ARG FEDORA_VERSION="39"

FROM ghcr.io/ublue-os/${SOURCE_IMAGE}-${SOURCE_SUFFIX}:${FEDORA_VERSION} AS isengard

ARG IMAGE_NAME="${IMAGE_NAME:-isengard}"
ARG IMAGE_VENDOR="${IMAGE_VENDOR:-noelmiller}"
ARG IMAGE_FLAVOR="${IMAGE_FLAVOR:-main}"
ARG AKMODS_FLAVOR="${AKMODS_FLAVOR:-fsync}"
ARG IMAGE_BRANCH="${IMAGE_BRANCH:-main}"
ARG BASE_IMAGE_NAME="${BASE_IMAGE_NAME:-kinoite}"
ARG FEDORA_MAJOR_VERSION="${FEDORA_MAJOR_VERSION:-39}"

COPY --from=ghcr.io/ublue-os/akmods:fsync-39 /rpms/ /tmp/rpms
RUN ls /tmp/rpms/kmods | grep bmi

STEP 10/10: RUN ls /tmp/rpms/kmods | grep bmi
kmod-bmi260-6.6.12-201.fsync.fc39.x86_64-0.0.git.13.4129c865-1.fc39.x86_64.rpm

STEP 10/10: RUN ls /tmp/rpms/kmods | grep bmi
kmod-bmi260-6.6.12-201.fsync.fc39.x86_64-0.0.git.13.4129c865-1.fc39.x86_64.rpm

Kyle Gospo•8mo ago

Odd, it's definitely in the last akmod build

Gaming

Programming

Bazzite Build failed