<@alexsaezm:fedora.im>
18:00:19
!startmeeting Go SIG meeting
<@meetbot:fedora.im>
18:00:21
Meeting started at 2026-10-19 18:00:19 UTC
<@meetbot:fedora.im>
18:00:21
The Meeting name is 'Go SIG meeting'
<@alexsaezm:fedora.im>
18:00:24
!topic Roll Call
<@alexsaezm:fedora.im>
18:00:27
Hi everyone! As always we'll wait ~5 minutes for everyone to join.
<@buckaroogeek:fedora.im>
18:03:15
!hi
<@zodbot:fedora.im>
18:03:16
Brad Smith: Brad Smith (buckaroogeek)
<@alexsaezm:fedora.im>
18:05:12
Hi!
<@alexsaezm:fedora.im>
18:05:57
Ok, 5 minutes passed...
<@alexsaezm:fedora.im>
18:06:35
I don't see anything tagged for the meeting
<@alexsaezm:fedora.im>
18:06:57
So I think we can move on to the open floor. I think it will be a quick one
<@alexsaezm:fedora.im>
18:06:58
!topic Open Floor
<@buckaroogeek:fedora.im>
18:07:25
I cannot think of anything for open floor
<@alexsaezm:fedora.im>
18:07:59
I just uploaded the patch we were talking about for the rootlesskit to golang-x-sys https://src.fedoraproject.org/rpms/golang-x-sys/pull-request/33#
<@alexsaezm:fedora.im>
18:08:14
(oh and it failed :D)
<@mikelolasagasti:matrix.org>
18:09:06
!hi
<@zodbot:fedora.im>
18:09:11
mikel: Mikel Olasagasti Uranga (mikelo2)
<@alexsaezm:fedora.im>
18:09:12
Interesting... maybe the solution has more nuance that I expected... in any case, as mikel said that there were several affected packages by this PIE issue, I will try to add it to golang-x-sys as soon as possible
<@mikelolasagasti:matrix.org>
18:09:28
i realized that `chezmoi` is affected also
<@mikelolasagasti:matrix.org>
18:09:40
everything that depends on `fatih/color`
<@mikelolasagasti:matrix.org>
18:10:16
I don't know what `fedrq` spell could show the list of possibly affected packages
<@alexsaezm:fedora.im>
18:11:23
is it also on a test?
<@mikelolasagasti:matrix.org>
18:12:22
I don't recall :/
<@mikelolasagasti:matrix.org>
18:12:52
checking...
<@mikelolasagasti:matrix.org>
18:13:04
yes
<@mikelolasagasti:matrix.org>
18:13:06
https://kojipkgs.fedoraproject.org//work/tasks/211/151380211/build.log
<@alexsaezm:fedora.im>
18:14:16
I guess any package that builds on ppc64le that uses x/sys as dependency
<@alexsaezm:fedora.im>
18:14:26
because all the x/sys versions are affected
<@buckaroogeek:fedora.im>
18:14:38
I had another go package fail in COPR only on ppc64le: SIGSEGV: segmentation violation: https://copr.fedorainfracloud.org/coprs/buckaroogeek/utils/build/11169474/
<@buckaroogeek:fedora.im>
18:15:06
i think x/sys is also involved
<@buckaroogeek:fedora.im>
18:15:32
but have not looked too closely as not many people use it, esp on that architecture
<@alexsaezm:fedora.im>
18:17:13
```
<@alexsaezm:fedora.im>
18:17:13
dnf --forcearch=ppc64le repoquery \
<@alexsaezm:fedora.im>
18:17:13
--enablerepo='*-source' \
<@alexsaezm:fedora.im>
18:17:13
--arch=src \
<@alexsaezm:fedora.im>
18:17:13
--whatrequires 'golang(golang.org/x/sys/unix)' \
<@alexsaezm:fedora.im>
18:17:13
--qf '%{name}' | sort -u
<@alexsaezm:fedora.im>
18:17:13
```
<@alexsaezm:fedora.im>
18:17:13
maybe?
<@alexsaezm:fedora.im>
18:17:29
for the query I mean
<@alexsaezm:fedora.im>
18:17:50
I tried it on a ppc64le machine right now and... it prints stuff ™️
<@alexsaezm:fedora.im>
18:18:10
ok, no, because it doesn't print rootlesskit
<@mikelolasagasti:matrix.org>
18:18:30
it doesn't require, it bundles it
<@alexsaezm:fedora.im>
18:18:39
oooh right right
<@mikelolasagasti:matrix.org>
18:18:44
so it would be a provides bundled, not whatrequires
<@alexsaezm:fedora.im>
18:19:17
```dnf --forcearch=ppc64le repoquery \
<@alexsaezm:fedora.im>
18:19:17
--whatprovides 'bundled(golang(golang.org/x/sys))' \
<@alexsaezm:fedora.im>
18:19:17
--qf '%{sourcerpm}' | sort -u```
<@alexsaezm:fedora.im>
18:19:26
```
<@alexsaezm:fedora.im>
18:19:26
dnf --forcearch=ppc64le repoquery \
<@alexsaezm:fedora.im>
18:19:26
--whatprovides 'bundled(golang(golang.org/x/sys))' \
<@alexsaezm:fedora.im>
18:19:26
--qf '%{sourcerpm}' | sort -u
<@alexsaezm:fedora.im>
18:19:26
```
<@alexsaezm:fedora.im>
18:19:37
a bunch of them
<@alexsaezm:fedora.im>
18:20:12
```
<@alexsaezm:fedora.im>
18:20:12
dnf --forcearch=ppc64le repoquery \
<@alexsaezm:fedora.im>
18:20:12
--whatprovides 'bundled(golang(golang.org/x/sys))' \
<@alexsaezm:fedora.im>
18:20:12
--qf '%{sourcerpm}\n' | sort -u
<@alexsaezm:fedora.im>
18:20:12
```
<@alexsaezm:fedora.im>
18:20:32
231 if I am not mistaken
<@mikelolasagasti:matrix.org>
18:20:41
it's a pretty common dep
<@alexsaezm:fedora.im>
18:21:34
well... I guess that if I fix the golang-x-sys failure that I have right now I can release an update
<@alexsaezm:fedora.im>
18:21:42
and... that will be it
<@mikelolasagasti:matrix.org>
18:22:41
I don't know if it's complex to patch golang with it, but it would safe lot of "downstream" work
<@alexsaezm:fedora.im>
18:23:23
so the question that I have is... do I need to fix it on golang-x-sys or in golang
<@alexsaezm:fedora.im>
18:23:29
that's what confuses me right now
<@alexsaezm:fedora.im>
18:23:34
I thought it was on golang-x-sys
<@mikelolasagasti:matrix.org>
18:25:34
i don't know if `unix/asm_linux_ppc64x.s` is used by Go during build time or only if golang-x-sys is used
<@alexsaezm:fedora.im>
18:26:12
I checked the logs and at least it seems that rootlesskit pulled golang-x-sys
<@alexsaezm:fedora.im>
18:26:29
go won't use it during build time (as far as I know)
<@alexsaezm:fedora.im>
18:27:34
!action @alexsaezm will fix x/sys on ppc64le and ping the Go SIG room
<@alexsaezm:fedora.im>
18:29:22
Is there anything else to cover?
<@buckaroogeek:fedora.im>
18:29:36
Nothing from me
<@mikelolasagasti:matrix.org>
18:29:47
no
<@alexsaezm:fedora.im>
18:30:23
in that case we can call it and I will try to no burn ppc64le 😄
<@buckaroogeek:fedora.im>
18:30:39
Have lots of fun!
<@alexsaezm:fedora.im>
18:30:58
I'll try 😄
<@alexsaezm:fedora.im>
18:31:14
Thanks everyone! See you next time!
<@alexsaezm:fedora.im>
18:31:20
!endmeeting