Bhere @Robert (p5)
Bso, yeah, as my normal silverblue user
I ran:
I ran:
podman build -f Containerfile --build-arg BASE_TAG=40 -t lumina:40 and did not have the tar permissions issueBbut, i have actually seen another weird issue with podman build which is only repoducible on some users and not others
RDoes your build contain the --no-same-permissions tar flag? It will depend on when you pulled the code
Bit does not contain that, i pulled right before you added
B2d3236a42ad08189345ca1b3b1c95c57edf57056
Rokay.. So somehow this is a Podman / Buildah bug which is fixed in newer versions?
BI DID have to comment out the ptyxis stuff to get a build though>
Bbecuase i was getting this failure and it stopped the build
error: Request to reinstall exact base package versions: gtk4 libadwaitaRYeah, that ptyxis stuff is fixed on the PR branch. Added a flag to only install those two deps on F39
Bwant me to try your branch?
RIt shouldn't really make a difference I don't think. Unless Ptyxis is causing the issues, which seems unlikely
Bagreed
Bso, the other problem i mentioned...
as my user on my main (custom silverblue) machine, i'm unable to do a build of akmods or hwe which uses the surface kernel...
but it does work on my bazzite machine
as my user on my main (custom silverblue) machine, i'm unable to do a build of akmods or hwe which uses the surface kernel...
but it does work on my bazzite machine
Bi need to test again (i've lost track) but it may even work on my main machine, but with a different user
RKinda wanting to switch to Docker. We may have less of these bugs, but it may also not fix anything
Bheh
Bit does feel like there's something environmental bleeding into the build container
Bbut hard to troubleshoot
Ryeah the whole thing is odd
Rusing --no-same-permissions is a shot in the dark, even if it works I'll be confused
Rbecause it will use the root user's umask
Rwhich is wonky
Byeah, so i've just confirmed, on my weird problem i mentioned... it's user specific... another user on my main machine CAN build surface image with the custom kernel, just not my main user
R@bsherman do both the users have the same umask?
Rand do they both have the same permissions?
Ras in neither is root 
Bright, both are users with wheel group membership, but not root
Rand same umask?
Byes, both have 0022
R
super weirdRScrew it. Switching to building inside Docker and Buildx so hopefully there's more consistency. Builds will be slower.
R@Robert (p5) did the flag work tho
Bthe tar --no-same-permissions flag? i haven't tested that locally
Bit really doesn't feel like that's the problem though
Rprobably not
RI'm unable to build locally since I'm on my locked down MacBook, and GitHub Actions is having issues right now. Will try the workflow again
Boh github actions
Bjoy
RIt always happens when I'm trying to do something. On the rest days, no availability issues
Bi feel ya
NGitHub
Run your GitHub Actions locally 
. Contribute to nektos/act development by creating an account on GitHub.
. Contribute to nektos/act development by creating an account on GitHub.Band actually, with act, all stuff runs in container, but buildah/podman can't work
Bbut... buildx can
