daniels 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
privacy has joined #freedesktop
scrumplex has joined #freedesktop
scrumplex_ has quit [Ping timeout: 480 seconds]
Ojus1_ has quit [Remote host closed the connection]
AbleBacon has quit [Read error: Connection reset by peer]
linyaa has quit [Read error: Connection reset by peer]
linyaa has joined #freedesktop
ximion has quit [Quit: Detached from the Matrix]
krushia has quit [Quit: Konversation terminated!]
todi has quit [Remote host closed the connection]
privacy has quit [Remote host closed the connection]
bmodem has joined #freedesktop
pzanoni has quit [Ping timeout: 480 seconds]
alice has quit [Remote host closed the connection]
alice has joined #freedesktop
sima has joined #freedesktop
hir0pro has joined #freedesktop
ofourdan has joined #freedesktop
mvlad has joined #freedesktop
tzimmermann has joined #freedesktop
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
samuelig has quit []
samuelig has joined #freedesktop
<MrCooper>
I got a reminder e-mail about the X.org election, but I can't vote, the members page says my membership application is being processed
<sad_plan>
hello, theres an issue with dubplicate certs on archive.mesa3d.org. is there someone here that could look into this? or would it be better if I sent an email to the mailing list instead?
<lynxeye>
X.org election reminder seems broken. I just got a mail claiming that I didn't vote yet, even though I voted a few days ago and the website confirms that I already voted.
<rg3igalia>
yep, there are a couple of issues with the last reminder
<rg3igalia>
I clicked the send reminder button instead of replying to the email thread to send a last reminder, but it turns out (a) it send the email to everyone, not only those who have not voted yet and (b) likely it sends the reminder also to people who have their membership application pending approval instead of only those already approved
<rg3igalia>
for process reasons, while a voting process is running, we must not approve new memberships
<MrCooper>
rg3igalia: not just "likely" for the latter, I reported exactly that an hour ago
<MrCooper>
it's a bit unfortunate, since when the original e-mail asking for renewals was sent, it wasn't actually possible to renew yet
<rg3igalia>
yes, there are two steps that must be done very close in time, which is sending the renewal email and opening the new membership period
<rg3igalia>
the process says "immediately" and this year it was not immediate at all
<rg3igalia>
several people have complained about the same
<rg3igalia>
it's our fault, definitely
<MrCooper>
I suspect I'm not the only one who missed renewing before the vote because of it
<rg3igalia>
you're not
<rg3igalia>
fortunately, compared to last year we're only down by ~10 people
<rg3igalia>
but still, that shouldn't have happened
<bentiss>
mupuf: for fixing hakzsam issue, we need someone (IIRC DavidHeidelberg) to migrate the kernel+rootfs from s3.fd.o/mesa-lava to s3.fd.o/mesa-rootfs. The latter has no expiration policy
<bentiss>
it was broken while the last attempt was done, but it's fixed now, so we really need that MR to go in
<mupuf>
Right....I guess the current rootfs has the file, so at this it is not lost
<mupuf>
But why use s3 and not Gitlab's package registry?
blatant has joined #freedesktop
<mupuf>
Requiring admins to do custom work for a project seems wrong to.me
<bentiss>
more global control, I guess (and s3 was available before pakcage registry was migrated to slef hosted)
<bentiss>
mupuf: the problem was in the setup of the new bucket. Now it's ready and can be freely used
<bentiss>
so no more admin time on it
blatant has quit []
<mupuf>
Well, I would rather we move to the package registry rather than this new bucket so that more people have a chance to fix issues when needed
<daniels>
it's the same thing as last time this came up - the kernel is uploading to the wrong bucket (the one which expires rather than the one which doesn't). there was an MR to fix it but I have no idea what happened to it since I haven't been looking at things. the way to fix it is to re-run the pipeline from gfx-ci/linux (no admin required here), which I've just done now, so it should be all good in 15 minutes
<daniels>
if you want to move to the package registry then please feel free to move to the package registry
<mupuf>
Great, thanks
<daniels>
s3 is not in and of itself causing any problems whatsoever
<mupuf>
It is making things more opaque than they have to be
<mupuf>
And manual work is error prone
<daniels>
if the kernel was being uploaded to the correct bucket (which is MRable and not requiring admin work), there would be no manual work ...
<bentiss>
personnally, between checking what is happening on s3 vs the package registry, I prefer s3, because I know exactly where things are and I can monitor it
<daniels>
but yeah, again, if you want to move to the package registry then you can MR it
<daniels>
you don't need me for anything here
<bentiss>
mostly because generic package uses the generic "artifacts" bucket on ceph, and this bucket is *very* opaque. But my advice doesn't count much here
<mupuf>
It is more opaque because it makes it impossible to know what project / branch generated the file
<mupuf>
You just have to know
<daniels>
afaict the package registry has no expiry at all, so we'd be carrying every kernel we built forever