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
Noel5mo 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
EyeCantCU5mo ago
Is this from CI or a local image build?
Noel
Noel5mo ago
local image build. been making sure to do --no-cache each time to do a brand new container build.
EyeCantCU
EyeCantCU5mo 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
Noel5mo ago
HikariKnight
HikariKnight5mo 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
Noel5mo ago
for sure! I just wanted to get visibility on this. I feel bad for DMing Kyle so early in the morning 😛
HikariKnight
HikariKnight5mo 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
1/4 Life
1/4 Life5mo ago
Have to wait for rpmfusion to update Their mesa freeworld package is behind fedora again
Noel
Noel5mo ago
sounds good. Any thoughts on the akmods failures?
1/4 Life
1/4 Life5mo ago
That one I'm not sure on, let me peek
Noel
Noel5mo 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
1/4 Life
1/4 Life5mo ago
If you're installing bmi233 It's bmi323
Noel
Noel5mo 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
1/4 Life
1/4 Life5mo ago
Odd, it's definitely in the last akmod build
Noel
Noel5mo ago
just for posterity, I built the container with --no-cache 2 seconds ago. unless my grep command is wrong, but I'm pretty sure it's not? 😛 at any rate, I love that we are catching these issues in CI and not on my machine I depend on! 😄 OK, akmods is a non issue. my most recent build just failed because of mesa. this is me lacking in knowledge on how to use podman. For my local container I didn't use --pull
1/4 Life
1/4 Life5mo ago
Dope
Noel
Noel5mo ago
Shows up now!
STEP 10/10: RUN ls /tmp/rpms/kmods | grep bmi
kmod-bmi260-6.6.14-201.fsync.fc39.x86_64-0.0.git.19.337ce2ed-1.fc39.x86_64.rpm
kmod-bmi323-6.6.14-201.fsync.fc39.x86_64-0.0.git.5.844ec2b6-1.fc39.x86_64.rpm
STEP 10/10: RUN ls /tmp/rpms/kmods | grep bmi
kmod-bmi260-6.6.14-201.fsync.fc39.x86_64-0.0.git.19.337ce2ed-1.fc39.x86_64.rpm
kmod-bmi323-6.6.14-201.fsync.fc39.x86_64-0.0.git.5.844ec2b6-1.fc39.x86_64.rpm
so now it's just an RPM fusion problem. OK cool. I learned stuff today!
HikariKnight
HikariKnight5mo ago
we love rpmfusion problems /s
Noel
Noel5mo ago
Bazzite is now building!
1/4 Life
1/4 Life5mo ago
Yeah and all it took was
̴̖̃ ̶͂͛ ̶̛̉ ̸̳̾r̵̓̆p̶̽̀m̵̋̓-̴̓̌o̵͋̈s̴̅t̷̔͂r̸ee overrid̂ë̴͝ ̷͗͝replace͝ ̸̆̄\̴͑͑
̶̆̉ ̶̘̓ --expér̵ì̶̕m̶̋̑e̵̓̓n̵̋̕t̸̍̐a̸̛l \
͘ --f̶͛͒r̴͂͝o̷m repo̎͝=̴̽͋ù̵̽p̴̾̐d̴͘ates \
̾ ̴̢̉ ̵̄͝ ̸͐̑ ̶̋͠ ̶͒͑ ̵͌glibc \̸͗
̵͝ͅ ̷͂ glib̭̚c̴̚͠-̷̋̾c̵̚o̷̓̚m̴̿mon \
̆ ̶́̚ ̸̪́ ̷͔̉ ̴̑ ̶̈́̎g̸̒̚libc-al̸͝l-lan̴͐g̃̽p̶acks \̴̎ͅ
̷̒̆ ̵͐̍ ̸͈͌ ̸͌̅ glibc-̶̈́͊g̷̈́̇c̸̅̆ơ̶̽n̶͛͗v̸̈͊-extrá̏ \
̃ ̷̐̇ ̷ ||̴͂̎ ̷͊tr̸͖̈́u̷̪̓è̵̽ ̶&& \
̴̖̃ ̶͂͛ ̶̛̉ ̸̳̾r̵̓̆p̶̽̀m̵̋̓-̴̓̌o̵͋̈s̴̅t̷̔͂r̸ee overrid̂ë̴͝ ̷͗͝replace͝ ̸̆̄\̴͑͑
̶̆̉ ̶̘̓ --expér̵ì̶̕m̶̋̑e̵̓̓n̵̋̕t̸̍̐a̸̛l \
͘ --f̶͛͒r̴͂͝o̷m repo̎͝=̴̽͋ù̵̽p̴̾̐d̴͘ates \
̾ ̴̢̉ ̵̄͝ ̸͐̑ ̶̋͠ ̶͒͑ ̵͌glibc \̸͗
̵͝ͅ ̷͂ glib̭̚c̴̚͠-̷̋̾c̵̚o̷̓̚m̴̿mon \
̆ ̶́̚ ̸̪́ ̷͔̉ ̴̑ ̶̈́̎g̸̒̚libc-al̸͝l-lan̴͐g̃̽p̶acks \̴̎ͅ
̷̒̆ ̵͐̍ ̸͈͌ ̸͌̅ glibc-̶̈́͊g̷̈́̇c̸̅̆ơ̶̽n̶͛͗v̸̈͊-extrá̏ \
̃ ̷̐̇ ̷ ||̴͂̎ ̷͊tr̸͖̈́u̷̪̓è̵̽ ̶&& \
Noel
Noel5mo ago
lol what the fuck is this font?
1/4 Life
1/4 Life5mo ago
Zalgo Text Generator - Create Glitchy Text Online
Zalgo Text Generator is a free tool to convert your text into glitch text. However, the Zalgo text is a glitchy form of normal text. You can also UnZalgo the scary or Halloween style text to normal text.
Noel
Noel5mo ago
lol you absolute meme lord I had to do a double take to make sure what we did didn't fuck up my fonts on my image I was like, is it like this on my phone? XD I lied: https://github.com/ublue-os/bazzite/actions/runs/7737876562/job/21097628490
1/4 Life
1/4 Life5mo ago
nah that's just the cockpit one and it's building again now had to wait 30 minutes because of all the github api spam
Noel
Noel5mo ago
RIP I’m sure you all saw, but Bazzite Surface Kernel signing is failing: https://github.com/ublue-os/bazzite/actions/runs/7743218443/job/21114151668
EyeCantCU
EyeCantCU5mo ago
Probably has something to do with the other Surface Linux packages. I won't be able to take this one up until later today unfortunately Is this new?
HikariKnight
HikariKnight5mo ago
i looked at the last successful sign for the surface image and that one has different sed and grep values seems like the grep and sed changed from kernel- to kernel-surface-
EyeCantCU
EyeCantCU5mo ago
Kernel surface devel is getting pulled in somehow We can't use uname because we get the host kernel so I search for installed kernel packages within the container. Probably a better way to do it
HikariKnight
HikariKnight5mo ago
i can probably regex it if you tell me exactly what you want and we can test if that will work with sed -E or you can just inverse grep the devel packages first with grep -v 🤔
HikariKnight
HikariKnight5mo ago
@EyeCantCU would this work for you? rpm -qa | grep -P "kernel-(\d+\.\d+\.\d+)"
No description
HikariKnight
HikariKnight5mo ago
can even do rpm -qa | grep -P "kernel-(|asus-|surface-)(\d+\.\d+\.\d+)" and it should work with asus, surface, etc kernels too
HikariKnight
HikariKnight5mo ago
No description
EyeCantCU
EyeCantCU5mo ago
We just need it for Surface. No one else renames their kernel. That would likely work!
HikariKnight
HikariKnight5mo ago
also means you dont need that if surface kernel check too 😉 here is the full command you will need @EyeCantCU i do not trust my network today rpm -qa | grep -P 'kernel-(|surface-)(\d+\.\d+\.\d+)' | sed -E 's/kernel-(|surface-)//' it will also match kernel version 203.11.444 if it ever came to that 😂 opened a PR to get it added as network has been stable the last few hours. still no idea how the old code grabbed the devel package
EyeCantCU
EyeCantCU5mo ago
All right, going to get a fix up for this here in 30. Sorry for the delay guys
Noel
Noel5mo ago
no worries! I wonder if main is still broken..
EyeCantCU
EyeCantCU5mo ago
I'll have to look. What happened in main?
Noel
Noel5mo ago
issues with mesa due to lack of updates from RPM fusion https://github.com/ublue-os/main/actions/runs/7743261935 most recent attempt.
EyeCantCU
EyeCantCU5mo ago
Can have a deeper look at that but ultimately we might have to wait it out
Noel
Noel5mo ago
Yeah, that is what @1/4 Life was saying unless we get our own repos going. That's still very much in a POC phase. Bazzite is failing again... our workaround is not working anymore 😦
1/4 Life
1/4 Life5mo ago
That's ok, lasted as long as it needed to Rpmfusion should have their shit together soon Never takes more than a week
Noel
Noel5mo ago
yeah, I just have shit I want to add to my own image.
1/4 Life
1/4 Life5mo ago
If you do from bazzite it should still build, no?
Noel
Noel5mo ago
Bazzite isn't building either. https://github.com/ublue-os/bazzite/actions/runs/7761778999
error: Could not depsolve transaction; 1 problem detected:
Problem: conflicting requests
- package mesa-vdpau-drivers-freeworld-23.2.1-2.fc39.x86_64 from rpmfusion-free requires mesa-filesystem(x86-64) = 23.2.1, but none of the providers can be installed
- package mesa-vdpau-drivers-freeworld-23.3.4-1.fc39.x86_64 from rpmfusion-free-updates requires mesa-filesystem(x86-64) = 23.3.4, but none of the providers can be installed
- cannot install both mesa-filesystem-23.2.1-2.fc39.x86_64 from fedora and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.x86_64 from @System
- cannot install both mesa-filesystem-23.3.4-1.fc39.x86_64 from updates and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.x86_64 from @System
- cannot install both mesa-filesystem-23.3.4-1.fc39.x86_64 from updates-archive and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.x86_64 from @System
error: Could not depsolve transaction; 1 problem detected:
Problem: conflicting requests
- package mesa-vdpau-drivers-freeworld-23.2.1-2.fc39.x86_64 from rpmfusion-free requires mesa-filesystem(x86-64) = 23.2.1, but none of the providers can be installed
- package mesa-vdpau-drivers-freeworld-23.3.4-1.fc39.x86_64 from rpmfusion-free-updates requires mesa-filesystem(x86-64) = 23.3.4, but none of the providers can be installed
- cannot install both mesa-filesystem-23.2.1-2.fc39.x86_64 from fedora and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.x86_64 from @System
- cannot install both mesa-filesystem-23.3.4-1.fc39.x86_64 from updates and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.x86_64 from @System
- cannot install both mesa-filesystem-23.3.4-1.fc39.x86_64 from updates-archive and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.x86_64 from @System
I get something slightly different because I don't include mesa-vdpau-drivers-freeworld
error: Could not depsolve transaction; 1 problem detected:
Problem: package mesa-va-drivers-freeworld-23.2.1-2.fc39.i686 from rpmfusion-free requires mesa-filesystem(x86-32) = 23.2.1, but none of the providers can be installed
- cannot install both mesa-filesystem-23.2.1-2.fc39.i686 from fedora and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.i686 from @System
- conflicting requests
- nothing provides mesa-filesystem(x86-32) = 23.3.4 needed by mesa-va-drivers-freeworld-23.3.4-1.fc39.i686 from rpmfusion-free-updates
error: Could not depsolve transaction; 1 problem detected:
Problem: package mesa-va-drivers-freeworld-23.2.1-2.fc39.i686 from rpmfusion-free requires mesa-filesystem(x86-32) = 23.2.1, but none of the providers can be installed
- cannot install both mesa-filesystem-23.2.1-2.fc39.i686 from fedora and mesa-filesystem-23.3.3-100.bazzite.0.0.git.2650.e43786eb.i686 from @System
- conflicting requests
- nothing provides mesa-filesystem(x86-32) = 23.3.4 needed by mesa-va-drivers-freeworld-23.3.4-1.fc39.i686 from rpmfusion-free-updates
Still to do with mesa. There is actually a very recent fedora thread of someone running into this issue: https://discussion.fedoraproject.org/t/error-updating-through-discover-after-adding-media-codec-support-to-kinoite/104100 either way, not the end of the world, it's more just annoying 🙂
1/4 Life
1/4 Life5mo ago
Right but doing from means it uses the last good build Which is gonna have rpmfusion mesa in it As long as you don't also touch it yours should build fine Makes it exclusively my issue lol
Noel
Noel5mo ago
lol that's true. it's more or less hidden 😛