2023-09-01 10:13:27 algitbot: retry master 2023-09-01 13:21:44 algitbot: retry master 2023-09-02 14:31:28 algitbot: retry master 2023-09-04 01:01:50 algitbot: retry master 2023-09-06 16:41:49 looks like go-quic still doesn't support go 1.21 yet 2023-09-06 17:57:27 oh my 2023-09-06 17:58:10 and it's all just go-quic 2023-09-06 18:45:26 algitbot: retry master 2023-09-06 18:58:14 hugo is a test failure 2023-09-06 19:22:11 algitbot: retry master 2023-09-06 19:27:52 ikke: as I got mostly all failures are caused by > The version of quic-go you're using can't be built on Go 1.21 yet 2023-09-06 19:28:43 yes 2023-09-06 19:28:44 most of them 2023-09-06 19:28:48 hugo is an exception 2023-09-06 19:28:56 just wanted to point that out 2023-09-06 19:51:37 algitbot: retry master 2023-09-06 20:18:12 urrgss 2023-09-06 20:18:55 working on traefik, there is a patch 2023-09-06 20:19:16 kubo is more problematic 2023-09-06 20:20:51 v2ray is also go-quic 2023-09-06 20:22:00 gomplate just needs an update of unsafe-assume-no-moving-gc 2023-09-06 20:22:27 ah, that one is anoying 2023-09-06 20:22:33 I mean, that you constantly have to update it 2023-09-06 20:39:35 ikke: kubo would have to get upgraded to a git commit 2023-09-06 20:40:06 right, I was reading the different issues, but it didn't seem convincing everythign was solved yet 2023-09-06 22:54:00 hugo upgrade working with new go https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/50802 2023-09-07 00:37:58 algitbot: retry master 2023-09-07 00:54:59 algitbot: retry master 2023-09-07 02:09:47 algitbot: retry master 2023-09-07 02:33:22 algitbot: retry master 2023-09-07 02:36:32 algitbot: retry master 2023-09-07 02:40:02 algitbot: retry master 2023-09-07 02:43:52 algitbot: retry master 2023-09-07 02:49:50 algitbot: retry master 2023-09-07 03:06:27 algitbot: retry master 2023-09-07 03:09:21 algitbot: retry master 2023-09-07 03:17:39 algitbot: retry master 2023-09-07 06:44:52 I think for terraform and v2ray it should be possible just to update the go-quic version 2023-09-07 19:45:33 that rebuild should hopefully be more smooth 2023-09-07 19:47:27 terraform on edge has some anoying test failure 2023-09-07 19:47:32 remote error: tls: certif 2023-09-07 19:47:34 icate required 2023-09-09 09:47:53 looking at grpcurl 2023-09-09 09:55:33 cloudflared uses a custom version of go-quic 😒 2023-09-09 10:04:22 algitbot: retry master 2023-09-09 10:14:17 looking at clue-cli 2023-09-09 10:14:20 *cue-cli 2023-09-09 10:34:24 algitbot: retry master 2023-09-09 13:09:19 algitbot: retry master 2023-09-09 23:26:45 > OSError: [Errno 12] Out of memory 2023-09-09 23:26:50 it tries to run.. one test...? 2023-09-10 16:13:38 algitbot: retry master 2023-09-10 20:01:44 uhhhhhhhhhh 2023-09-10 20:01:51 https://ptrc.gay/xqmrHXKC 2023-09-10 20:01:55 what 2023-09-10 20:02:53 clandmeter: ikke: any idea why it might just "fail"? tried listening to the mqtt feed but it doesn't say much 2023-09-10 20:04:18 checking 2023-09-10 20:04:26 looks like it's stuck on e96a162a9ba15e78145a7e802c7a9c3febef21d1 2023-09-10 20:05:06 wait, so it *is* up to date 2023-09-10 20:05:13 what is it even trying to upload 2023-09-10 20:07:12 it's not failing on upload 2023-09-10 20:09:15 oh 2023-09-10 20:09:36 could it be the same thing as in this job: https://gitlab.alpinelinux.org/spameier/aports/-/jobs/1108907 ? 2023-09-10 20:09:49 or is the latter CI-specific 2023-09-10 20:10:15 ohhhhh 2023-09-10 20:10:17 I think there is a syntax error in community 2023-09-10 20:10:22 is some package in community unsetting JOBS 2023-09-10 20:10:23 and ap fails 2023-09-10 20:10:30 no, the jobs one is innocent 2023-09-10 20:11:01 one thing that comes to mind is 39b9da579 not having the case.. cases terminated with ";;" 2023-09-10 20:11:19 sh: ./APKBUILD: line 48: syntax error: unexpected ")" (expecting ";;") 2023-09-10 20:11:24 eyup 2023-09-10 20:11:30 i'll fix that real quick 2023-09-10 20:11:33 thanks 2023-09-10 20:33:38 algitbot: retry 3.18-stable 2023-09-11 05:18:08 wondering why kitty is running out of memory. Maybe an endianness issue? 2023-09-11 12:49:56 > testing/spotify 2023-09-11 12:50:03 wha- 2023-09-11 12:50:20 ohh, py3-mopidy-spotify.. 2023-09-13 10:36:00 algitbot: retry master 2023-09-13 20:39:37 algitbot: retry master 2023-09-13 20:44:35 hm 2023-09-13 20:44:52 what happened to ad652682 2023-09-13 20:44:55 it's kinda.. not here? 2023-09-13 20:45:52 "Error occurred while executing the hook's command. Please check your logs for more details" :P 2023-09-13 20:46:01 made a syntax error, 2 messages were lost 2023-09-13 20:46:48 ohh, makes sense :p 2023-09-15 13:17:08 algitbot:retry community 2023-09-15 13:32:12 algitbot:retry community 2023-09-15 13:36:26 algitbot: retry master 2023-09-15 17:29:28 algitbot: retry master 2023-09-16 02:23:15 algitbot: kick master 2023-09-16 02:24:02 algitbot: kick x86 2023-09-16 02:24:30 algitbot: kick build-edge-x86 2023-09-16 02:32:10 algitbot: retry testing 2023-09-16 02:32:26 algitbot: retry community 2023-09-16 02:40:54 It seems smplxmpp will need some fmt10 patching too, but i don't see any activity upstream.. 2023-09-16 02:51:41 Hmm, if i do a git pull now and open a new MR, the CI would attempt to build all the nheko/smplxmpp stuff that's failing now, right? 2023-09-16 02:53:33 On second thought, maybe not 2023-09-16 05:50:42 Alright, !51690 should unblock the builders (at least for nheko) 2023-09-16 05:52:40 The commits for coeurl and mtxclient that bump pkgrel can probably just be dropped when merged against master, i just needed them to make the CI pass (as those 2 rebuilds haven't gone into the repo due to the builders being blocked) 2023-09-16 06:55:36 celie: thanks, lets see if that helps 2023-09-16 07:06:09 ikke: You're welcome, though there's smplxmpp now...for which i couldn't find any patch upstream 2023-09-16 07:08:24 Maybe this: "Removed deprecated implicit conversions for enums and conversions to primitive types for compatibility with std::format and to prevent potential ODR violations. Use format_as instead" 2023-09-16 07:12:00 celie: The message comes from gloox, maybe the fix is there 2023-09-16 07:30:42 I believe it's the subtype, which is an EventType, which is an Enum, is what is not being able to be formatted 2023-09-16 07:31:04 but smplxmpp uses spdlog, which then uses fmt 2023-09-16 07:31:15 So in total 4 projects involved 2023-09-16 07:31:41 gloox, smplxmpp, spdlog, fmt 2023-09-16 07:33:54 I can't seem to find anything relevant in gloox's svn 2023-09-16 07:35:10 I don't think it's a gloox isssue perse 2023-09-16 07:35:37 just that smplxmpp tries to pass one of the values (indirectly) to fmt, and fmt does not know how to format it 2023-09-16 07:36:10 and my suspicion it's msg.subtype() 2023-09-16 07:36:54 I found fmt::underlying() https://fmt.dev/latest/api.html?highlight=enum#_CPPv4I0EN3fmt10underlyingE12underlying_tI4EnumE4Enum 2023-09-16 07:36:58 but not sure if that's suitable 2023-09-16 07:37:19 I have to go now 2023-09-16 07:37:51 See you later 2023-09-16 07:59:49 It seems using fmt::underlying at least allows the build to complete (!51701) but not sure if this is the right solution 2023-09-16 08:00:39 and now i have to go too, bye 2023-09-16 10:52:29 algitbot: retry master 2023-09-16 13:08:52 algitbot: retry master 2023-09-17 21:10:42 > # TODO: make runs deterministic 2023-09-17 21:10:46 aaaaa 2023-09-17 21:10:49 algitbot: retry msater 2023-09-17 21:10:51 algitbot: retry master 2023-09-17 21:10:53 sigh 2023-09-17 21:56:40 algitbot: retry master 2023-09-17 21:57:41 algitbot: retry master 2023-09-17 21:58:52 algitbot: retry master 2023-09-17 22:02:15 algitbot: retry master 2023-09-18 12:00:02 hm, it didn't segfault on the CI 2023-09-18 12:00:11 hopefully some racy condition or something 2023-09-18 18:24:20 algitbot: retry master 2023-09-18 19:09:45 algitbot: retry master 2023-09-19 05:43:06 algitbot: retry master 2023-09-21 18:53:06 algitbot: retry master 2023-09-21 20:53:53 chereskata: ^ 2023-09-21 20:53:59 satisfies: gnome-bluetooth-42.6-r1[bluez>=5] 2023-09-21 20:53:59 breaks: obexd-enhanced-5.68-r0[bluez~5.68] 2023-09-21 20:53:59 ERROR: unable to select packages: 2023-09-21 20:53:59 bluez-5.59-r0: 2023-09-21 20:54:00 sigh 2023-09-21 20:54:13 that doesn't seem fun 2023-09-21 20:54:48 seems like obexd-enhanced needs to be bumped? 2023-09-21 20:54:54 oh 2023-09-21 20:54:59 im sorry 2023-09-21 20:55:17 i'm curious as to why that didn't fail in the CI 2023-09-21 20:55:46 i think the obexd-enhanced daemon is in community while bluez is in main 2023-09-21 20:55:55 also it was added after the mr was opened afaik 2023-09-21 20:56:55 In the pipeline: Installing obexd-enhanced (5.68-r0) 2023-09-21 20:57:24 Installing bluez (5.68-r2) 2023-09-21 20:57:33 oh? 2023-09-21 20:57:44 does it not install dependencies cross-repo from CI artifacts 2023-09-21 20:58:10 !51411 2023-09-21 20:58:21 bluez was bumped in a seperate MR 2023-09-21 20:58:30 ohh 2023-09-21 20:58:35 so these crossed each-other 2023-09-21 20:59:29 so who's bumping obexd-enhanced? :p 2023-09-21 21:02:38 git pull is taking forever atm 2023-09-21 21:03:18 i'm trying to bump it and i'm having some other minor problems, but that might be just a skill issue 2023-09-21 21:03:34 ERROR: unable to select packages: 2023-09-21 21:03:34 breaks: world[bluez~5.69] 2023-09-21 21:03:34 bluez-5.59-r0: 2023-09-21 21:03:37 like, what does that even mea 2023-09-21 21:03:38 n 2023-09-21 21:06:03 bluez available is 5.59, but it wants 5.69, which is not available 2023-09-21 21:06:44 hmm, I think that's a type 2023-09-21 21:06:46 typo 2023-09-21 21:06:52 bluez was downgraded to 5.59 2023-09-21 21:07:06 https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/51411/diffs#0d3498192788c33285d2c574c7876c17ba85f6f5_7_5 2023-09-21 21:07:37 chereskata: ^ 2023-09-21 21:09:02 oh wow 2023-09-21 21:09:14 yeah, that's a typo 2023-09-21 21:09:34 and nobody has noticed it, hah 2023-09-21 21:10:06 and some patches now seem to be superfluous 2023-09-21 21:10:45 and some fail to apply 2023-09-21 21:11:33 alright, i'll try and fix it 2023-09-21 21:11:36 thanks 2023-09-21 21:13:28 I'm sorry! 2023-09-21 21:13:39 that's alright, that's on us for not noticing it earlier :p 2023-09-21 21:22:39 ptrc: thank you for fixing my mistake 2023-09-21 21:22:51 no worries, you're welcome :)