2023-02-02 15:40:28 algitbot: retry master 2023-02-02 22:09:46 algitbot: retry 3.16-stable 2023-02-03 05:47:43 algitbot: retry master 2023-02-04 20:15:34 algitbot: retry master 2023-02-04 21:37:17 ikke: i'm not sure why that fails ^ 2023-02-04 21:37:20 i can't seem to reproduce it 2023-02-04 21:37:24 passed in ci too 2023-02-04 21:38:08 Issue is the illegal instruction? 2023-02-04 21:39:11 and the truncated invalid file somehow 2023-02-04 21:39:35 i guess it could just be something like avx2 in new libjxl but that wouldn't break every test i don't think 2023-02-04 21:51:55 basically seems to call `vips affine` and so on and fails on a .jpg 2023-02-04 21:52:10 iirc you said the ci machines did have avx2 didn't they 2023-02-04 21:53:27 psykose: yes, returned by /proc/cpuinfo 2023-02-04 22:04:09 now that is interesting 2023-02-04 22:15:54 yeah not related to jxl 2023-02-04 22:18:28 ok 2023-02-04 22:18:35 it's unconditional avx2 in libjpg 2023-02-04 22:18:46 libjpeg-turbo that is 2023-02-04 22:18:52 thank goodness i have a machine without avx2 2023-02-04 22:20:34 https://github.com/libjpeg-turbo/libjpeg-turbo/issues/649 2023-02-07 03:23:54 algitbot: retry master 2023-02-07 07:22:40 psykose, 2023-02-07 07:22:40 +source="$pkgname-$pkgver-2.tar.gz::https://github.com/greenbone/ospd-openvas/archive/v$pkgver.tar.gz 2023-02-07 07:22:44 what is this? 2023-02-07 07:41:06 fcolista: as the commit says, it fixes the checksums 2023-02-07 07:41:30 the names are cached in distfiles 2023-02-07 07:43:31 ddf48f628ad8 changed from e8cb6f86380c026eaf074.. to 9cc83d19faf6d0e394a.. because 9cc is the current checksums, but e8b was the one on github when they made the breaking change so it was reverted and changed back 2023-02-07 07:44:03 but distfiles had e8b cached so the name has to be changed to use a new one 2023-02-07 10:16:42 ikke: why does this riscv build get killed randomly after some time ^ 2023-02-07 11:26:15 psykose: not sure, nothing in /var/log/messages or dmesg 2023-02-07 11:26:28 it sounds like that timed autokill thing from a while ago 2023-02-07 11:26:41 potentially 2023-02-07 11:34:28 I'm not sure if that's still in place or where clandmeter would've added that 2023-02-07 15:48:44 ikke: what did i do? 2023-02-07 15:56:54 clandmeter: you experimented with a build timeout right? 2023-02-07 15:58:39 some time ago yes 2023-02-07 16:18:07 clandmeter: where did you add that 2023-02-07 16:29:41 algitbot: retry 3.14-stable 2023-02-07 17:49:18 quic-go 0.32.0 supports go 1.20 2023-02-07 17:53:23 hmm, so many packages will fail that depend on quic-go 2023-02-07 17:53:45 and since quic-go changed module name, it's not a simple version bump 2023-02-07 17:56:10 I had the suspicion I should wait 2023-02-07 18:06:21 algitbot: retry master 2023-02-07 18:17:08 too slow 2023-02-07 18:17:19 psykose: btw, how do you do these updates?/ 2023-02-07 18:17:58 git init; git add .; git commit -m asd; go get -u github.com/quic-go/quic-go@v0.32.0; go mod tidy; git diff; .. 2023-02-07 18:18:36 I don't even see quic-go being updated in the latest patch 2023-02-07 18:18:58 funny ain't it 2023-02-07 18:19:40 and yet it somehow builds after 2023-02-07 18:19:45 strange 2023-02-07 18:20:21 are you testing with go1.20? 2023-02-07 18:20:31 very good point :p 2023-02-07 18:22:12 sadly go mod tidy kills indirects 2023-02-07 18:23:09 probably because the packages still use the old naame 2023-02-07 18:23:15 so go mod tidy sees them as not used 2023-02-07 18:23:44 that's what I was referring to earlier 2023-02-07 18:29:19 algitbot: retry master 2023-02-07 18:30:37 algitbot: retry master 2023-02-07 18:31:17 the dendrite one is indeed hard then 2023-02-07 18:31:24 replace doesn't seem to work for some reason 2023-02-07 18:31:30 none of the imports are in itself 2023-02-07 18:35:21 normally a replace would work, but not combined with the module name change 2023-02-07 18:36:18 shall i just fork the repo and apply the rename :p 2023-02-07 18:36:23 that is an easy 2 minute fix i guess 2023-02-07 18:37:14 I once setup https://gitlab.alpinelinux.org/mirror 2023-02-07 18:38:33 but you'd need to fix all dependencies that use quic-go 2023-02-07 18:38:45 sure 2023-02-07 18:39:45 I also forked bolt: https://gitlab.alpinelinux.org/kdaudt/bolt 2023-02-07 18:40:29 not sure how many projects still use bolt 2023-02-07 18:51:00 frp still fails 2023-02-07 18:53:10 working on frp 2023-02-07 19:02:16 algitbot: retry master 2023-02-07 19:06:16 working on syncthing 2023-02-07 19:09:40 i was 2023-02-07 19:10:08 getting stuck though 2023-02-07 19:12:58 ah, syncthing has a new release 2023-02-07 19:15:34 ship it 2023-02-07 19:16:34 quic update was not part of it, including the commit as a patch 2023-02-07 19:27:55 let's see 2023-02-07 19:31:46 kubo be turbofucked 2023-02-07 19:33:30 also "update to " :p 2023-02-07 19:35:07 heh 2023-02-07 19:40:43 algitbot: retry master 2023-02-08 18:23:26 algitbot: retry master 2023-02-08 23:18:55 algitbot: retry master 2023-02-08 23:36:05 ikke: it looks like the s390x builder is having some connectivity issues (?) 2023-02-08 23:40:52 algitbot: retry 3.18-stable 2023-02-09 12:58:56 love networking 2023-02-09 13:04:40 eventually geoip mirror will work, but why does it not end up in distfiles anyway? ikke 2023-02-09 13:09:34 psykose: it's synced onces per day 2023-02-09 13:09:39 once* 2023-02-09 13:09:53 ah 2023-02-09 13:09:55 ok, makes sense 2023-02-09 13:10:11 that makes me curious, how does that work then 2023-02-09 13:10:18 local distfiles synced once daily? or 2023-02-09 13:10:28 (and then deleted locally) 2023-02-09 13:10:57 yes 2023-02-09 13:11:09 before it was x86_64 that hosted distfiles 2023-02-09 13:11:16 so whenever it downloaded something, it was availaable 2023-02-09 13:11:21 but now we moved it to an external host 2023-02-09 13:12:12 makes sense 2023-02-09 13:12:13 thanks 2023-02-09 13:12:37 (download.savannah.gnu.org is geoipd and these builders are in brazil and that mirror takes hours) 2023-02-09 14:14:23 psykose: I manually ran the sync script 2023-02-09 14:14:37 thanks 2023-02-09 15:17:09 algitbot: retry master 2023-02-10 05:40:21 ikke: you have to restart aarch64 for stunnel as always 2023-02-10 05:40:29 yay 2023-02-10 05:41:34 I just killed the test process which lets it continue 2023-02-10 05:45:08 did you get the name by chance 2023-02-10 05:45:26 sorry, no 2023-02-10 05:47:27 np 2023-02-10 06:06:54 algitbot: ping 2023-02-10 15:44:19 algitbot: retry 3.14-stable 2023-02-11 06:03:22 ikke: aarch64 is stuck again :p fun 2023-02-11 06:03:25 py3-trimesh 2023-02-11 13:49:51 ikke: could you restart 3.17-aarch64 and edge-aarch64 2023-02-11 13:53:43 algitbot: retry master 2023-02-11 13:53:48 algitbot: retry 3.17-stable 2023-02-11 13:59:25 novorol[m]: why would a mkinitfs problem break grub? 2023-02-11 13:59:43 oops, wrong channel 2023-02-11 14:40:43 author: psykose, comitter: alice :P 2023-02-11 14:41:04 gitlab rewrites the committer: field to the gitlab account username 2023-02-11 14:41:10 when you rebase in webui 2023-02-11 14:41:23 visible name not username* 2023-02-11 14:41:40 Yeah 2023-02-11 14:47:36 it is annoying indeed 2023-02-12 02:11:35 algitbot: kick master 2023-02-12 02:12:12 algitbot: kick build-edge-x86_64 2023-02-12 02:13:09 algitbot: kick build-edge-riscv64 2023-02-12 02:36:35 algitbot: retry master 2023-02-12 02:46:44 algitbot: retry master 2023-02-12 02:47:46 algitbot: retry master 2023-02-12 02:59:40 algitbot: retry master 2023-02-12 03:03:05 algitbot: retry master 2023-02-12 03:04:23 algitbot: retry master 2023-02-13 06:35:41 algitbot: retry master 2023-02-13 06:38:31 algitbot: retry master 2023-02-14 23:23:37 algitbot: retry master 2023-02-15 06:18:47 fun times 2023-02-15 07:45:26 more killed stuff 2023-02-15 20:33:23 fun failing test 2023-02-15 21:10:21 algitbot: retry 3.17-stable 2023-02-15 21:31:13 algitbot: retry 3.17-stable 2023-02-15 21:31:19 algitbot: retry master 2023-02-15 22:02:22 algitbot: retry 3.17-stable 2023-02-15 22:18:40 urg 2023-02-15 22:18:46 algitbot: retry master 2023-02-15 22:18:50 "address already in use? 2023-02-15 22:20:31 timing 2023-02-15 22:20:52 I know, it's stil anoying 2023-02-15 22:53:19 I know, it's stil anoying 2023-02-15 22:53:21 "address already in use? 2023-02-15 22:53:24 algitbot: retry master 2023-02-15 22:57:01 seems like vault no longer builds on 32-bits 2023-02-15 22:59:07 https://github.com/golang/go/issues/58503 2023-02-15 22:59:26 https://github.com/golang/go/issues/58425 2023-02-15 22:59:35 how did it build on the 1.20 rebuild haha 2023-02-15 23:01:33 algitbot: retry master 2023-02-16 11:32:22 algitbot: retry master 2023-02-17 20:16:38 something something abuild checksum 2023-02-17 20:17:11 something something YES YES EVERY TIME 2023-02-17 20:17:21 i'm terrible at these 2023-02-17 20:20:14 algitbot: retry master 2023-02-20 12:44:09 algitbot: retry master 2023-02-22 20:57:17 algitbot: retry master 2023-02-22 20:57:22 flock FAILED 2023-02-22 20:57:28 such wow, much detail 2023-02-25 16:20:22 algitbot: retry master 2023-02-26 20:46:58 algitbot: retry master 2023-02-26 20:53:51 algitbot: retry master 2023-02-26 21:26:43 algitbot: retry master 2023-02-26 21:26:57 algitbot: retry master 2023-02-26 21:27:03 success 2023-02-26 21:27:15 algitbot: retry 3.17-stable 2023-02-27 18:30:06 algitbot: retry master 2023-02-27 20:38:50 algitbot: retry master 2023-02-28 05:57:15 algitbot: retry master 2023-02-28 06:41:51 algitbot: retry master