01:13 <alanc> I only see git gc & repacke in the "Housekeeping" option in the UI, but it looks like the libX11 repo needs a fsck - is there any way to do that? See https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/150 for details

01:27 <daniels> fsck only flags those errors, which are checks introduced since after the tags were made; you need to delete and recreate the tags

02:22 <alanc> I see there's a script in https://github.com/collectd/collectd/issues/2115 which may help with that - can try that tomorrow

09:41 <bentiss> finally... no 504 errors in 33 hours and the backups are working fine too :)

10:01 <emersion> nice

10:01 <emersion> let me know when the next gitlab upgrade comes in, would be nice to learn how to do these

10:15 <bentiss> emersion: just make sure to subscribe to MRs on helm-gitlab-omnibus, we have a scheduled pipeline that checks for new releases there, so just jump in the MR if you want to test something :)

10:17 <emersion> ack

10:23 <bentiss> emersion: on that note: generally upgrading a minor version (14.6.1 to 14.6.2 for example) is flawless. Upgrading between majors (14.6 to 14.7) usually requires a review of the changes as there might be some impact in the way we deploy things (with a separate nginx)

10:24 <emersion> i see

10:24 <bentiss> emersion: also we tend to not jump on the new version ASAP, (except for security ones) because often after a major release we see a minor coming in a couple of days later :)

10:25 <emersion> yea that makes sense

10:26 <bentiss> anyway, this can be discussed in each MR if needed :)

11:36 <kusma> daniels: Seems there's some issues with the windows builders: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/17576595#L20

11:37 <daniels> alatiera: ^ can you please kick them?

11:37 <alatiera> sure thing

11:41 <alatiera> kicked

11:59 <daniels> thanks a lot!

12:20 <kusma> Awesome, kicking helped :)