09:18 <glehmann> would adding marge as a member to my fork work around https://gitlab.com/gitlab-org/gitlab/-/issues/521993 ?

09:34 <MrCooper> glehmann: yes, it does

09:34 <glehmann> would it have an downsides?

09:35 <MrCooper> not aware of any offhand

09:37 <f_> gitlab pages seem to be broken

09:37 <f_> https://wayback.freedesktop.org/ returns 500

09:38 <f_> and networkmanager docs also return the same error

09:38 <glehmann> MrCooper: thanks, I will give it a try then

09:40 <daniels> cwabbott: shrug, looks from that job like s3 was failing to serve the kernel (and we confusingly failed to detect that) and crosvm refused to boot a zero-sized kernel image. in the job before that which got retried, we sat around waiting for 5 minutes for it to answer HTTP requests and it didn't. not sure if it was a transient load spike or network gremlins, but nothing structural to be done

09:43 <bentiss> f_: likely related to https://status.hetzner.com/incident/8b973d3d-b110-474e-a9bf-5ad55cb20446

09:47 <Ermine> > network gremlins --- I'll remember this one

09:47 <f_> bentiss: ok, good to know

12:51 <demarchi> any idea what are these errors while rebuilding drm-maintainer's build container?

12:51 <demarchi> https://gitlab.freedesktop.org/rodrigovivi/maintainer-tools/-/jobs/83321113#L699

12:52 <demarchi> Copying blob sha256:67a5b54ece0064d8bbaac7909616b4078529f38a033259d03372ad0a538160e8

12:52 <demarchi> Error: trying to reuse blob sha256:67a5b54ece0064d8bbaac7909616b4078529f38a033259d03372ad0a538160e8 at destination: Requesting bearer token: invalid status code from registry 500 (Internal Server Error)

13:04 <demarchi> rodrigovivi: maybe because I pushed to your MR? Maybe try pushing again with the same content... ?

13:14 <zmike> daniels: that trace checksum thing still isn't fixed ?

13:46 <demarchi> just tried to split the update-to-fedora-42 part in another MR and it passed

13:46 <demarchi> https://gitlab.freedesktop.org/demarchi/maintainer-tools/-/jobs/83327692

13:47 <demarchi> rodrigovivi: ok to merge the MR and then you rebase yours on top (don't forget to also change the container tag)

13:49 <rodrigovivi> demarchi: definitely!

14:00 <demarchi> rodrigovivi: done

14:44 <tuliom> I'm trying to report a regression to wireplumber. My account is new and has just been verified, but I'm getting an error message saying my report "has been recognized as spam". Is there a delay between the verification of the account and being allowed to create new issues?

15:12 <bentiss> tuliom: there is a delay between account creation/verification and automated trust. I ǘe manually trusted you so you should be good

15:23 <tuliom> bentiss: thank you! It worked now.