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
ity has quit []
ity has joined #freedesktop
bnieuwenhuizen has quit [Quit: Bye]
bnieuwenhuizen has joined #freedesktop
pixelcluster has quit [Ping timeout: 480 seconds]
pixelcluster has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
Leopold_ has quit []
Leopold_ has joined #freedesktop
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #freedesktop
karolherbst_ has joined #freedesktop
karolherbst has quit [Ping timeout: 480 seconds]
privacy has quit [Quit: Leaving]
mrkomododragon has joined #freedesktop
<mrkomododragon>
hello, i am mrkomdodragon and I would like contribute to XKB, by adding a layout called tamil ITRANS. my question is, can xkb handle a sequence of keys and output a code. The reason is this is a phonetic keyboard, and several latin characters are used to refer to a singular tamil letter
AbleBacon has quit [Read error: Connection reset by peer]
Leopold_ has quit [Remote host closed the connection]
Leopold has joined #freedesktop
Leopold has quit [Remote host closed the connection]
Leopold has joined #freedesktop
mrkomododragon has quit [Ping timeout: 480 seconds]
Leopold has quit [Remote host closed the connection]
<DavidHeidelberg>
cont of CI the HASH discussion. I think we could go from KERNEL_TAG: "v6.6.12-for-mesa-ci-5a92d0709d0b" to v6.6.12-5a92d0709d0b (as vignesh suggested)
<DavidHeidelberg>
even maybe reducing 12 chars of hash could go to 7, since we using the version and usually having only few tags per one mainline/stable/next release
<DavidHeidelberg>
what I'm thinking if keeping the mesa in "vX.Y.Z-mesa-$hash" would make sense
sergi has joined #freedesktop
<sergi>
DavidHeidelberg: How may characters in this hash? How many tags we would need for the same x.y.z kernel to avoid collisions?
Leopold_ has joined #freedesktop
<DavidHeidelberg>
sergi: IMHO 4 would be enough, but I assume convention is not go below 7
GNUmoon has quit [Remote host closed the connection]
<sergi>
DavidHeidelberg: We use the hash field as an identifier within and identifier of the kernel version. This number is more our balance to avoid collisions in the naming that any cryptographic meaning about hash functions. Let's start with 4 and if we see a collision we can reevaluate.
<sergi>
The combination of image-tag fields in MesaCI usually goes close to the limit to name the containers. We need to maintain collectively this with small fields. I would suggest the use of a minimal number of characters in hashes, just thought to avoid tag recycling when a new one is expected.
<sergi>
sergi: We can reduce the dashes between date fields separator. Dates YYYY-MM-DD can give us two extra characters by removing those dashes.
<sergi>
sergi: There is another place to save characters, in the field separator between fields, in this docker image construction. It is currently two dashes (as we use single dashes as in field separators).
<DavidHeidelberg>
sergi: 4 chars making me sweaty when I'll be pushing new kernels, but why not :D
<DavidHeidelberg>
I think I can bump kernel with Tomeu etnaviv ML patches (which aren't in yet)
<tomeu>
I will add a commit to my MR disabling the farm, if you don't mind
<jasuarez>
Sure
<ishitatsuyuki>
could the gmail delivery issues be due to missing SPF, DKIM and DMARC? the gitlab emails seems to be authenticated with none of them.
<DavidHeidelberg>
ishitatsuyuki: for ML you cannot use all of them, but at least one could be implemented. but for example I think DMARC isn't that valuable (which can be done I guess)
<ishitatsuyuki>
well, there's the new guideline thing at https://support.google.com/a/answer/81126. It seems SPF & DKIM are required, and DMARC needs to be set up but can be set to none
<DavidHeidelberg>
I recall the issue with SPF was when you send email to ML and ML resend the email, you would have to define ML in your SPF record, but maybe thats history? (been few years I setup postfix)
<DavidHeidelberg>
tomeu: I can turn off the farm in separate MR or u want to?
<tomeu>
is that the fix?
<tomeu>
I can do that if so
<tomeu>
ah, read your comment now
<DavidHeidelberg>
yup, there is explicitly stated that disabling/enabling farms shouldn't go with any other changes
<tomeu>
I can do it, no problem, thanks for explaining
<DavidHeidelberg>
usually when enabling farms, there can be the fails/flakes fixes :)
<DavidHeidelberg>
tomeu: nice thing we have these days that when you disable farm, it doesn't run almost anything in the pipeline
<DavidHeidelberg>
so separate MR isn't burden
<DavidHeidelberg>
Marge-bot doesn't feel well (I guess because of gitlab, since it was not showing my pipeline in preview even after refresh)
<DavidHeidelberg>
I deassigned, but I don't see any activity.