02:37 <ukky> beerman: did you figure out why you had permission issues building mesa? I might have experienced the same/similar problem with a few ports, including mesa, when building in chroot container.

08:40 <beerman> jaeger no, it isn't, didn't for me

08:40 <beerman> ukky: no, didn't investigate any further and locked meson at the older version

09:56 <jue> jaeger: run into the same problem, build of qt6-base fails if old version is installed

10:06 <Romster> winehq.org seems down but dl.winehq.org worked

10:13 <Romster> ok it's very slow but now it loads

10:19 <beerman> jue interesting.. haven't hit that on two machines

13:06 <ukky> beerman: Try starting your container as real root user (non-sudo) and build mesa in the container. Then try starting your container as sudo user and build mesa. It seems 'meson' drops privileges to a user defined by SUDO_UID, if defined.

15:20 <beerman> ukky: the container (lxc) runs as root

15:39 <ukky> do you start lxc container as 'sudo lxc-start', or you login as root (actual login, or 'su --login root'), and then do 'lxc-start' as root?

15:53 <beerman> opendoas, but yeah

16:56 <ukky> In my opinion, that is the issue with 'meson'. If meson can detect non-privileged user which started the container via sudo/opendoas, it will drop privileges to that user. In your case, when building mesa, meson will try to write as non-privileges user to log file owned by root.

17:13 <beerman> mh, very weird, how does it do that?

17:17 <ukky> I do not know python well enough, but it is somewhere along the lines here: https://github.com/mesonbuild/meson/pull/11667/files

17:19 <beerman> cheers

17:20 <ukky> But I do not know if that is the case for your mesa build failure.

17:21 <beerman> i'm trying out the patch right now

17:24 <ukky> For me it was the exact reason. I was building CRUX ISO bootstrap target in chroot container and plenty of ports failed build due to missing user with UID 1000. And chroot container did not have user with UID 1000, so meson was dropping privileges to a user that started /usr/bin/chroot.

17:37 <beerman> yeah, seems like thats it for me as well, even on the desktop, which doesn't quite fit the use-case, but oh well

17:51 <ukky> For me, I did not apply the patch building ISO. I think dropping privileges is a good thing. But dropping privileges in chroot/lxc container makes no sense.

18:02 <beerman> well, its merged so it will be included in the next release