ChanServ changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
ybogdano has quit [Ping timeout: 480 seconds]
Seirdy has quit [Ping timeout: 480 seconds]
Seirdy has joined #freedesktop
jarthur has quit [Ping timeout: 480 seconds]
emanuele6 has quit [Ping timeout: 480 seconds]
alatiera has quit [Quit: Ping timeout (120 seconds)]
alatiera has joined #freedesktop
alatiera is now known as Guest4761
emanuele6 has joined #freedesktop
agd5f has quit [Remote host closed the connection]
agd5f has joined #freedesktop
ximion has quit []
rando25892 has joined #freedesktop
chomwitt has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
rando25892 has quit [Quit: off for now]
danvet has joined #freedesktop
chomwitt has quit [Ping timeout: 480 seconds]
rando25892 has joined #freedesktop
chomwitt has joined #freedesktop
ximion has joined #freedesktop
ximion has quit []
Guest4761 has quit [Read error: Connection reset by peer]
<daniels>
nah, it’s that the project was set as internal
<MrCooper>
huh, that affects packet runners but not Hetzner ones?
<MrCooper>
the other build jobs ran on the latter and passed
<daniels>
right, the Hetzner ones would've authenticated to the registry with the credentials from the job and completed
<daniels>
the Packet ones would've hit the cache, which doesn't do authentication because why would we need to, and bounced off it
<MrCooper>
gotcha
<pq>
does that mean that non-public repositories on fd.o are... expected to have various problems?
<pq>
should there be a policy on fd.o then that all repositories must be always public?
<pq>
but then things like the wayland-security repo...
<daniels>
basically, yeah
<daniels>
it's very much the case that we'll do what we can do to make legitimate cases work, but short of security there are almost no legitimate cases for having private repos there
<daniels>
(the CI aspect in particular is something which will get fixed as the new container registry continues to get introduced, and there are workarounds available)
jeramiah has joined #freedesktop
vsyrjala has quit [Ping timeout: 480 seconds]
pendingchaos has quit [Quit: Quit]
thelounge51 is now known as alatiera
vsyrjala has joined #freedesktop
pendingchaos has joined #freedesktop
rando25892 has quit [Quit: No windows for this server]
chomwitt has quit [Ping timeout: 480 seconds]
<ndufresne>
I think we are seeing more of these recently in GStreamer project (internal projects)
<ndufresne>
I wonder if some default settings for forks have changed ?
<daniels>
nope, see conversation from Monday
<daniels>
I don't know why it's happening, but it's not a default setting that all new forks should be private or internal
<emersion>
daniels, bentiss: we've recently migrated wlroots from github to gitlab.fdo (\o/), but i now realize we're hitting an issue wrt CI and forks
<emersion>
we're using our own CI runners, this works perfectly fine for the project's branches
<emersion>
however as soon as someone tries to fork the project, gitlab tries to use their runners, whcih aren't able to run our CI
<emersion>
(gitlab doesn't find a suitable runner, so the jobs are stuck)
<emersion>
so i have a request: would it be possible to register a shared runner?
<emersion>
the shared runner has a tag, so won't run normal CI jobs
<daniels>
sure, though I didn't realise wlroots was moving tbh - usually that goes through a new-project request in an issue
<emersion>
we requested the wlroots namespace a whiole ago -- probably that's why you don't remmeber
<daniels>
that being said I didn't chase the mail on sitewranglers@, so