2023-10-02 10:52:41 <ikke> algitbot: retry master
2023-10-02 19:47:30 <andypost[m]> algitbot: retry master
2023-10-03 05:27:41 <ikke> algitbot: retry master
2023-10-03 05:34:07 <ikke> algitbot: retry master
2023-10-03 09:51:07 <nmeum> ikke: ^ looks like the builders also seem to have some sort of network issues?
2023-10-03 09:51:35 <nmeum> ah wait that's just a 302
2023-10-03 10:19:10 <ikke> nmeum: I did see some ssl connect issues on the builder
2023-10-03 14:25:18 <andypost[m]> algitbot: retry master
2023-10-03 18:42:23 <ikke> algitbot: retry master
2023-10-03 21:29:41 <ptrc> ikke: no space left on device
2023-10-03 21:29:45 <ptrc> on aarch64
2023-10-03 21:46:15 <ptrc> algitbot: retry master
2023-10-04 04:23:04 <ikke> algitbot: retry master
2023-10-04 04:49:43 <ikke> algitbot: retry master
2023-10-04 04:55:38 <ikke> algitbot: retry master
2023-10-04 05:35:18 <ikke> algitbot: retry 3.18-stable
2023-10-04 10:22:39 <ikke> algitbot: retry master
2023-10-05 14:00:23 <ikke> algitbot: retry master
2023-10-05 19:55:03 <ikke> celie: checksum failure &
2023-10-05 19:55:05 <ikke> ^
2023-10-05 19:57:08 <andypost[m]> algitbot: retry master
2023-10-05 19:59:24 <andypost[m]> algitbot: retry master
2023-10-05 21:12:10 <andypost[m]> algitbot: retry master
2023-10-05 22:42:13 <andypost[m]> algitbot: retry master
2023-10-06 06:45:51 <rnalrd> algitbot:retry master
2023-10-06 06:46:05 <rnalrd> algitbot:retry edge
2023-10-06 09:45:58 <ptrc> typing-extensions, huh
2023-10-06 17:06:19 <nmeum> > ERROR: Clock skew detected. File /bin/busybox has a time stamp 12091.4603s in the future.
2023-10-06 17:07:15 <nmeum> was the clock updated by an ntp client between the busybox build and the spot build or something?
2023-10-06 18:48:25 <ikke> nmeum: I have no idea
2023-10-06 18:49:07 <ikke> Modify: 2023-10-06 20:27:21.000000000 +0000
2023-10-06 19:11:16 <ikke> nmeum: and it's on all arches, so unlikely that NTP shifted on all builders
2023-10-06 19:44:00 <ncopa> maybe it get confused by timezone?
2023-10-06 23:32:03 <andypost[m]> algitbot: retry master
2023-10-06 23:53:46 <andypost[m]> algitbot: retry master
2023-10-07 20:18:10 <PureTryOut> algitbot: retry master
2023-10-07 20:20:49 <PureTryOut> algitbot: retry master
2023-10-07 20:36:50 <PureTryOut> algitbot: retry master
2023-10-07 21:10:14 <ptrc> PureTryOut: ikona fails on `open64`, will need a proper fix
2023-10-07 21:10:22 <ptrc>           ikona_cli.3a4e10652c9e049a-cgu.0:(.text._ZN9getrandom9util_libc13open_readonly17hf453b83768d20ec9E+0xa): undefined reference to `open64'
2023-10-07 21:10:45 <PureTryOut> where do you see that?
2023-10-07 21:11:47 <ptrc> in the armv7 failure 
2023-10-07 21:11:56 <ptrc> posted here 22:36:06 by algitbot
2023-10-07 21:13:31 <PureTryOut> ah I missed that. Strange as neither the package nor it's dependencies actually changed it's contents
2023-10-07 21:14:19 <ptrc> yeah, it's musl 1.2.3 vs 1.2.4
2023-10-07 21:14:49 <ptrc> the *64 syscall symbols got hid behind a macro, but they shouldn't be used
2023-10-07 21:16:46 <PureTryOut> ah that explains it
2023-10-07 21:17:05 <PureTryOut> tbh the project hasn't had a commit in a year and no releases in 3 years. I might just drop it
2023-10-07 21:27:04 <PureTryOut> algitbot: retry master
2023-10-07 21:44:35 <andypost[m]> PureTryOut (matrix.org): qgpgme6 and qgpgme both installed for wacomtablet
2023-10-07 21:47:49 <PureTryOut> nah problem is just a missing include
2023-10-07 21:56:58 <PureTryOut> algitbot: retry master
2023-10-07 22:22:39 <PureTryOut> algitbot: retry master
2023-10-07 22:29:52 <andypost[m]> algitbot: retry master
2023-10-07 22:38:06 <andypost[m]> algitbot: retry master
2023-10-07 22:39:02 <andypost[m]> algitbot: retry master
2023-10-08 00:22:59 <andypost[m]> algitbot: retry master
2023-10-08 00:35:48 <andypost[m]> algitbot: retry master
2023-10-08 00:59:21 <andypost[m]> algitbot: retry master
2023-10-08 01:06:35 <andypost[m]> algitbot: retry master
2023-10-08 01:10:34 <andypost[m]> algitbot: retry master
2023-10-08 01:17:28 <andypost[m]> algitbot: retry master
2023-10-08 01:18:31 <andypost[m]> algitbot: retry master
2023-10-08 01:19:42 <andypost[m]> algitbot: retry master
2023-10-08 01:21:07 <andypost[m]> algitbot: retry master
2023-10-08 01:23:39 <andypost[m]> algitbot: retry master
2023-10-08 08:35:46 <PureTryOut> algitbot: retry master
2023-10-08 09:15:14 <PureTryOut> algitbot: retry master
2023-10-08 09:26:57 <PureTryOut> algitbot: retry master
2023-10-08 09:27:19 <PureTryOut> Damn xvfb on armv7
2023-10-08 09:29:40 <PureTryOut> algitbot: retry master
2023-10-08 09:32:28 <PureTryOut> algitbot: retry master
2023-10-08 09:37:31 <PureTryOut> algitbot: retry master
2023-10-08 09:59:19 <PureTryOut> algitbot: retry master
2023-10-08 10:02:15 <PureTryOut> algitbot: retry armv7
2023-10-08 10:02:15 <PureTryOut> algitbot: retry master
2023-10-08 10:05:43 <PureTryOut> algitbot: retry master
2023-10-08 10:08:29 <PureTryOut> algitbot: retry master
2023-10-08 10:20:06 <PureTryOut> algitbot: retry master
2023-10-08 10:24:44 <PureTryOut> algitbot: retry master
2023-10-08 10:29:09 <PureTryOut> algitbot: retry master
2023-10-08 10:36:10 <PureTryOut> algitbot: retry master
2023-10-08 10:41:22 <PureTryOut> algitbot: retry master
2023-10-08 10:45:03 <PureTryOut> algitbot: retry master
2023-10-08 10:53:30 <PureTryOut> algitbot: retry master
2023-10-08 10:58:33 <PureTryOut> algitbot: retry master
2023-10-08 11:04:08 <PureTryOut> algitbot: retry master
2023-10-08 11:05:08 <PureTryOut> algitbot: retry master
2023-10-08 11:15:31 <PureTryOut> algitbot: retry master
2023-10-08 11:23:12 <PureTryOut> algitbot: retry master
2023-10-08 11:24:42 <PureTryOut> algitbot: retry master
2023-10-08 11:26:45 <PureTryOut> algitbot: retry master
2023-10-08 11:29:53 <PureTryOut> algitbot: retry master
2023-10-08 11:31:48 <PureTryOut> algitbot: retry master
2023-10-08 11:36:40 <PureTryOut> algitbot: retry master
2023-10-08 13:46:51 <ptrc> algitbot: retry master
2023-10-08 14:09:29 <ikke> algitbot: retry master
2023-10-08 14:43:14 <ikke> algitbot: retry master
2023-10-08 14:51:17 <ikke> algitbot: retry master
2023-10-08 14:58:09 <ptrc> that's a segfault, isn't it?
2023-10-08 14:59:02 <ikke> yes
2023-10-08 14:59:22 <ikke> just trying to get the other packages built
2023-10-08 16:01:35 <PureTryOut> algitbot: retry master
2023-10-08 16:09:18 <ikke> PureTryOut: it segfaults during tests
2023-10-08 16:22:47 <ikke> algitbot: retry master
2023-10-09 09:32:49 <PureTryOut> algitbot: retry master
2023-10-09 09:34:23 <PureTryOut> Why is that suddenly failing wth, only on that arch too. I literally just bumped the pkgrel to change $replaces...
2023-10-09 09:34:41 <PureTryOut> algitbot: retry master
2023-10-09 09:35:35 <PureTryOut> Oh now it's x86 too lol
2023-10-09 09:36:00 <PureTryOut> algitbot: retry master
2023-10-09 09:53:39 <PureTryOut> algitbot: retry master
2023-10-09 10:39:32 <ikke> algitbot: retry 3.18-stable
2023-10-09 16:21:39 <celie> algitbot: retry master
2023-10-09 16:25:29 <celie> It appears the `rm t/11term-output-screen.c` line i removed from check() is actually needed...for the x86_64 builder
2023-10-09 16:26:16 <celie> Perhaps the builders for the other archs have some additional terminfo installed or something
2023-10-09 16:30:12 <celie> It's a bit late for me now...so if someone could please fix that for me, i would be grateful, maybe put in the comment that it causes the x86_64 builder to fail, so the next person that upgrades libtickit doesn't remove it again after seeing that it doesn't affect the CI
2023-10-09 16:32:43 <celie> Thanks in advance, and good night
2023-10-09 16:37:57 <ptrc> celie: fixed, and good night!
2023-10-09 20:20:04 <ikke> algitbot: retry master
2023-10-09 20:33:06 <PureTryOut> wtf armv7, that's not the deps you should be looking for...
2023-10-09 20:40:15 <ikke> they get pulled in through kthml
2023-10-09 20:40:18 <ikke> khtml-dev
2023-10-09 20:48:49 <ikke> PureTryOut: did you on purpose decrease the pkgrel of khtml again?
2023-10-09 20:48:56 <ikke> a4b27e96709955d9166954dec625ef4ec02b988f
2023-10-09 20:49:23 <ikke> I think khtml has not been rebuilt on armv7 with the new deps
2023-10-09 20:49:48 <PureTryOut> No? Did I do that?
2023-10-09 20:49:52 <ikke> yes
2023-10-09 20:50:24 <ikke> 1 -> 0
2023-10-09 20:51:47 <ikke> PureTryOut: should I bump it?
2023-10-09 20:52:09 <PureTryOut> Yes please
2023-10-09 20:52:43 <ikke> maybe to 2 even if 1 has already been built
2023-10-09 20:52:49 <ikke> (I saw build logs)
2023-10-10 05:48:23 <ikke> algitbot: retry master
2023-10-11 12:14:16 <andypost[m]> algitbot: retry master
2023-10-11 15:36:46 <ikke> algitbot: retry master
2023-10-11 16:46:09 <celie> Actually, i think the version in tea/configure is for sqlite-tcl, i noticed the skipped 3.43.1 in filelist diff while doing !53185 (already rebased it in response to the checksum change in main/sqlite)
2023-10-11 16:48:54 <celie> Should probably consider merging that instead of correcting the checksum again for sqlite-tcl (i'll be off for the night now, so if i need to do another rebase, that'll have to wait for tomorrow)
2023-10-11 17:03:06 <ikke> celie: It failed after updating the checksum because the builders use a cached version of the archives mirrored on distfiles.a.ol
2023-10-11 17:03:13 <ikke> distfiles.a.o
2023-10-11 17:03:24 <ikke> So they will still the original checksum
2023-10-11 17:08:02 <andypost[m]> +1 to merge !53185 as it fixes memleak https://www.sqlite.org/releaselog/3_43_2.html
2023-10-12 05:42:34 <ikke> algitbot: retry master
2023-10-12 06:01:27 <ikke> algitbot: retry 3.18-stable
2023-10-12 08:47:34 <celie> ^ Something is happening with networkmanager, i noticed it while working on !53260, and after trying a simple rebuild (without libmbim/libqmi/modemmanager), i think networkmanager now fails to build on 32-bit (it seems ninja gets a signal 11 when running vapigen)
2023-10-12 08:51:29 <celie> As networkmanager built fine on armhf and x86 last night, probably the change that is now causing it to fail was merged after that
2023-10-12 14:50:12 <nmeum> brace for build failures 😬
2023-10-12 14:51:00 <ikke> 😬
2023-10-12 14:53:43 <ikke> 
ACTION hides

2023-10-12 15:13:04 <ikke> segfault
2023-10-12 15:13:23 <ikke> panic: runtime error: invalid memory address or nil pointer dereference
2023-10-12 15:15:02 <ikke> algitbot: retry 3.18-stable
2023-10-12 15:21:12 <ikke> acme: error presenting token: could not start HTTPS server for challenge: listen tcp :23457: bind: address already in use
2023-10-12 15:23:31 <ptrc> the all seem like temporary failures for now
2023-10-12 15:23:41 <ptrc> s/the/they/
2023-10-12 15:23:56 <ikke> algitbot: retry 3.18-stable
2023-10-12 15:28:35 <nmeum> at some point it would probably be wortwhile to investigate if we can reduce the rebuild set somehow. for example, the CVE fixed in this version of Go should only affect HTTP/2 servers
2023-10-12 15:29:03 <ikke> nmeum: yeah, I have been wanting to make an inventory somewhere of what packages have what dependenceis
2023-10-12 15:29:06 <ikke> dependencies
2023-10-12 15:30:27 <nmeum> there is also https://gitlab.alpinelinux.org/Leo/atools/-/blob/master/print-go-deps.go which extract that information using debug/buildinfo
2023-10-12 15:30:59 <nmeum> I guess that info is removed by strip(1) though and we would have to include it in the apk during build time somehow?
2023-10-12 15:31:11 <ikke> yeah
2023-10-12 15:31:43 <nmeum> I think back in the day Ariadne also had some ideas on how to add such additional dependency information to .apk but not sure if she ever got around to working on that
2023-10-12 15:32:18 <nmeum> would most likely also be useful for rust to know which dependencies where vendored during the build of an .apk
2023-10-12 15:32:31 <Ariadne> working on it in melange :)
2023-10-12 15:32:40 <nmeum> for example if there is some security fix in a certain rust library
2023-10-12 15:33:09 <nmeum> Ariadne: oh cool, any chance it will be done in a way that is re-usable in apk-tools and Alpine? (:
2023-10-12 15:33:17 <ikke> nmeum: that does wait for apkv3 though
2023-10-12 15:33:24 <nmeum> ah
2023-10-12 15:33:31 <ikke> as we didn't want to increase the APKINDEXes too much
2023-10-12 15:33:44 <nmeum> right
2023-10-12 15:34:18 <ikke> for rust, I think aports using cargo-auditable helps
2023-10-12 15:34:29 <ikke> but no idea how / what
2023-10-12 15:35:19 <nmeum> ideally we would want something that integrates well with apk (instead of something that operates on the source/cargo files like cargo-auditable)
2023-10-12 15:36:18 <nmeum> so in an ideal world I would like to be able to construct an apk search query along the lines of "give me all packages which contain binaries that are statically linked against version XYZ of Go's net/http package"
2023-10-12 15:36:20 <ikke> for c-like binaries we can use readelf to extract this information
2023-10-12 15:36:48 <ikke> but there is no generic way to do it for other languages
2023-10-12 15:37:51 <nmeum> I mean for C we are just looking at shared libraries
2023-10-12 15:37:53 <Ariadne> the analysis engine is its own golang package
2023-10-12 15:38:22 <nmeum> is that public already?
2023-10-12 15:43:38 <Ariadne> partially.  check back in a few weeks and the refactoring should be complete.  we also have various binary package linters too that may be interesting
2023-10-12 15:47:14 <ikke> algitbot: retry 3.18-stable
2023-10-12 16:18:37 <ikke> algitbot: retry 3.18-stable
2023-10-12 16:18:39 <ikke> algitbot: retry master
2023-10-12 16:37:52 <ikke> ^ project seems to have disappeared
2023-10-12 16:47:14 <ikke> algitbot: retry 3.18-stable
2023-10-12 16:47:17 <ikke> algitbot: retry master
2023-10-12 17:26:16 <ikke> algitbot: retry master
2023-10-12 17:26:18 <ikke> algitbot: retry 3.18-stable
2023-10-12 18:05:45 <ikke> algitbot: retry master
2023-10-12 18:05:47 <ikke> algitbot: retry 3.18-stable
2023-10-12 18:27:28 <ikke> ^ upstream renamed to gitness
2023-10-12 18:51:32 <ikke> !53308
2023-10-12 18:51:46 <ikke> !53303
2023-10-12 18:57:41 <ikke> algitbot: retry master
2023-10-12 19:00:12 <ptrc> ikke: thanks!
2023-10-12 19:00:41 <ikke> np
2023-10-12 19:07:37 <ikke> ah, mpolanski disabled clipmanb
2023-10-12 19:14:29 <ikke> algitbot: retry master
2023-10-12 19:45:31 <ikke> algitbot: retry master
2023-10-12 20:14:50 <ikke> algitbot: retry master
2023-10-12 20:47:41 <ikke> algitbot: retry master
2023-10-12 20:48:09 <ikke> GitHub rate limit exceeded for https://api.github.com/repos/pulumi/pulumi-pkgA/releases/latest,
2023-10-12 20:48:11 <ikke> lesigh
2023-10-13 02:23:01 <celie> algitbot: retry master
2023-10-13 09:04:30 <ptrc> are the builders temporarily banned from github now
2023-10-13 10:05:21 <ikke> yes
2023-10-13 10:05:24 <ikke>                         
2023-10-13 10:05:39 <ikke> rate limited from the APAI
2023-10-13 10:05:41 <ikke> API
2023-10-13 10:05:45 <ikke> thanks to pulumi
2023-10-13 10:31:55 <ikke> nmeum: unexpected return pc for github.com/aws/aws-sdk-go-v2/service/sso/internal/endpoints.init called from 0x75a3792
2023-10-13 10:31:57 <ikke> ^
2023-10-13 10:58:25 <ikke> algitbot: retry 3.18-stable
2023-10-13 11:14:45 <minimal> popeye
2023-10-13 21:36:43 <ptrc> nmeum: have you seen that one?
2023-10-13 21:36:48 <ptrc> runtime: g 1: unexpected return pc for github.com/aws/aws-sdk-go-v2/service/sso/internal/endpoints.init called from 0x3
2023-10-13 21:36:54 <ptrc> that looks like.. some stack corruption?
2023-10-13 23:12:54 <andypost[m]> algitbot: retry master
2023-10-14 02:11:12 <celie> algitbot: retry master
2023-10-14 07:21:52 <PureTryOut> These merges are going to take a while to build 🙈
2023-10-14 07:23:28 <ikke> yup
2023-10-14 07:23:55 <ikke> poor riscv64, it's already backlogged
2023-10-14 07:24:08 <ikke> 48 / 343 (14%)
2023-10-14 07:27:43 <ikke> algitbot: retry master
2023-10-14 07:28:07 <PureTryOut> Yeah that's bound to happen with non-native builders
2023-10-14 07:51:37 <ikke> ppc64le seems to be hung as well
2023-10-14 08:12:31 <ikke> algitbot: retry master
2023-10-14 08:44:33 <ikke> algitbot: retry master
2023-10-14 09:56:30 <ikke> nmeum: should that backport fix helmfile on armhf?
2023-10-14 09:56:57 <ikke> seems to only mention aarch64
2023-10-14 09:57:14 <nmeum> no, helmfile is a different issue
2023-10-14 09:57:17 <ikke> ok
2023-10-14 09:57:24 <nmeum> this only fixes aports which use -buildmode=c-archive
2023-10-14 09:57:45 <nmeum> those that link Go code and C code together in a shared library
2023-10-14 09:57:58 <nmeum> which is not super common
2023-10-14 09:59:33 <nmeum> the helm thing definitly warrants further investigation too
2023-10-14 11:57:00 <ikke> nmeum: seems like something broke with go ^
2023-10-14 12:59:42 <nmeum> oh
2023-10-14 12:59:49 <nmeum> that doesn't happen on the CI
2023-10-14 13:00:19 <nmeum> algitbot: retry master
2023-10-14 13:07:58 <nmeum> I can't reproduce this locally
2023-10-14 13:08:14 <nmeum> lets hope its just racy?
2023-10-14 13:08:46 <nmeum> if it fails reliable on the inlinable test, then someone needs to test if it also fails with 0004-runtime-cgo-avoid-taking-the-address-of-crosscall2-i.patch removed from $source
2023-10-14 13:09:17 <ikke> it failed on 2 arches (both 32-bit)
2023-10-14 13:09:41 <nmeum> oh right it's only 32-bit
2023-10-14 13:09:47 <nmeum> let me check if I can repo it on x86
2023-10-14 13:13:21 <nmeum> it did pass ci on armhf and x86
2023-10-14 13:19:19 <ikke> I can check it passes without the patch on armhf
2023-10-14 13:21:43 <nmeum> yea, I think that would be good to know
2023-10-14 13:21:51 <nmeum> currently running it locally with CBUILD=armhf in abuild rootbld
2023-10-14 13:22:58 <ikke> failed without the patch
2023-10-14 13:24:02 <nmeum> yea that what I suspected
2023-10-14 13:25:31 <ikke> need me to test anything?
2023-10-14 13:26:03 <nmeum> https://gitlab.alpinelinux.org/alpine/aports/-/jobs/1136065/
2023-10-14 13:26:20 <nmeum> this was the last succesfull build on armhf
2023-10-14 13:26:26 <nmeum> so I guess since that a dependency was changed in some way?
2023-10-14 13:28:54 <nmeum> maybe 9fcc726a0d811a115e6f2b1feb881940c725f36c?
2023-10-14 13:29:03 <nmeum> though this probably only affects x86 not armhf?
2023-10-14 13:31:48 <ikke> and only in the testsuite?
2023-10-14 13:33:40 <nmeum> I mean this test checks for function inlining, if gcc code generation changed on 32-bit arches than this naturally might affect inlining
2023-10-14 13:34:05 <ikke> I mean, the gcc patch only changes things in the testsuite
2023-10-14 13:34:37 <nmeum> no it changes the .md files which affect code generation
2023-10-14 13:35:19 <nmeum> if it only changed things in the gcc testsuite, then it wouldn't fix the botan3 build :D
2023-10-14 13:35:43 <nmeum> from the lsat succesfull CI build I linked above:
2023-10-14 13:35:44 <nmeum> > v20230901-2604-g87ca28e3156 [https://dl-cdn.alpinelinux.org/alpine/edge/main]
2023-10-14 13:36:08 <nmeum> so I guess that means the CI succesfully go armhf CI build was with commit 87ca28e31561015e9df71250c1ce46e9e8021225
2023-10-14 13:36:15 <nmeum> and that commit is before the gcc change
2023-10-14 13:36:21 <nmeum> I don't see any musl changes since that commit
2023-10-14 13:36:41 <nmeum> and not sure what would affect the Go build other than musl, binutils, and gcc (in the case of cgo)
2023-10-14 13:36:46 <ikke> nmeum: oh lol, I thought md for markdown
2023-10-14 13:36:53 <nmeum> haha, no :D
2023-10-14 13:37:16 <nmeum> can you try reverting the gcc commit and check if it builds on x86 without the gcc commit and without the go patch
2023-10-14 13:37:21 <nmeum> that would be my best guess for now
2023-10-14 13:38:00 <ikke> need to make sure I clean up properly afterwards
2023-10-14 13:38:42 <nmeum> I don't see any other changes in `git log 87ca28e31561015e9df71250c1ce46e9e8021225..HEAD` which may be relevant to this build failure
2023-10-14 13:39:00 <nmeum> you are 100% sure that Go also doesn't build without the patch, right?
2023-10-14 13:39:31 <ikke> I ran abuild clean
2023-10-14 13:39:38 <ikke> I checked that 0004*.patch was not applied
2023-10-14 13:40:15 <ikke> nmeum: https://tpaste.us/BJzY 
2023-10-14 13:41:12 <nmeum> yea looks good
2023-10-14 13:41:20 <nmeum> and same test failure? the inlinable test?
2023-10-14 13:42:11 <nmeum> do we still have the gcc-r2 package for x86 cached somewhere? should be easy to check if it is a regression in gcc-r3 on x86 then
2023-10-14 13:43:01 <ikke> I don't think so, I'd have to rebuild
2023-10-14 13:45:22 <ikke> building gcc in x86 without that patch now
2023-10-14 13:45:24 <nmeum> ok
2023-10-14 13:45:45 <nmeum> on x86 or armhf?
2023-10-14 13:46:12 <nmeum> the armhf failure is still a mystery to me as the gcc patch should only affect x86 in theory
2023-10-14 13:46:20 <ikke> x86 as you asked
2023-10-14 13:46:41 <nmeum> but then again the gcc codebase is a mystery in itself so who knows
2023-10-14 13:46:54 <nmeum> yea testing on x86 makes more sense for now, thanks
2023-10-14 13:48:45 <nmeum> I am also open to alternative hypothesis which explain the test failure but the gcc change is definitly the first that comes to mind…
2023-10-14 13:49:58 <ikke> yes, it's a good candidate and relatively easy to test
2023-10-14 14:24:55 <ikke> (still compiling)
2023-10-14 14:40:44 <ikke> gcc finished building, building go now
2023-10-14 14:45:28 <ikke> nmeum: still fails
2023-10-14 14:45:49 <nmeum> oh wow
2023-10-14 14:46:04 <nmeum> so what's causing this then?
2023-10-14 14:46:05 <ikke> oh, the old gcc was still installed
2023-10-14 14:46:09 <ikke> retrying
2023-10-14 14:46:51 <ikke> forgot that it was part of alpine-sdk, so no installed by abuild deps
2023-10-14 14:47:16 <nmeum> ah ok
2023-10-14 14:51:31 <ikke> still failing 🤔
2023-10-14 14:51:38 <ikke> Installed:                                Available:
2023-10-14 14:51:40 <ikke> gcc-13.1.1_git20230722-r4               = 13.1.1_git20230722-r4
2023-10-14 14:52:08 <ikke> https://tpaste.us/NBXv 
2023-10-14 14:52:30 <ikke> now ppc64le as well, so not just 32-bits
2023-10-14 14:54:06 <nmeum> huh
2023-10-14 14:54:16 <nmeum> ok but what is it then
2023-10-14 14:54:53 <nmeum> can we somehow get a detailed version report for the last succesfull (CI) build and compare that with the current version of all installed packages?
2023-10-14 14:57:44 <ikke> not sure how
2023-10-14 14:58:02 <nmeum> !53411 checking to make sure that it also fails on the CI without the patch
2023-10-14 14:58:30 <nmeum> I mean we can also disable the inlining tests but it would be very good to know why it is suddently failing
2023-10-14 14:58:39 <ikke> yup
2023-10-14 15:06:52 <nmeum> on the CI it passes without the patch
2023-10-14 15:07:11 <nmeum> see !53411
2023-10-14 15:07:11 <ikke> and with the patch?
2023-10-14 15:08:33 <nmeum> testing that too now (pushed another commit to the MR)
2023-10-14 15:08:38 <nmeum> will be afk for a bit now
2023-10-14 15:08:41 <ikke> alright
2023-10-14 15:30:21 <andypost[m]> algitbot: retry master
2023-10-14 16:07:18 <nmeum> ikke: ok so the MR on the CI also passes with the patch and with the present musl, binutils, and gcc version !53411
2023-10-14 16:07:33 <nmeum> so I guess it's related to the builder configuration maybe?
2023-10-14 16:07:58 <ikke> hmm
2023-10-14 16:08:19 <nmeum> was there anything changed recently (as in: after the succesfull go-1.21.3-r0) build
2023-10-14 16:08:42 <ikke> Not something that would affect 3 different hosts
2023-10-14 16:09:03 <ikke> That would have to come from aports
2023-10-14 16:09:26 <nmeum> are there custom GOFLAGS/CFLAGS set?
2023-10-14 16:09:42 <nmeum> I mean basically we need to figure out if there is a difference between the CI build environment and the builders builder in environment in terms of configuration
2023-10-14 16:10:08 <nmeum> this is a function inlining test so it would be very weird if the builders would produce different Go code than the CI
2023-10-14 16:10:17 <ikke> especially now since that flags are defined in /usr/share/abuild/default.conf, that is less likely
2023-10-14 16:10:51 <ikke> I'm checking /etc/abuild.conf, but nothing significant is set there
2023-10-14 16:17:33 <ikke> `env` from the go APKBUILD: https://tpaste.us/xymW
2023-10-14 16:17:59 <ikke> seems to fail on all arches
2023-10-14 16:19:46 <nmeum> ok but then I just cannot reproduce it locally :D
2023-10-14 16:20:50 <nmeum> there is actually an additional test failure on x86_64: --- FAIL: TestLoopVarOpt (0.21s)
2023-10-14 16:20:55 <nmeum> what is happening
2023-10-14 16:22:47 <ikke> testing with rootbld now
2023-10-14 16:29:46 <nmeum> another thing to test may be: `abuild fetch unpack prepare deps build` and then cd into $srcdir/go/src/ and run ../bin/go build --gcflags=-m net/netip (that is what the failing inlining test does essentially)
2023-10-14 16:30:06 <nmeum> this is what the output looks like for me https://tpaste.us/yYEk
2023-10-14 16:30:20 <ikke> ok, waiting for rootbld to finish
2023-10-14 16:30:28 <nmeum> yea
2023-10-14 16:31:08 <ikke> rootbld passed 🤔
2023-10-14 16:31:34 <nmeum> as expected I guess? also passes locally in my rootbld
2023-10-14 16:31:55 <nmeum> so I guess the question than is: what is the difference between the rootbld build environment and the lxc build environment used by the builders?
2023-10-14 16:32:06 <nmeum> because that essentially rules out that is something that was changed in aports.git the last 2 days
2023-10-14 16:32:29 <ikke> maybe something in ~/go or ~/.cache/go-build?
2023-10-14 16:32:45 <nmeum> oh? is that not cleared?
2023-10-14 16:33:03 <nmeum> should definitly try remove those dirs and running the tests again then
2023-10-14 16:33:56 <nmeum> maybe backup them up instead of removing them entirely that we might be able to investigate this further if needed
2023-10-14 16:34:02 <nmeum> s/that we/then we/
2023-10-14 16:34:03 <ikke> yes, that's exactly what I did
2023-10-14 16:34:37 <ikke> for most go packages we set GOMODCACHE and GOTMPDIR
2023-10-14 16:37:46 <nmeum> I guess that could explain it if we merged/build an aport in the last two days that doesn't have those vars set
2023-10-14 16:41:04 <ikke> Wouldn't expect compiling go itself would be affected by that
2023-10-14 16:43:04 <nmeum> ikke: I mean that particular test just invokes the go command, so I think it should just pick up the usual environment variables
2023-10-14 16:43:43 <nmeum> https://github.com/golang/go/blob/master/src/net/netip/inlining_test.go#L19-L23
2023-10-14 16:43:45 <nmeum> this is the test case
2023-10-14 16:44:32 <ikke> "ALL TESTS PASSED"
2023-10-14 16:45:10 <ikke> so yes, stale GOMODCACHE / GOTMPDIR
2023-10-14 16:46:02 <nmeum> haha
2023-10-14 16:46:09 <nmeum> well at least we figured it out now :d
2023-10-14 16:46:11 <nmeum> *:D
2023-10-14 16:46:31 <ikke> Do we want to investigate, or just nuke these dirs on all builders?
2023-10-14 16:47:13 <nmeum> I mean technically it's probably some sort of cache invalidation bug in Go
2023-10-14 16:47:26 <ikke> Yeah, not the first time we ran into that
2023-10-14 16:47:53 <nmeum> *nod*
2023-10-14 16:49:15 <nmeum> I am not really familiar with the compiler cache code in Go and don't really put in the work to investigate it further to write a bug report
2023-10-14 16:49:25 <nmeum> so would be ok with me to just delete them
2023-10-14 16:49:30 <ikke> 👍
2023-10-14 16:56:40 <ikke> algitbot: retry master
2023-10-14 16:56:50 <ikke> purged it on all builders now
2023-10-14 16:57:39 <ikke> purged it on all builders now
2023-10-14 16:57:41 <ikke> algitbot: retry master
2023-10-14 17:04:22 <ikke> algitbot: retry master
2023-10-14 17:39:34 <ikke> algitbot: retry master
2023-10-14 19:44:06 <PureTryOut> algitbot: retry master
2023-10-14 19:57:00 <ikke> algitbot: retry master
2023-10-14 20:04:21 <ikke> PureTryOut: didn't seem to help :(
2023-10-14 20:05:25 <PureTryOut> Probably need https://invent.kde.org/utilities/ark/-/commit/8c0b53590a8876eaa19f76e6491cad4ca3c085a0 as well
2023-10-14 20:09:51 <ikke> algitbot: retry master
2023-10-14 20:11:00 <PureTryOut> ugh ok now I'm just getting all the patches
2023-10-14 20:11:16 <ikke> "Patch. All. The. Things"
2023-10-14 20:13:44 <PureTryOut> and every time it built successfully locally 🙈
2023-10-14 20:14:04 <ikke> interesting
2023-10-14 20:15:31 <PureTryOut> algitbot: retry master
2023-10-14 20:16:43 <PureTryOut> Ok I give up
2023-10-14 20:37:09 <andypost[m]> so only a "application/x-iso9660-appimage left
2023-10-14 20:47:57 <ikke> PureTryOut: ah, x86_64 passed because checks have been disabled there
2023-10-14 20:48:27 <PureTryOut> oh derp you're right lol
2023-10-14 20:48:58 <ikke> for exactly this issue
2023-10-14 20:49:02 <ikke> #14266
2023-10-14 20:59:58 <ikke> PureTryOut: okay if I skip the mimetype tests for now?
2023-10-14 21:00:11 <PureTryOut> I suppose yes
2023-10-14 21:05:49 <ikke> algitbot: retry master
2023-10-15 04:41:03 <andypost[m]> algitbot: retry master
2023-10-15 07:08:47 <ikke> algitbot: retry master
2023-10-15 09:10:49 <ikke> algitbot: retry master
2023-10-15 12:25:09 <ikke> algitbot: retry master
2023-10-15 16:01:58 <andypost[m]> algitbot: retry master
2023-10-15 16:02:37 <ikke> andypost[m]: thanks for fixing
2023-10-15 21:40:42 <andypost[m]> algitbot: retry 3.17-stable
2023-10-16 00:47:28 <andypost[m]> algitbot: kick master
2023-10-16 00:47:54 <andypost[m]> algitbot: kick build-edge-riscv64
2023-10-16 19:31:16 <ikke> algitbot: retry master
2023-10-17 11:49:42 <ikke> celie: perl-xml-bare seems to segfault during tests on armv7: t/Bug_node_named_value.t   (Wstat: 11 (Signal: SEGV) Tests: 1 Failed: 0)
2023-10-17 20:05:02 <ptrc> oops.
2023-10-17 20:05:57 <ptrc> ikke: do builders use the same distfiles?
2023-10-17 20:06:16 <ptrc> because the checksum changed for the source file upstream, but i didn't update it, as i assumed the builders would just use distfiles
2023-10-17 20:06:28 <ikke> they should
2023-10-17 20:06:32 <ptrc> welp
2023-10-17 20:06:37 <ptrc> arm doesn't seem to do so
2023-10-17 20:06:55 <ikke> Let me verify
2023-10-17 20:08:40 <ikke> algitbot: retry master
2023-10-17 20:09:47 <ikke> The new builders we created weren't setup to use distfiles
2023-10-17 20:31:55 <ptrc> ah
2023-10-18 10:44:08 <ikke> algitbot: retry master
2023-10-19 10:59:20 <ikke> algitbot: retry master
2023-10-19 16:00:01 <ptrc> ohno
2023-10-19 16:00:13 <ptrc> right, the distfiles from back then are probably deleted
2023-10-19 16:00:27 <ptrc> and the package itself is.. not used by anything and hasn't been touched by the maintainer since 2020
2023-10-20 10:13:24 <ncopa> algitbot: retry master
2023-10-20 11:19:55 <ncopa> algitbot: retry master
2023-10-20 12:23:59 <ncopa> algitbot: retry master
2023-10-20 13:03:52 <ncopa> algitbot: retry master
2023-10-20 13:05:42 <ncopa> algitbot: retry master
2023-10-20 16:00:33 <andypost[m]> algitbot: retry master
2023-10-20 19:35:31 <andypost[m]> algitbot: retry master
2023-10-20 20:27:21 <andypost[m]> algitbot: retry master
2023-10-20 20:34:15 <andypost[m]> algitbot: retry master
2023-10-20 21:13:35 <andypost[m]> algitbot: retry master
2023-10-21 01:01:06 <andypost[m]> algitbot: retry master
2023-10-21 01:02:50 <andypost[m]> algitbot: retry master
2023-10-21 01:49:38 <andypost[m]> algitbot: retry master
2023-10-21 01:50:39 <andypost[m]> algitbot: retry master
2023-10-21 01:51:21 <andypost[m]> algitbot: retry master
2023-10-21 01:53:26 <andypost[m]> algitbot: retry master
2023-10-21 03:32:26 <celie> algitbot: retry master
2023-10-21 06:25:22 <andypost[m]> algitbot: retry master
2023-10-21 06:40:45 <andypost[m]> algitbot: retry master
2023-10-21 07:58:22 <celie> algitbot: retry master
2023-10-21 08:26:41 <ncopa> algitbot: retry
2023-10-21 08:27:02 <ncopa> algitbot: retry master
2023-10-21 09:45:51 <ikke> algitbot: retry master
2023-10-21 09:46:52 <ikke> algitbot: retry 3.17-stable
2023-10-21 09:47:09 <ikke> algitbot: retry 3.16-stable
2023-10-21 12:27:37 <ikke> bootstrapping rust on aarch64
2023-10-21 18:16:40 <andypost[m]> algitbot: retry master
2023-10-21 19:12:18 <andypost[m]> algitbot: retry master
2023-10-21 19:48:01 <andypost[m]> algitbot: retry master
2023-10-21 19:50:22 <andypost[m]> algitbot: retry master
2023-10-21 21:55:19 <andypost[m]> algitbot: retry master
2023-10-21 22:08:22 <andypost[m]> algitbot: retry master
2023-10-21 23:56:59 <andypost[m]> algitbot: retry master
2023-10-21 23:58:31 <andypost[m]> algitbot: retry master
2023-10-22 00:42:35 <andypost[m]> algitbot: retry master
2023-10-22 00:47:05 <andypost[m]> algitbot: retry master
2023-10-22 00:54:44 <andypost[m]> algitbot: retry master
2023-10-22 01:05:34 <celie> andypost[m]: hi, would it be possible to add a 3.19 milestone tag to !51536 so it gets more attention? thanks
2023-10-22 01:07:10 <andypost[m]> celie: I find it ready - are you ok to merge it now?
2023-10-22 01:09:58 <andypost[m]> celie: I found no conflicts with fixing build
2023-10-22 01:10:55 <andypost[m]> algitbot: retry master
2023-10-22 01:19:16 <celie> andypost[m]: thanks, so now i'll keep an eye on https://build.alpinelinux.org (and this channel) to see if anything errors out
2023-10-22 01:19:44 <andypost[m]> thank you
2023-10-22 01:21:16 <celie> though i think the armhf builder is stuck on rakudo-star that was merged more than 12 hours ago
2023-10-22 01:21:50 <celie> algitbot: kick build-edge-armhf
2023-10-22 01:25:23 <andypost[m]> algitbot: kick build-3-19-s390x
2023-10-22 01:34:56 <celie> hmm, i wonder what's up with openldap on x86_64..
2023-10-22 01:35:05 <celie> algitbot: kick build-edge-x86_64
2023-10-22 01:43:20 <celie> algitbot: kick build-edge-x86_64
2023-10-22 01:52:51 <celie> algitbot: kick build-edge-armhf
2023-10-22 04:27:46 <celie> algitbot: retry master
2023-10-22 04:28:09 <celie> algitbot: kick build-edge-armhf
2023-10-22 06:57:07 <celie> algitbot: kick build-edge-armhf
2023-10-22 06:57:29 <celie> algitbot: kick build-3-19-s390x
2023-10-22 11:17:43 <ikke> algitbot: retry master
2023-10-22 13:26:19 <andypost[m]> algitbot: kick build-edge-armhf
2023-10-22 13:30:47 <ikke> algitbot: retry master
2023-10-22 13:40:39 <ikke> algitbot: retry master
2023-10-22 13:42:32 <celie> I wonder why those Python aports have started asking for typing-extensions now
2023-10-22 13:48:16 <celie> I tried grepping for typing extensions in py3-apipkg source, but couldn't find it, so perhaps it's one of its dependencies that's asking for it..
2023-10-22 13:50:08 <ikke> yeah, me too
2023-10-22 13:56:14 <celie> Exploring the typing-extensions thing in !53855
2023-10-22 13:58:39 <celie> I think it works, so when you've confirmed it, i'll remove the commit with the test rebuild of py3-apipkg (or you can remove it too)
2023-10-22 13:59:01 <ikke> remove what?]
2023-10-22 14:00:00 <ikke> I guess the test rebuild commit
2023-10-22 14:00:06 <celie> Yes
2023-10-22 14:00:20 <ikke> I can drop it
2023-10-22 14:01:21 <celie> Ok, the last aport that you added typing-extensions to (py3-pytest-mock) also depends on setuptools_scm, so i guess that's the problem
2023-10-22 14:01:49 <ikke> yeah
2023-10-22 14:02:41 <ikke> passes indeed without the dep now
2023-10-22 14:02:53 <celie> Great :)
2023-10-22 14:03:23 <ikke> celie: thanks, much better than arbitrarily adding that dep everywhere
2023-10-22 14:03:30 <celie> You're welcome
2023-10-22 14:07:29 <ikke> algitbot: retry master
2023-10-22 14:09:03 <celie> I think omni found out about the ion-shell getrandom crate open64 issue in !50904, but found some other problem with it
2023-10-22 14:12:00 <ikke> celie: syntax error, hmm
2023-10-22 14:16:27 <ikke> celie: maybe depends on rust nightly or so
2023-10-22 14:16:29 <ikke> ?
2023-10-22 14:21:39 <celie> I'm not sure, but i just tried the ion-shell that's currently in the repo, and i didn't get a syntax error
2023-10-22 14:42:41 <andypost[m]> algitbot: retry master
2023-10-22 14:57:05 <andypost[m]> algitbot: retry master
2023-10-22 15:26:52 <andypost[m]> algitbot: retry master
2023-10-22 15:27:48 <andypost[m]> algitbot: retry master
2023-10-22 15:34:42 <andypost[m]> ikke: ^^ go segfaults somehow on x86
2023-10-22 15:38:47 <celie> I think i encountered the py3-pyproject-api test failure while trying to upgrade it to 1.6.1
2023-10-22 15:53:39 <celie> Hmm, seems like lfs64 errors in tinyxml2
2023-10-22 15:54:31 <celie> Checksum failed
2023-10-22 16:00:44 <celie> Anyway, last MR before i head off for the night: !53860
2023-10-22 16:01:31 <celie> I think omni should handle the upgrade, especially because upstream doesn't seem to be tagging releases for the past few years
2023-10-22 16:02:53 <celie> My MR should fix the open64 errors and another 2 errors i encountered due to `cargo test` trying to download crates that `cargo fetch` did not download (probably due to --target)
2023-10-22 16:05:51 <celie> I tried the ion binary from build artifacts and i don't seem to get the syntax error omni mentioned in !50904
2023-10-22 16:08:50 <ikke> tinyxml2: https://github.com/leethomason/tinyxml2/pull/945
2023-10-22 16:18:40 <celie> It seems htmlq also needs a checksum update for the patch
2023-10-22 16:48:25 <nmeum> naaah this is easy to fix. no need to disable check
2023-10-22 16:49:08 <ikke> 👍
2023-10-22 16:49:33 <nmeum> it's just that the python binary patch in $builddir changed, may affect a few other python aports as well
2023-10-22 16:49:37 <nmeum> s/patch/path/
2023-10-22 16:50:57 <andypost[m]> nmeum: thank you
2023-10-22 16:51:11 <andypost[m]> algitbot: retry master
2023-10-22 16:51:18 <nmeum> no problem, I think we were working on it at the same time :D
2023-10-22 16:51:23 <nmeum> loooking and libsoup3 now
2023-10-22 16:51:26 <nmeum> s/and/at/
2023-10-22 16:57:59 <ikke> most arches reached community already
2023-10-22 16:58:16 <nmeum> \o/
2023-10-22 16:59:59 <ikke> algitbot: retry master
2023-10-22 17:33:16 <ikke> alpine-ipxe assembly issue
2023-10-22 17:33:18 <ikke> Error: operand size mismatch for `push'
2023-10-22 18:12:34 <ikke> algitbot: retry master
2023-10-22 18:13:31 <ikke> algitbot: retry master
2023-10-22 18:15:49 <ikke> algitbot: retry master
2023-10-22 18:17:17 <ikke> algitbot: retry master
2023-10-22 18:21:46 <andypost[m]> algitbot: retry master
2023-10-22 21:18:01 <ikke> algitbot: retry master
2023-10-23 01:50:40 <celie> algitbot: retry master
2023-10-23 02:27:17 <celie> algitbot: retry master
2023-10-23 05:33:34 <ikke> algitbot: retry master
2023-10-23 05:42:25 <celie> I just had a thought, could `make -j1 test` solve #15388 ?
2023-10-23 07:29:54 <celie> For py3-lz4: !53893
2023-10-23 07:50:00 <celie> For navi: !53897
2023-10-23 13:29:35 <ptrc> hm
2023-10-23 13:29:37 <ptrc> there's a dep missing
2023-10-23 13:29:41 <ptrc> but it's not for img2pdf
2023-10-23 13:29:47 <ptrc> and not sure for what really
2023-10-23 13:30:10 <ptrc> pikepdf 8.5.1 requires deprecation, which is not installed.
2023-10-23 13:30:11 <ptrc> ah
2023-10-23 13:41:02 <celie> For py3-snuggs: !53908 (patch is from Debian)
2023-10-23 14:37:36 <celie> For nlohmann-json: !53912
2023-10-23 15:39:39 <ikke> algitbot: retry master
2023-10-23 15:41:22 <nmeum> py3-pyzmq fails check() because we build zeromq without curve support since the 4.3.5 (since upstream changed the default in this regard)
2023-10-23 15:41:51 <ikke> aha
2023-10-23 15:41:57 <ikke> I already wondered what that was
2023-10-23 15:42:03 <nmeum> I guess we want to build zeromq with curve support
2023-10-23 15:42:09 <nmeum> otherwise the libsodium dependency is also useless
2023-10-23 15:42:22 <nmeum> compare https://build.alpinelinux.org/buildlogs/build-edge-x86_64/main/zeromq/zeromq-4.3.4-r5.log and https://build.alpinelinux.org/buildlogs/build-edge-x86_64/main/zeromq/zeromq-4.3.5-r0.log
2023-10-23 15:42:31 <nmeum> in the latter buildlog zeromq is no longer linked against libsodium
2023-10-23 15:42:39 <nmeum> > -- CURVE security is disabled
2023-10-23 15:44:45 <ikke> ctest [..] -E test_security_curve 
2023-10-23 15:44:52 <ikke> so the check was excluded
2023-10-23 15:45:33 <nmeum> yea but that has been present for a while
2023-10-23 15:45:37 <nmeum> even before the 4.3.5 release
2023-10-23 15:45:45 <ikke> ah ok
2023-10-23 15:45:50 <ikke> was just blaming that line
2023-10-23 15:51:53 <nmeum> !53925
2023-10-23 15:59:54 <nmeum> PureTryOut: ^ in case you haven't seen it yet: can you look at qt5-qtbase when you have the time? :)
2023-10-23 16:02:23 <PureTryOut> I was already asked by ikke, I will when I have the time
2023-10-23 16:06:56 <nmeum> PureTryOut: ah sorry. didn't see that
2023-10-23 16:32:00 <nmeum> uff looks like gcc-go broke
2023-10-23 16:37:48 <nmeum> hm, still works locally on x86_64. I guess that's a regression in gcc 13.2.1 on x86, let's see if it fails on other arches too
2023-10-23 17:12:24 <andypost[m]> algitbot: retry master
2023-10-23 18:05:07 <ikke> XKB_KEY_dead_lowline and others were removed from libxkbcommon
2023-10-23 18:07:54 <ikke> https://github.com/qt/qtbase/commit/8af35d27e8f02bbb99aef4ac495ed406e50e3cca
2023-10-23 18:11:26 <andypost[m]> ikke: are you going to create MR for both qt6 and 5?
2023-10-23 18:11:30 <ikke> yes
2023-10-23 18:12:29 <andypost[m]> btw go build passed on x86_64
2023-10-23 18:20:22 <ikke> !53933
2023-10-23 18:21:34 <ikke> algitbot: retry master
2023-10-23 18:23:19 <andypost[m]> algitbot: retry master
2023-10-23 18:28:26 <ikke> algitbot: retry master
2023-10-23 20:27:19 <andypost> algitbot: retry master
2023-10-23 20:27:34 <andypost> algitbot: retry 3.18-stable
2023-10-23 20:29:21 <andypost>  algitbot: retry master
2023-10-23 20:42:59 <andypost> algitbot: retry 3.18-stable
2023-10-23 20:47:34 <andypost> gonna merge !53937
2023-10-23 21:02:02 <andypost> algitbot: retry master
2023-10-23 21:21:35 <andypost> algitbot: retry 3.18-stable
2023-10-23 21:57:31 <andypost> algitbot: retry master
2023-10-23 22:34:31 <andypost> algitbot: retry master
2023-10-23 22:39:59 <andypost> algitbot: retry 3.18-stable
2023-10-23 22:41:09 <andypost> algitbot: retry master
2023-10-23 22:51:38 <andypost> nmeum, filed #15390
2023-10-23 23:00:53 <andypost> algitbot: retry master
2023-10-23 23:01:23 <andypost> algitbot: retry master
2023-10-23 23:07:51 <andypost> algitbot: retry master
2023-10-23 23:12:47 <andypost> algitbot: retry master
2023-10-23 23:15:17 <andypost> algitbot: retry master
2023-10-23 23:15:50 <andypost> algitbot: retry master
2023-10-23 23:16:56 <andypost> algitbot: retry master
2023-10-24 00:35:57 <andypost> algitbot: retry master
2023-10-24 00:38:13 <andypost[m]> algitbot: retry master
2023-10-24 00:39:34 <andypost[m]> algitbot: retry master
2023-10-24 00:41:14 <andypost[m]> algitbot: retry master
2023-10-24 00:41:42 <andypost[m]> algitbot: kick build-3-19-x86
2023-10-24 00:59:01 <andypost[m]> algitbot: kick build-3-19-aarch64
2023-10-24 00:59:11 <andypost[m]> algitbot: kick build-3-19-ppc64le
2023-10-24 00:59:39 <andypost[m]> algitbot: kick build-3-19-armhf
2023-10-24 00:59:52 <andypost[m]> algitbot: retry master
2023-10-24 01:04:12 <andypost[m]> algitbot: retry master
2023-10-24 01:12:53 <andypost[m]> algitbot: retry master
2023-10-24 01:13:31 <andypost[m]> algitbot: kick build-edge-x86
2023-10-24 01:15:03 <celie> I wonder if 'kick' still works..
2023-10-24 01:30:13 <andypost[m]> algitbot: retry master
2023-10-24 01:30:35 <andypost[m]> celie: as I see only for edge x86_64
2023-10-24 01:33:32 <celie> https://build.alpinelinux.org/buildlogs/build-3-19-s390x/community/timed/timed-3.6.14-r0.log - setcap binary found, i wonder if it's new
2023-10-24 01:38:05 <andypost[m]> algitbot: retry 3.18-stable
2023-10-24 01:38:36 <andypost[m]> algitbot: kick build-3-19-ppc64le
2023-10-24 01:38:48 <andypost[m]> algitbot: retry master
2023-10-24 02:00:02 <andypost[m]> algitbot: retry master
2023-10-24 02:05:54 <andypost[m]> algitbot: retry master
2023-10-24 02:12:55 <andypost[m]> algitbot: retry master
2023-10-24 02:24:47 <andypost[m]> algitbot: retry master
2023-10-24 02:33:15 <andypost[m]> algitbot: retry master
2023-10-24 02:37:49 <andypost[m]> algitbot: retry master
2023-10-24 02:48:43 <celie> There seems to be a lot of "failed to mkdir" errors (for example, libhandy1 and gtksourceview4)
2023-10-24 02:50:32 <celie> Hmm, and both of them are trying to mkdir ~/.config/ibus/bus (while running tests)
2023-10-24 02:53:05 <celie> https://build.alpinelinux.org/buildlogs/build-3-19-aarch64/community/uhttpmock/uhttpmock-0.9.0-r0.log is trying to mkdir ~/.config/glib-2.0/settings in tests
2023-10-24 02:59:11 <celie> https://build.alpinelinux.org/buildlogs/build-3-19-x86_64/community/gops/gops-0.3.28-r2.log is trying to mkdir ~/.config/gops
2023-10-24 03:00:46 <celie> Anyway, i opened !53941 to !53944 to fix the build issues i could help out with
2023-10-24 05:23:27 <ikke> celie: I've fixed the .config dir permissions
2023-10-24 05:23:51 <ikke> andypost[m]: celie kick only works for riscv64
2023-10-24 05:42:36 <celie> Ok
2023-10-24 05:50:54 <celie> Anyway, a few more MRs to fix issues found by the 3.19 builders: !53943 !53942 !53897
2023-10-24 06:47:27 <celie> For mutter: !53961
2023-10-24 07:09:57 <celie> OCaml is failing on s390x due to "No file descriptors available" and "diff: unrecognized option: strip-trailing-cr"
2023-10-24 07:10:26 <celie> I don't remember that happening on the CI though
2023-10-24 07:12:28 <celie> It seems it didn't happen on edge too, and OCaml was rebuilt there last month
2023-10-24 07:17:10 <celie> and OCaml built successfully on build-3-19-ppc64le, so perhaps a retry will fix it
2023-10-24 07:17:16 <celie> algitbot: retry master
2023-10-24 08:16:31 <andypost[m]> algitbot: retry master
2023-10-24 11:01:01 <andypost[m]> algitbot: retry master
2023-10-24 11:09:05 <ikke> Lookup AS6939 failed, got AS6939 
2023-10-24 11:09:07 <ikke> 🤔
2023-10-24 12:34:33 <celie> For gitstatus: !53968
2023-10-24 13:46:18 <celie> For py3-validate-pyproject: !53970
2023-10-24 13:46:35 <celie> For gnome-feeds: !53973
2023-10-24 13:46:52 <celie> For libselinux: !53974
2023-10-24 15:02:44 <andypost[m]> spdlog !53983
2023-10-24 15:05:59 <celie> Alright, last fix of the day from me for errors found by the 3.19 builders: !53980
2023-10-24 15:34:27 <andypost[m]> algitbot: retry master
2023-10-24 15:37:27 <andypost[m]> algitbot: retry master
2023-10-24 16:26:45 <andypost[m]> algitbot: retry master
2023-10-25 00:09:29 <andypost[m]> algitbot: retry master
2023-10-25 00:18:13 <andypost[m]> algitbot: retry master
2023-10-25 00:18:58 <andypost[m]> algitbot: retry master
2023-10-25 00:31:23 <andypost[m]> algitbot: retry master
2023-10-25 00:36:51 <andypost[m]> algitbot: retry master
2023-10-25 01:11:28 <andypost[m]> algitbot: retry master
2023-10-25 01:36:38 <andypost[m]> algitbot: retry master
2023-10-25 01:38:56 <andypost[m]> algitbot: retry master
2023-10-25 04:04:58 <andypost[m]> algitbot: retry master
2023-10-25 05:20:16 <andypost[m]> algitbot: retry master
2023-10-25 05:28:25 <celie> !54035 upstream changed repository name, but i think i'll let @mpolanski do the actual package transition
2023-10-25 05:39:01 <ikke> openjdk* misses a makedepends on java-common. The actual dependency is on a subpackage, which is hidden for the build order solver
2023-10-25 05:53:18 <celie> Other merge requests that fix issues found by the 3.19 builders: !54029 !54033 !54030 !54037
2023-10-25 08:08:04 <celie> More fixes: !54039 !54041 !54042 !54043 !54045
2023-10-25 14:41:24 <andypost[m]> algitbot: retry master
2023-10-25 14:49:12 <andypost[m]> algitbot: retry master
2023-10-25 14:49:35 <andypost[m]> algitbot: retry master
2023-10-25 14:53:00 <andypost[m]> algitbot: retry master
2023-10-25 15:20:11 <andypost[m]> algitbot: retry master
2023-10-25 15:20:57 <ikke> fyi, as long as builders are busy, I will not bootstrap a openjdk8
2023-10-25 15:26:41 <andypost[m]> ikke: looks like it stops every 15 minutes)
2023-10-25 15:27:08 <andypost[m]> also ghc needs bootstrap
2023-10-25 15:34:06 <ikke> 👍
2023-10-25 15:42:09 <celie> Fixes for errors from the 3.19 builders: !54075 !54076 !54077 !54080 !54081 !54082 !54083
2023-10-25 16:29:27 <andypost[m]> ncopa: ^^ source gone
2023-10-25 16:37:08 <celie> 2 fixes from earlier today: !54039 !54041
2023-10-25 16:39:05 <celie> andypost[m]: Thanks :)
2023-10-25 18:42:15 <andypost[m]> algitbot: retry master
2023-10-25 19:50:33 <ikke> bootstrapping openjdk8 on armv7
2023-10-25 20:05:40 <ikke> re py3-qt6: https://www.riverbankcomputing.com/pipermail/pyqt/2023-October/045553.html
2023-10-25 20:06:15 <ikke> They say qt6 removed things unanounced
2023-10-25 20:06:23 <ikke> or without deprecation
2023-10-25 20:14:19 <ikke> bootstrapping openjdk8 on x86
2023-10-25 20:15:02 <andypost[m]> 🫰
2023-10-25 20:23:17 <ikke> tried to upgrade py3-qt6 but it still fails to build
2023-10-25 20:26:01 <andypost[m]> ikke: why it passed in edge?
2023-10-25 20:26:43 <ikke> andypost[m]: qt6 was upgraded
2023-10-25 20:26:50 <ikke> this package was not rebuilt since then 
2023-10-25 20:27:24 <andypost[m]> ah, csos many aports depend on it
2023-10-25 20:27:57 <ikke> and maybe no soname bump, so only build time dependencies
2023-10-25 20:34:52 <ikke> openjdk8 is hanging on armv7 😫
2023-10-25 20:46:39 <ikke> bootstrapping openjdk8 on ppc64le
2023-10-25 21:45:46 <andypost[m]> ikke: looks openjdk8 repeatedly fails on s290x
2023-10-25 21:45:54 <andypost[m]> s/290/390
2023-10-25 22:22:26 <andypost[m]> algitbot: retry master
2023-10-26 00:20:24 <andypost[m]> algitbot: retry master
2023-10-26 07:02:32 <celie> Fixes for issues found during the 3.18 rebuild: !54120 !54130 !54132 !54134
2023-10-26 07:02:44 <celie> s/3.18/3.19/
2023-10-26 07:03:15 <celie> Opps, sorry, !54129 not 54120
2023-10-26 11:05:52 <ikke> algitbot: retry master
2023-10-26 11:48:48 <ikke> huh, gcompat...
2023-10-26 12:30:20 <ikke> algitbot: retry master
2023-10-26 13:18:52 <ikke> bootstrapping openjdk8 on s390x
2023-10-26 13:19:35 <ikke> oh it's a different failure
2023-10-26 13:32:37 <ikke> algitbot: retry master
2023-10-26 15:59:38 <pluewn> 5     ,        ,
2023-10-26 15:59:39 <pluewn> 5    /(_,    ,_)\
2023-10-26 15:59:40 <pluewn> 5    \ _/    \_ /  irc.ircnow.org
2023-10-26 15:59:41 <pluewn> 5    //        \\
2023-10-26 15:59:42 <pluewn> 5    \\ 15(7@15)(7@15)5 //      #ircnow
2023-10-26 15:59:43 <pluewn> 5     \'=\"==\"='/
2023-10-26 15:59:44 <pluewn> 5 ,===/        \===,
2023-10-26 15:59:45 <pluewn> 5\",===\        /===,\"
2023-10-26 15:59:46 <pluewn> 5\" ,==='------'===, \"
2023-10-26 15:59:47 <pluewn> 5 \"                \"
2023-10-26 18:50:05 <andypost[m]> algitbot: retry master
2023-10-26 18:55:46 <andypost[m]> algitbot: retry master
2023-10-26 19:06:38 <andypost[m]> algitbot: retry master
2023-10-26 20:57:36 <andypost[m]> algitbot: retry master
2023-10-26 21:27:24 <andypost[m]> algitbot: retry master
2023-10-26 22:21:23 <andypost[m]> algitbot: retry master
2023-10-26 22:24:03 <andypost[m]> algitbot: retry master
2023-10-26 22:47:32 <andypost[m]> algitbot: retry master
2023-10-26 23:52:51 <andypost[m]> algitbot: retry master
2023-10-27 00:16:20 <andypost[m]> algitbot: retry master
2023-10-27 00:24:12 <andypost[m]> algitbot: retry master
2023-10-27 00:28:40 <andypost[m]> algitbot: retry master
2023-10-27 00:33:59 <andypost[m]> algitbot: retry master
2023-10-27 00:42:08 <andypost[m]> algitbot: retry master
2023-10-27 00:47:56 <andypost[m]> algitbot: retry master
2023-10-27 01:16:13 <andypost[m]> algitbot: retry master
2023-10-27 01:16:54 <andypost[m]> algitbot: retry master
2023-10-27 01:17:39 <andypost[m]> algitbot: retry master
2023-10-27 01:24:08 <andypost[m]> algitbot: retry master
2023-10-27 01:42:12 <andypost[m]> algitbot: retry master
2023-10-27 01:50:04 <andypost[m]> algitbot: retry master
2023-10-27 01:51:09 <andypost[m]> algitbot: retry master
2023-10-27 01:53:33 <andypost[m]> algitbot: retry master
2023-10-27 01:57:07 <andypost[m]> algitbot: retry master
2023-10-27 02:04:29 <andypost[m]> algitbot: retry master
2023-10-27 02:04:56 <andypost[m]> algitbot: retry master
2023-10-27 02:39:46 <andypost[m]> algitbot: retry master
2023-10-27 02:43:37 <andypost[m]> algitbot: retry master
2023-10-27 03:03:31 <andypost[m]> algitbot: retry master
2023-10-27 03:06:52 <andypost[m]> algitbot: retry master
2023-10-27 03:27:58 <andypost[m]> algitbot: retry master
2023-10-27 03:51:11 <andypost[m]> algitbot: retry master
2023-10-27 04:03:34 <andypost[m]> algitbot: retry master
2023-10-27 04:10:04 <andypost[m]> algitbot: retry master
2023-10-27 08:17:05 <celie> Fixes for the 3.19 build issues: !54208 !54209 !54213 !54215 !54216 !54217
2023-10-27 15:08:34 <andypost[m]> algitbot: retry master
2023-10-27 15:10:02 <andypost[m]> algitbot: retry master
2023-10-27 15:14:55 <andypost[m]> algitbot: retry master
2023-10-27 15:51:51 <andypost[m]> algitbot: retry master
2023-10-27 16:45:19 <andypost[m]> algitbot: retry master
2023-10-27 16:55:49 <andypost[m]> algitbot: retry master
2023-10-27 16:58:16 <andypost[m]> algitbot: retry master
2023-10-27 17:02:46 <ikke> going to bootstrap ghc
2023-10-27 17:02:48 <ikke> hold on
2023-10-27 17:04:05 <ikke> algitbot: retry master
2023-10-27 18:36:31 <ikke> algitbot: retry master
2023-10-27 19:03:54 <ikke> algitbot: retry master
2023-10-27 19:16:39 <andypost[m]> algitbot: retry master
2023-10-27 19:17:24 <andypost[m]> algitbot: retry master
2023-10-27 21:10:37 <ptrc> ikke: do the builders retain builddir for failed packages?
2023-10-27 21:10:55 <ikke> ptrc: abuild does a clean before building a package
2023-10-27 21:11:05 <ikke> so after, it stays, but on rebuild it's cleaned
2023-10-27 21:11:11 <ptrc> kinda curious what happened to duplicity; `NotADirectoryError: [Errno 20] Not a directory: 'foo/bar'`
2023-10-27 21:11:33 <ptrc> as in, would that be a file called 'foo' or perhaps cwd being broken in some way
2023-10-27 21:11:46 <ikke> let me check
2023-10-27 21:14:55 <ikke> wondering what PWD is
2023-10-27 21:14:57 <ikke> $builddir?
2023-10-27 21:15:26 <ikke> builds in a .venv
2023-10-27 21:15:40 <ikke> or rather, tests
2023-10-27 21:17:09 <ptrc> tests should still be ran with PWD being builddir, i think?
2023-10-27 21:17:17 <ptrc> s/^/in that case, /
2023-10-27 21:17:42 <ikke> nothing called foo or bar
2023-10-27 21:18:50 <ptrc> hm, i'll try if it reproduces locally
2023-10-27 21:19:57 <ptrc> it doesn't
2023-10-27 21:20:55 <ikke> NotADirectoryError implies either foo or bar is a file, right?
2023-10-27 21:21:01 <ikke> or something else at least
2023-10-27 21:21:03 <ptrc> i think so?
2023-10-27 21:21:20 <ptrc> python docs are not being very specific as to what could cause that 
2023-10-27 23:26:11 <andypost[m]> algitbot: retry master
2023-10-28 00:54:00 <andypost[m]> algitbot: retry master
2023-10-28 10:29:35 <HRio> algitbot: retry master
2023-10-28 10:31:48 <HRio> py3-nats errors looks like timeouts
2023-10-28 10:32:01 <HRio> (in the test suite)
2023-10-28 12:55:49 <celie> taskd's old url now returns 404, according to https://taskwarrior.org/download/ the files are now hosted on Github: !54307 (no checksum change)
2023-10-28 15:17:10 <andypost[m]> algitbot: retry master
2023-10-28 16:25:41 <andypost[m]> algitbot: retry master
2023-10-28 16:55:29 <andypost[m]> algitbot: retry master
2023-10-28 17:25:15 <ikke> algitbot: retry master
2023-10-28 20:54:09 <andypost[m]> algitbot: retry master
2023-10-28 21:00:25 <andypost[m]> algitbot: retry master
2023-10-29 01:03:30 <celie> ansible-lint's checksum changed: !54327
2023-10-29 02:19:10 <andypost[m]> algitbot: retry master
2023-10-29 02:20:12 <andypost[m]> algitbot: retry master
2023-10-29 03:03:09 <andypost[m]> algitbot: retry master
2023-10-29 03:07:31 <andypost[m]> algitbot: retry master
2023-10-29 03:10:24 <andypost[m]> algitbot: retry master
2023-10-29 03:20:47 <andypost[m]> algitbot: retry master
2023-10-29 03:40:55 <andypost[m]> algitbot: retry master
2023-10-29 06:04:56 <ptrc> ..oops
2023-10-29 06:07:02 <ptrc> is there even a way to disable a subpackage on other architectures than the main package?
2023-10-29 12:19:07 <andypost[m]> algitbot: retry master
2023-10-29 12:19:55 <andypost[m]> algitbot: retry master
2023-10-29 12:22:11 <andypost[m]> algitbot: retry master
2023-10-29 12:31:40 <andypost[m]> algitbot: retry master
2023-10-29 13:03:16 <andypost[m]> algitbot: retry master
2023-10-29 13:29:50 <andypost[m]> algitbot: retry master
2023-10-29 13:30:31 <andypost[m]> algitbot: retry master
2023-10-29 14:01:06 <celie> This should allow oq to pass checks on 3.19: !54352
2023-10-30 01:07:10 <andypost[m]> algitbot: retry master
2023-10-30 01:32:19 <andypost[m]> algitbot: retry master
2023-10-30 02:19:29 <celie> Fixes for errors found by the 3.19 rebuilders: !54378 !54380 !54381
2023-10-30 05:16:51 <celie> More fixes: !54385, and possibly !54383
2023-10-30 06:30:25 <celie> There's also !54378 from earlier on, which as rustup is not enabled for s390x, probably doesn't need to wait for the s390x runner
2023-10-30 06:33:01 <ikke> checkapk mentions 3 packages needing to be rebuild for lldp, but I cannot find actual packages depending on the actual libraries
2023-10-30 06:36:00 <ikke> seems to be dependencies directly on lldp, not on the libraries
2023-10-30 06:37:07 <ikke> lldb*
2023-10-30 06:56:44 <celie> I kind of brought up the possibility of that happening (non-library dependencies being caught) in https://gitlab.alpinelinux.org/alpine/abuild/-/merge_requests/223#note_339534 though i probably didn't choose a very good example, as the Python aports will have to be rebuilt for major version upgrades, but due to the site-packages directory change, not due to linking to Python libraries
2023-10-30 07:20:33 <celie> Perhaps checkapk should also list the packages it thinks needs rebuilding, maybe if there are too many, it could output them to a file that's added to the CI build artifacts
2023-10-31 00:16:55 <andypost[m]>  algitbot: retry master
2023-10-31 00:38:39 <andypost[m]> algitbot: retry master
2023-10-31 01:34:37 <andypost[m]> algitbot: retry master
2023-10-31 02:17:34 <andypost[m]> algitbot: retry master
2023-10-31 03:20:57 <andypost[m]> algitbot: retry master
2023-10-31 03:43:34 <andypost[m]> algitbot: retry master
2023-10-31 03:44:35 <andypost[m]> algitbot: retry master
2023-10-31 03:47:10 <andypost[m]> algitbot: retry master
2023-10-31 03:51:00 <andypost[m]> algitbot: retry master
2023-10-31 03:54:17 <andypost[m]> algitbot: retry master
2023-10-31 04:24:59 <andypost[m]> algitbot: retry master
2023-10-31 04:26:40 <andypost[m]> algitbot: retry master
2023-10-31 04:27:09 <andypost[m]> algitbot: retry master
2023-10-31 04:30:18 <andypost[m]> algitbot: retry master
2023-10-31 04:51:16 <andypost[m]> algitbot: retry master
2023-10-31 04:54:01 <andypost[m]> algitbot: retry master
2023-10-31 05:02:11 <andypost[m]> algitbot: retry master
2023-10-31 05:16:18 <andypost[m]> algitbot: retry master
2023-10-31 05:20:08 <andypost[m]> algitbot: retry master
2023-10-31 05:54:19 <andypost[m]> algitbot: retry master
2023-10-31 06:01:00 <andypost[m]> algitbot: retry master
2023-10-31 06:17:51 <andypost[m]> algitbot: retry master
2023-10-31 06:22:39 <ikke> algitbot: retry master
2023-10-31 06:37:40 <celie> Umm, ikke, i don't think the pipeline passed for !54269: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/54269/pipelines
2023-10-31 06:38:48 <ikke> hmf
2023-10-31 06:40:54 <celie> Hmm, game-devices-udev fails checksum, hopefully nothing else fails after that's fixed
2023-10-31 06:41:30 <ikke> checking
2023-10-31 06:42:16 <ikke> passes after that
2023-10-31 06:42:18 <celie> Seems like it's just copying udev rules, so should be alright
2023-10-31 06:43:55 <ikke> seems like the archive changed in some way, but no file differences
2023-10-31 06:44:10 <ikke> Format-specific differences are supported for Gzipped files but no file-specific differences were detected; falling back to a binary diff.
2023-10-31 06:52:01 <celie> freedoom seems to build fine after this applying patch: https://github.com/freedoom/freedoom/commit/d64ddc6ea
2023-10-31 06:54:10 <celie> However, i still see quite a number of errors, but they don't cause the build to fail
2023-10-31 06:54:23 <ikke> could not find file
2023-10-31 06:54:46 <celie> Because it couldn't run asciidoctor-pdf
2023-10-31 06:54:54 <celie> to generate the PDF manual
2023-10-31 06:55:21 <celie> Do we even have an aport providing that command..
2023-10-31 06:56:08 <ikke> nope https://pkgs.alpinelinux.org/contents?file=asciidoctor-pdf&path=&name=&branch=edge
2023-10-31 06:56:13 <ikke> I have to go now, thanks celie!
2023-10-31 06:56:21 <celie> You're welcome
2023-10-31 06:56:25 <celie> Bye
2023-10-31 07:03:20 <celie> Hmm, the PDF manual thing was the last error, but before that there are lots of other could not find file errors, probably some game-related files, the Git repo includes PNG but not other formats it seems
2023-10-31 07:04:01 <celie> So, Saijin_Naib[m], you'll probably want to take a look at freedoom to see if those errors affect its operation in any way
2023-10-31 07:08:17 <celie> librist fails a test on s390x (but it was fine on the CI, let's see if a retry will allow it to pass)
2023-10-31 07:08:24 <celie> algitbot: retry master
2023-10-31 07:19:41 <celie> algitbot: retry master
2023-10-31 07:20:31 <celie> Hmm, probably needs a rename on distfiles or in the APKBUILD
2023-10-31 10:58:09 <andypost[m]> algitbot: retry master
2023-10-31 11:11:02 <andypost[m]> algitbot: retry master
2023-10-31 11:15:12 <ikke> algitbot: retry master
2023-10-31 14:58:50 <andypost[m]> algitbot: retry master
2023-10-31 15:35:06 <andypost[m]> imagemagick has no jpg support, that's why some tests like community/py3-pywal fails
2023-10-31 15:46:52 <andypost[m]> ikke: any idea why checkdepends is not installed on build-edge-riscv64 builder? that's it fails on scudo-malloc
2023-10-31 16:08:39 <ikke> andypost[m]: because ABUILD_BOOTSTRAP is defined, disabling checks
2023-10-31 16:09:23 <ikke> andypost[m]: so something like want_check || TESTS=off should be added
2023-10-31 16:11:35 <ikke> hmm, a custom Makefile has been added
2023-10-31 16:14:57 <ikke> My makefu is not good enough to propose a solution
2023-10-31 17:07:42 <ikke> andypost[m]: ^
2023-10-31 17:08:36 <andypost[m]> ikke: nice!))