2022-10-01 09:33:13 algitbot: retry master 2022-10-01 17:07:30 algitbot: retry 3.16-stable 2022-10-03 09:53:21 algitbot: retry master 2022-10-03 09:55:38 algitbot: retry master 2022-10-03 10:00:16 algitbot: retry master 2022-10-03 10:00:36 algitbot: retry master 2022-10-04 15:24:05 algitbot: do your magic 2022-10-04 15:24:43 algitbot: retry master 2022-10-04 17:04:17 andypost[m]: ^ 2022-10-04 17:05:17 looks we should disable this tests, still no response from upstream 2022-10-04 18:21:26 hah 2022-10-04 18:21:28 i thought they fixed that 2022-10-04 18:21:36 guess not, probably nobody reported it then 2022-10-04 18:21:47 ran into it a month ago testing rcs 2022-10-04 18:22:21 (config_speakup having some broken headers) 2022-10-04 18:22:23 unknown type name u_char? 2022-10-04 18:24:22 ye 2022-10-04 18:36:51 mps: could you fix that ^ 2022-10-04 18:40:58 psykose: huh 2022-10-04 18:41:20 ok will disable speakup 2022-10-04 18:41:33 don't think that's the correct solution 2022-10-04 18:41:59 hmm, what is 2022-10-04 18:42:25 I see this first time 2022-10-04 18:43:07 it just needs #include most likely 2022-10-04 18:44:03 aha, but I don't want to start this 'game' with kernel 2022-10-04 18:45:03 psykose: you noticed this problem earlier? 2022-10-04 18:45:30 sure 2022-10-04 18:46:03 and you fixed it by patch? 2022-10-04 18:46:39 https://lkml.org/lkml/2022/8/16/580 2022-10-04 18:46:53 "I 2022-10-04 18:46:55 suspect because of the musl based host" 2022-10-04 18:47:29 patch included 2022-10-04 18:48:19 I see 2022-10-04 18:48:34 hmm, not sure what to do 2022-10-04 18:49:04 if we start with such patches in kernels who knows where we will end 2022-10-04 18:50:36 it worked quite fine with 5.19 series 2022-10-04 19:00:50 one patch is enough to break the build :) 2022-10-04 19:01:10 5.19 didn't contain this change in it 2022-10-04 19:01:19 no sure how it's relevant 2022-10-04 19:04:52 idk if anyone uses speakup with alpine 2022-10-04 19:05:14 never seen any report 2022-10-04 19:05:41 Someone was in #alpine-linux the other day 2022-10-04 19:06:56 lmao 2022-10-04 19:07:00 "So I loaded the Alpine Linux image on a USB today and I could not mod probe the speak up module. I know it is included in the Linux kernel maybe somebody could help me out." 2022-10-04 19:07:15 ahm 2022-10-04 19:07:30 huh, ok, lets add patch 2022-10-04 19:09:00 uh, patch is not small 2022-10-04 19:09:08 it's one line 2022-10-04 19:09:53 https://lkml.org/lkml/diff/2022/8/16/580/1 2022-10-04 19:10:54 I see, looked first one 2022-10-04 19:11:34 mps: I was helping someone to use speakup with Alpine about 2 weeks ago 2022-10-04 19:11:46 minimal: yes, I was referring to that :) 2022-10-04 19:12:24 minimal: ok, I agree we should add it for now 2022-10-04 19:13:04 mps: its not that simple to enable the ISO so that a visually impared person can install Alpine though 2022-10-04 19:15:00 assuming they are not using hardware device for speech but want to use software then espeakup package needs to be moved from testing to community, added to the ISO packages, and setup up in some automatic fashion when ISO is booted 2022-10-04 19:15:39 building with patch to see will it pass 2022-10-04 19:33:43 minimal: psykose: ikke: pushed fix with patch. lets see 2022-10-04 19:33:48 should be ok 2022-10-04 19:33:50 yes, saw 2022-10-04 19:33:54 will fail once 2022-10-04 19:34:51 speakup is not enabled on armv7, btw 2022-10-04 19:35:15 do we have userspace tools 2022-10-04 19:39:51 algitbot: retry master 2022-10-04 19:40:06 mps: espeakup package is the userspace tool (for software synthesis) 2022-10-04 19:41:31 mps: in trying to help the guy I cobbled together some scripting to try and simplify the setup for him: https://github.com/dermotbradley/alpine-espeakup 2022-10-04 19:42:02 minimal: aha, good. will look if I find time 2022-10-04 19:42:36 would be good to test it and know how to set it, for users if someone ask 2022-10-04 19:43:12 mps: it was just to get a working setup on a VM. There's a catch-22 situation - if you are visually impaired then how do you install Alpine and a screenreader in order to be able to install Alpine?... 2022-10-04 19:46:19 minimal: happily I have good eyesight (after 35 years on computers I even don't need glasses) but would be nice to about it to some degree, for our possible users with less luck to help 2022-10-04 19:48:38 algitbot: retry master 2022-10-04 19:54:01 mps: 30 years ago I did research in this area, access to GUIs by the visually impaired 2022-10-04 19:56:04 minimal: long ago I found works of William Bates oftamologist and learned how to preserve eyesight 2022-10-04 19:57:13 don't like to give advises about health, but I think it is good read for anyone working with computers 2022-10-04 21:55:04 algitbot: kick build-edge-riscv64 2022-10-04 22:38:30 psykose: kicking does not work anymore 2022-10-04 22:39:15 and there is no need, the builder is still building 2022-10-04 22:39:36 the things its building got an upgrade so it will just build them again after 2022-10-04 22:39:41 i kick it for a reason not for fun 2022-10-04 22:39:58 its not implemented anymore 2022-10-04 22:40:02 i noticed 2022-10-04 22:40:05 i'm just telling you why 2022-10-05 05:13:30 algitbot: retry master 2022-10-06 11:27:10 algitbot: retry master 2022-10-06 15:30:51 algitbot: retry master 2022-10-06 18:24:04 algitbot: retry master 2022-10-06 22:23:02 algitbot: retry 3.13-stable 2022-10-07 16:34:41 I really like those git-lfs tests, it's immediately clear what failed and it's easy to fix 2022-10-07 16:34:53 haha 2022-10-07 16:35:08 tried upgrading the package and it still looks the same :( 2022-10-07 16:54:32 forgot to bump grafana-frontend as well 2022-10-07 16:56:08 ah, thanks 2022-10-07 17:03:49 ikke: was tzdata previously installed on the builders or something? 2022-10-07 17:03:57 nmeum: not that I'm aware of 2022-10-07 17:04:01 minimal, yq and miller all fail because tzdata is missing 2022-10-07 17:04:04 I don't have tzdata in my container and it passes 2022-10-07 17:04:15 yq passes at least 2022-10-07 17:04:17 hm, in abuild rootbld it also fails without tzdata 2022-10-07 17:04:52 maybe something depended on tzdata and no longer does? 2022-10-07 17:05:14 yq only depends on go 2022-10-07 17:05:15 but wondering why it passed in my build container 2022-10-07 17:05:27 nmeum: I mean in the base packages installed on the builders 2022-10-07 17:05:33 ah, right that could be the case 2022-10-07 17:07:03 still wondering why it passes in my build container without tzdata 2022-10-07 17:07:37 are you sure that tzdata is not installed in your container? 2022-10-07 17:07:53 I don't know how it would be able to retrieve information about the Australia/Perth timezone otherwise (in the yq case) 2022-10-07 17:07:53 apk version tzdata returns nothing 2022-10-07 17:08:01 maybe the test is skipped in your container environment for some reason? 2022-10-07 17:08:09 was checking that 2022-10-07 17:10:15 === RUN TestDatetimeOperatorScenarios 2022-10-07 17:10:17 --- PASS: TestDatetimeOperatorScenarios (0.02s) 2022-10-07 17:11:15 are you on go 1.19.2 in your container? 2022-10-07 17:11:28 not yet 2022-10-07 17:11:32 let me test 2022-10-07 17:11:51 might be that they changed the time.LoadLocation implementation in go 1.19.2 2022-10-07 17:12:40 yet again a tzdata issue 2022-10-07 17:13:21 still passes 2022-10-07 17:13:24 hm, I don't see any direct changes to the time package in go 1.19.2 2022-10-07 17:14:34 do you set $ZONEFILE in your container environment? 2022-10-07 17:14:49 nope 2022-10-07 17:15:16 nothing timezone related 2022-10-07 17:16:41 oh, go 1.19.1 ships /usr/lib/go/lib/time/zoneinfo.zip 2022-10-07 17:16:52 openat(AT_FDCWD, "/usr/share/zoneinfo//Australia/Perth", O_RDONLY) = -1 ENOENT (No such file or directory) 2022-10-07 17:16:52 openat(AT_FDCWD, "/usr/share/lib/zoneinfo//Australia/Perth", O_RDONLY) = -1 ENOENT (No such file or directory) 2022-10-07 17:16:52 openat(AT_FDCWD, "/usr/lib/locale/TZ//Australia/Perth", O_RDONLY) = -1 ENOENT (No such file or directory) 2022-10-07 17:16:52 openat(AT_FDCWD, "/usr/lib/go/lib/time/zoneinfo.zip", O_RDONLY) = 3 2022-10-07 17:17:21 I still have that 2022-10-07 17:17:31 /usr/lib/go/lib/time/zoneinfo.zip is owned by go-1.19.2-r0 2022-10-07 17:17:48 yea me too 2022-10-07 17:17:51 wierd 2022-10-07 17:17:55 why not on the builders then? 2022-10-07 17:18:05 let me look at tz 2022-10-07 17:18:09 https://tpaste.us/bnYW 2022-10-07 17:18:15 this is what I am stracing locally 2022-10-07 17:18:17 can you run that on the builders? 2022-10-07 17:18:22 yes 2022-10-07 17:19:36 strange: openat(AT_FDCWD, "/usr/lib/go/lib/time/zoneinfo.zip", O_RDONLY|O_LARGEFILE) = 3 2022-10-07 17:19:43 on build-edge-armv7 2022-10-07 17:20:14 does the program panic? 2022-10-07 17:20:18 nope 2022-10-07 17:20:33 prints Australia/Perth 2022-10-07 17:20:43 let me check yq on aarch64 2022-10-07 17:21:10 hm, in abuild rootbld it panics 2022-10-07 17:21:42 tzdata is at least not installed 2022-10-07 17:21:56 openat(AT_FDCWD, "/usr/share/lib/zoneinfo//Australia/Perth", O_RDONLY) = -1 ENOENT (No such file or directory) 2022-10-07 17:21:56 openat(AT_FDCWD, "/usr/share/zoneinfo//Australia/Perth", O_RDONLY) = -1 ENOENT (No such file or directory) 2022-10-07 17:21:56 openat(AT_FDCWD, "/usr/lib/locale/TZ//Australia/Perth", O_RDONLY) = -1 ENOENT (No such file or directory) 2022-10-07 17:22:02 it doesn't try to open /usr/lib/go/lib/time/zoneinfo.zip in rootbld 2022-10-07 17:22:26 AAAAHHH! 2022-10-07 17:22:29 > GOROOT=/usr/lib/go ./main 2022-10-07 17:22:31 that works 2022-10-07 17:22:35 > ./main 2022-10-07 17:22:37 that panics 2022-10-07 17:23:19 was GOROOT previously set on the builders in /etc/abuild.conf or something? 2022-10-07 17:23:33 no 2022-10-07 17:24:35 nmeum: on the builder, it passes if I use go test directly, but fails if I use abuild 2022-10-07 17:24:41 so it's definitely something in the env 2022-10-07 17:24:51 yea, it's about GOROOT 2022-10-07 17:25:04 since tzdata isn't installed it looks for zoneinfo.zip 2022-10-07 17:25:12 and it finds zoneinfo.zip relative to GOROOT 2022-10-07 17:25:18 and if it can't find zoneinfo.zip then it fails 2022-10-07 17:25:21 GOROOT is not set in the nev 2022-10-07 17:25:27 env* 2022-10-07 17:26:35 nmeum: https://tpaste.us/70J9 2022-10-07 17:26:41 (set in the package) 2022-10-07 17:27:13 yea I saw 2022-10-07 17:27:21 it probably determines GOROOT using runtime.GOROOT() 2022-10-07 17:27:28 in my rootbld runtime.GOROOT returns "" 2022-10-07 17:27:36 if GOROOT is not set in the environment 2022-10-07 17:27:59 outside abuild rootbld runtime.GOROOT returns /usr/lib/go even if GOROOT is not set in the environment :DD 2022-10-07 17:28:25 https://cs.opensource.google/go/go/+/refs/tags/go1.19.2:src/runtime/extern.go;l=255 2022-10-07 17:28:35 GOFLAGS is what causes it to fail 2022-10-07 17:29:05 https://tpaste.us/1lW9 2022-10-07 17:29:09 This fails 2022-10-07 17:29:12 right 2022-10-07 17:29:18 without GOFLAGS it works 2022-10-07 17:29:19 but why? 2022-10-07 17:29:28 maybe due to trimpath? 2022-10-07 17:29:38 ohh!! 2022-10-07 17:29:52 yes 2022-10-07 17:29:54 wasn't trimpath recently enabled by default? 2022-10-07 17:29:57 yes 2022-10-07 17:29:59 that's why it didn't fail before 2022-10-07 17:30:00 ah 2022-10-07 17:30:12 But why would -trimpath do that.. 2022-10-07 17:31:22 trimpath probably nukes GOROOT 2022-10-07 17:32:52 https://tpaste.us/pngj 2022-10-07 17:32:59 yea, trimpath unsets GOROOT it seems 2022-10-07 17:33:09 and without GOROOT it doesn't find zoninfo.zip 2022-10-07 17:35:43 https://github.com/golang/go/commit/9ac75d39514402d9b314e758524dcc28612b8937 2022-10-07 17:36:50 reading the trimpath documentation again this does make sense also 2022-10-07 17:37:29 after all it would otherwise depend on the GOROOT file system path and trimpaths purpose is to remove "all file system paths from the resulting executable" 2022-10-07 17:37:36 why did we enable -trimpath by default again? 2022-10-07 17:38:34 https://gitlab.alpinelinux.org/alpine/abuild/-/commit/79624340a1ef4ef6aef7d6dc2cd24dba7e014237 2022-10-07 17:38:47 No real reason 2022-10-07 17:39:33 well… 2022-10-07 17:39:45 so we either revert that or we add tzdata everywhere :S 2022-10-07 17:40:08 I don't fully understand why using -trimpath by default is useful for us 2022-10-07 17:41:04 I suppose to prevent leaking build dirs in the binary? 2022-10-07 17:41:54 is that really a problem? 2022-10-07 17:42:06 for reproducability probably 2022-10-07 17:44:26 hm, well… 2022-10-07 17:44:41 we can make go itself depend on tzdata 2022-10-07 17:44:50 hm 2022-10-07 17:44:54 i don't know 2022-10-07 17:45:06 It does not really need it itself 2022-10-07 17:45:39 true 2022-10-07 17:45:52 I guess adding tzdata to checkdepends of affected packages is actually fine 2022-10-07 17:45:56 yup 2022-10-07 17:46:01 I mean if you use those packages you will actually need to install tzdata too 2022-10-07 17:46:07 since you don't have /usr/lib/go then 2022-10-07 17:46:14 but then you need it in depends 2022-10-07 17:46:17 not checkdepends 2022-10-07 17:46:25 but that was also the case before 2022-10-07 17:46:54 but in many cases it happens to be already installed I suppose 2022-10-07 17:46:56 implicitly 2022-10-07 17:47:02 yes 2022-10-07 17:47:08 I think you can also argue that it is an optional dependency 2022-10-07 17:47:31 it's not really pulled in by a lot or something basic 2022-10-07 17:50:10 ^ this package for example should definitly have a run-time dependency on tzdata for example as you can't display information about other timezones otherwise 2022-10-07 17:50:20 (which is the purpose of the package according to the $pkgdesc) 2022-10-07 17:52:23 nmeum: yes, makes sense 2022-10-07 17:52:36 yq you can argue about 2022-10-07 17:52:49 It would only come up when you do things with timezones 2022-10-07 17:53:23 yea, for yq it is an optional dependency imho 2022-10-07 18:00:50 hmm, it does depend on unbound-dev 2022-10-07 18:01:25 oh, my bad 2022-10-07 18:01:27 algitbot: retry master 2022-10-07 18:46:37 algitbot: retry master 2022-10-07 19:09:12 algitbot: retry master 2022-10-07 19:11:43 algitbot: retry master 2022-10-07 19:12:19 algitbot: retry master 2022-10-07 19:28:13 nmeum: geth still has issues 2022-10-07 19:36:09 nmeum: geth still has issues 2022-10-07 20:11:55 algitbot: retry master 2022-10-07 20:23:23 algitbot: retry master 2022-10-07 20:42:32 algitbot: retry master 2022-10-07 21:07:20 algitbot: retry master 2022-10-07 21:51:42 algitbot: retry master 2022-10-07 22:30:55 algitbot: retry master 2022-10-07 22:51:02 algitbot: retry master 2022-10-07 23:11:20 algitbot: retry 3.16-stable 2022-10-07 23:28:46 algitbot: retry 3.16-stable 2022-10-07 23:35:26 algitbot: retry 3.16-stable 2022-10-07 23:44:25 algitbot: retry 3.16-stable 2022-10-08 00:07:47 algitbot: retry 3.16-stable 2022-10-08 00:14:04 algitbot: retry 3.16-stable 2022-10-08 00:23:24 algitbot: retry master 2022-10-08 00:38:16 algitbot: retry 3.16-stable 2022-10-08 00:39:09 algitbot: retry master 2022-10-08 00:44:17 algitbot: retry 3.16-stable 2022-10-08 00:55:59 algitbot: retry master 2022-10-08 00:56:09 algitbot: retry 3.16-stable 2022-10-08 06:48:46 algitbot: retry master 2022-10-08 11:58:54 algitbot: retry master 2022-10-08 12:04:35 ikke: is there anything weird in the world of those builders ^ 2022-10-08 12:04:41 passes locally fine 2022-10-08 12:08:12 psykose: no 2022-10-08 12:08:16 strange 2022-10-08 12:08:26 seems to fail on all builders 2022-10-08 12:13:27 psykose: fails in my build container as well 2022-10-08 15:05:32 algitbot: retry master 2022-10-08 15:11:00 algitbot: retry master 2022-10-08 17:09:31 algitbot: retry 3.15-stable 2022-10-08 17:26:14 algitbot: retry master 2022-10-08 17:37:24 algitbot: retry 3.15-stable 2022-10-08 17:38:01 algitbot: retry 3.14-stable 2022-10-08 18:23:11 psykose: fails in my build container as well 2022-10-08 18:23:13 oops 2022-10-08 18:23:17 algitbot: retry master 2022-10-08 18:25:12 passes in mine, certainly 2022-10-08 18:27:26 that was an accidental repost 2022-10-08 18:28:06 :) 2022-10-08 18:35:45 algitbot: retry 3.13-stable 2022-10-08 18:36:58 hmmm, yeah, that was what I was meant to do 2022-10-09 13:27:36 hmm, stripping fails 2022-10-09 13:27:38 strip: ./usr/libexec/wpe-webkit-1.1/stjDmJdm: not enough room for program headers, try linking with -N 2022-10-09 14:10:26 yeah just classic binutils stuff 2022-10-09 14:10:38 for actual strip it's more unfun to override with something else 2022-10-09 15:42:05 algitbot: retry master 2022-10-09 22:15:11 algitbot: retry master 2022-10-10 02:01:01 algitbot: retry master 2022-10-10 02:03:03 algitbot: retry master 2022-10-10 04:17:01 algitbot: retry 3.13-stable 2022-10-10 06:51:44 algitbot: retry master 2022-10-10 06:57:06 algitbot: retry master 2022-10-10 06:57:13 Fun, it succeeded on CI 🤔 2022-10-10 06:57:36 very cute error too 2022-10-10 06:58:05 any foobar.tar (1).gz enjoyers 2022-10-10 06:58:13 lol 2022-10-10 08:58:18 I... Don't know what's up with `kcoreaddons`. It succeeded on x86_64 CI and it also succeeded on the builders on every other arch. I suppose I could just disable that test for now? 2022-10-10 09:03:22 maybe, but the test is very clear cut 2022-10-10 09:03:35 << "foobar.tar.gz" << (QStringList() << QStringLiteral("foobar.tar.gz")) << "foobar (1).tar.gz" 2022-10-10 09:03:41 and yet it completely gets inverted doing that 2022-10-10 09:03:50 etc 2022-10-10 09:04:03 it's so peculiar it almost makes me think something is completely broken 2022-10-10 09:04:10 yet at the same time it's probably nothing 2022-10-10 09:07:48 ah 2022-10-10 09:08:28 does go a bit deeper and calls KFileUtils::suggestName() with that, but yeah 2022-10-10 09:08:29 weh 2022-10-10 14:55:09 algitbot: retry master 2022-10-10 22:41:54 algitbot: retry master 2022-10-11 15:22:05 tomalok: the mdev-conf MR is unlikely to affect tiny-cloud, it simply adds the creation of /dev/block/* and /dev/disk/by-* entries to mdev and mdevd, these are expected by some of cloud-init's modules that configure disks 2022-10-11 15:22:19 oops, wrong channel :-) 2022-10-12 01:47:32 algitbot: retry master 2022-10-12 02:36:30 algitbot: retry master 2022-10-12 03:06:35 algitbot: retry master 2022-10-12 16:15:35 algitbot: retry master 2022-10-12 16:16:42 algitbot: retry master 2022-10-12 16:24:50 algitbot: retry master 2022-10-12 16:42:05 algitbot: retry master 2022-10-13 01:01:15 algitbot: retry master 2022-10-14 06:31:16 algitbot: retry master 2022-10-14 06:32:40 algitbot: retry master 2022-10-14 06:36:33 algitbot: retry master 2022-10-14 06:39:20 algitbot: retry master 2022-10-14 06:58:43 algitbot: retry master 2022-10-14 07:33:31 algitbot: retry master 2022-10-14 15:27:49 algitbot: retry master 2022-10-14 20:45:12 algitbot: retry master 2022-10-14 21:48:24 algitbot: retry master 2022-10-14 22:39:20 algitbot: retry master 2022-10-14 23:10:33 algitbot: retry master 2022-10-15 00:43:18 algitbot: retry master 2022-10-15 00:52:44 algitbot: retry master 2022-10-15 02:20:11 algitbot: retry master 2022-10-15 07:45:58 PureTryOut: ark has test failures on x86_64 ^ 2022-10-15 08:51:27 What the hell. Why do things often go through CI fine and then fail on the builders? 😢 2022-10-15 08:52:27 algitbot: retry master 2022-10-15 09:13:35 hard to tell in a general sense 2022-10-15 09:24:34 h 2022-10-16 01:03:27 algitbot: retry master 2022-10-16 10:03:39 fcolista: perl-type-tiny fails on 32-bits arches 2022-10-16 10:03:48 test failure 2022-10-16 14:01:52 algitbot: retry master 2022-10-16 14:02:17 I suppose we'd need to disable that speciifc test for now 2022-10-17 14:04:41 algitbot: retry master 2022-10-17 15:33:08 algitbot: retry master 2022-10-18 04:38:52 algitbot: retry master 2022-10-19 16:57:37 algitbot: retry master 2022-10-19 17:16:04 algitbot: retry master 2022-10-19 17:16:24 algitbot: retry 3.16-stable 2022-10-19 17:16:50 algitbot: retry 3.15-stable 2022-10-19 17:17:02 algitbot: retry 3.14-stable 2022-10-19 17:17:05 algitbot: retry 3.13-stable 2022-10-19 21:10:11 algitbot: retry 3.13-stable 2022-10-19 21:39:41 algitbot: retry 3.13-stable 2022-10-20 08:21:48 algitbot: retry 3.13-stable 2022-10-20 08:33:04 algitbot: retry 3.14-stable 2022-10-20 10:39:31 retry 3.15-stable 2022-10-20 10:39:40 algitbot: retry 3.15-stable 2022-10-20 11:07:25 algitbot: retry 3.16-stable 2022-10-20 12:07:15 algitbot: retry 3.15-stable 2022-10-20 12:07:25 algitbot: retry 3.16-stable 2022-10-20 12:45:51 algitbot: retry master 2022-10-20 13:30:05 (that was me) 2022-10-20 13:45:46 hmm 2022-10-20 13:45:49 that is bizarre 2022-10-20 13:46:00 ikke: i think the 3.16-ppc builder is fucked in some way 2022-10-20 13:46:19 the libprotobuf had a missing symbol that is caused by having something not rebuild against gcc11 libstdc++ 2022-10-20 13:46:27 then on rebuild of protobuf ruby is missing qsort_r 2022-10-20 13:46:31 but all of that is present in 3.16 2022-10-20 13:46:37 it's like it's a.. 3.15 builder? 2022-10-20 13:46:53 3.15 didn't have gcc11 or qsort_r iirc 2022-10-20 13:47:36 it looks like what would happen if world was half 3.15/3.16 with 3.15 deps of the mentioned things but some things from 3.16 2022-10-20 13:47:50 could you triple check it :) 2022-10-20 14:13:54 algitbot: retry master 2022-10-20 14:13:58 algitbot: retry 3.16-stable 2022-10-20 14:14:00 algitbot: retry 3.15-stable 2022-10-20 14:14:02 algitbot: retry 3.14-stable 2022-10-20 14:14:05 algitbot: retry 3.13-stable 2022-10-20 14:15:35 find anything? 2022-10-20 14:15:51 We're trying to tighten the mqtt config 2022-10-20 14:16:07 yeah, can't see build status anymore 2022-10-20 14:16:18 Made build/# read-only for anomous 2022-10-20 14:16:40 anonymous* 2022-10-20 14:16:46 could you also look at the ppc thing before i forget 2022-10-20 14:17:04 Oh, I missed that 2022-10-20 14:22:51 psykose: I think that's something ncopa will need to look at 2022-10-20 14:22:58 I'm almost heading off for the weekend 2022-10-20 14:23:08 safe travels 2022-10-20 14:29:19 i can clean up 2022-10-20 14:29:54 psykose: what ppc thingy? 2022-10-20 14:30:03 scroll up a bit 2022-10-20 14:30:39 looks like the 3.16-ppc builder is not on 3.16 2022-10-20 14:31:15 indeed. it is not 2022-10-20 14:31:54 some amount of things already rebuilt incorrectly, don't know which ones 2022-10-20 14:34:44 i know 2022-10-20 14:34:54 find packages/ -ctime -4 -type f -delete 2022-10-20 14:35:01 anything build within last 4 days 2022-10-20 14:36:36 algitbot: retry 3.16-stable 2022-10-20 14:37:27 ah yea 2022-10-20 14:37:33 that works, thanks a lot :) 2022-10-20 14:37:48 now just have to let build.a.o see the status somehow 2022-10-20 14:37:58 ah, 3.16 is visible 2022-10-20 14:38:01 almost 2022-10-20 14:44:16 algitbot: retry 3.16-stable 2022-10-20 15:03:24 algitbot: retry master 2022-10-20 15:07:59 i think stuff is building. we can just not see anything no msg.a.o 2022-10-20 15:16:25 yeah 2022-10-20 15:16:30 errors still get printed here 2022-10-20 15:16:32 no blockers for me 2022-10-20 15:16:33 idc 2022-10-20 15:18:16 algitbot: retry master 2022-10-20 15:18:22 algitbot: retry 3.15-stable 2022-10-20 15:21:25 (unless they don't actually get printed) 2022-10-20 15:24:36 algitbot: retry 3.15-stable 2022-10-20 15:56:55 algitbot: retry master 2022-10-20 15:57:12 algitbot: retry 3.15-stable 2022-10-20 15:58:13 are the errors not actually printed or is there some other reason to retry things 2022-10-20 16:00:46 I reenabled anonymous write access again until we found out how to make it work 2022-10-20 16:01:23 we need to fix both aports-build as the lua plugin 2022-10-20 16:01:50 mqtt-exec authentication is not that important, as it would only read 2022-10-20 16:05:50 ~ 2022-10-20 16:32:24 algitbot: retry master 2022-10-20 16:48:35 algitbot: retry master 2022-10-20 17:47:39 algitbot: retry 3.16-stable 2022-10-20 18:42:28 algitbot: retry master 2022-10-20 19:43:19 algitbot: retry master 2022-10-20 19:56:10 algitbot: retry master 2022-10-20 21:39:07 algitbot: retry master 2022-10-20 23:40:53 algitbot: retry master 2022-10-21 08:51:39 algitbot: retry master 2022-10-21 11:03:14 algitbot: retry master 2022-10-21 14:08:44 algitbot: retry master 2022-10-21 15:58:01 algitbot: retry master 2022-10-21 16:21:27 psykose: thanks for taking care of the build fail 2022-10-21 17:29:10 algitbot retry master 2022-10-21 17:34:05 algitbot: retry master 2022-10-21 21:41:59 algitbot: retry 3.14-stable 2022-10-21 21:44:06 algitbot: retry master 2022-10-22 09:31:35 algitbot: retry master 2022-10-22 10:57:26 algitbot: retry 3.16-stable 2022-10-23 17:05:11 ooh ffs lol, fixing 2022-10-23 17:11:19 I'm... Pushing things to quickly... Ignore me 2022-10-23 17:11:32 algitbot: kick master 2022-10-23 17:11:53 algitbot: kick edge 2022-10-23 17:11:57 nvm then 2022-10-23 17:12:44 algitbot: retry master 2022-10-23 17:13:33 you added a prefix of qtdeclarative- to the qtbase tarball 2022-10-23 17:13:37 (in https://git.alpinelinux.org/aports/commit/?id=0613f67a089e) 2022-10-23 17:14:18 I noticed hold on 2022-10-23 17:14:29 no worries ^_^ 2022-10-23 17:14:32 (I'm watching this channel closely 😜) 2022-10-23 17:15:54 ffs I need to stop doing things now 2022-10-23 17:16:01 algitbot: retry master 2022-10-23 17:16:48 algitbot: retry master 2022-10-23 21:24:54 algitbot: retry master 2022-10-23 21:29:52 algitbot: retry master 2022-10-23 21:36:56 algitbot: retry master 2022-10-23 22:27:57 algitbot: retry master 2022-10-23 22:47:53 algitbot: retry master 2022-10-23 23:16:07 algitbot: retry master 2022-10-24 02:35:43 algitbot: retry master 2022-10-24 08:01:05 Uh I clicked merge on the wrong thing it seems, damn 2022-10-24 08:10:30 algitbot: retry master 2022-10-24 08:14:51 algitbot: retry master 2022-10-24 11:15:54 algitbot: retry master 2022-10-24 14:20:35 algitbot: retry master 2022-10-24 14:22:44 algitbot: retry master 2022-10-24 14:31:11 algitbot: retry master 2022-10-24 14:35:04 algitbot: retry master 2022-10-24 14:36:29 algitbot: retry master 2022-10-24 14:50:45 algitbot: retry master 2022-10-24 15:04:35 algitbot: retry master 2022-10-24 15:05:26 algitbot: retry master 2022-10-24 15:39:12 ikke: is there a chance https://gitlab.alpinelinux.org/alpine/infra/docker/alpine-gitlab-ci/-/merge_requests/12 could get merged? 2022-10-24 15:39:37 could prevent some new checksum mismatches 2022-10-24 15:48:40 algitbot: retry master 2022-10-24 16:21:41 algitbot: retry master 2022-10-24 17:14:47 algitbot: retry master 2022-10-24 17:20:46 algitbot: retry master 2022-10-24 17:23:15 algitbot: retry master 2022-10-24 17:29:10 algitbot: retry master 2022-10-24 17:50:22 algitbot: retry master 2022-10-24 18:06:09 algitbot: retry master 2022-10-24 18:10:04 algitbot: retry master 2022-10-24 18:14:48 ncopa: you forgot to uninstall some makedepends on ppc64le i think 2022-10-24 18:14:59 or they were just left over 2022-10-24 18:15:10 algitbot: retry master 2022-10-24 18:20:26 algitbot: retry master 2022-10-24 18:59:28 algitbot: retry master 2022-10-24 19:13:41 algitbot: retry master 2022-10-24 19:27:57 algitbot: retry master 2022-10-24 19:33:53 algitbot: retry master 2022-10-24 19:50:43 algitbot: retry master 2022-10-24 20:10:44 algitbot: retry master 2022-10-24 20:24:21 i think the makedepends are removed on ppc64le 2022-10-24 20:31:59 ncopa: did you remove them? 2022-10-24 21:21:40 algitbot: retry master 2022-10-24 21:34:21 algitbot: retry master 2022-10-24 21:44:13 algitbot: retry master 2022-10-24 21:51:26 algitbot: retry master 2022-10-24 22:32:45 algitbot: retry master 2022-10-24 22:43:14 algitbot: retry master 2022-10-24 23:28:47 algitbot: retry master 2022-10-24 23:38:31 algitbot: retry master 2022-10-24 23:48:04 algitbot: retry master 2022-10-25 00:07:00 algitbot: retry master 2022-10-25 00:46:29 algitbot: retry master 2022-10-25 01:03:13 algitbot: retry master 2022-10-25 01:11:41 algitbot: retry master 2022-10-25 01:24:40 algitbot: retry master 2022-10-25 01:28:13 algitbot: retry master 2022-10-25 01:46:19 algitbot: retry master 2022-10-25 01:52:45 algitbot: retry master 2022-10-25 02:13:14 algitbot: retry master 2022-10-25 02:20:06 algitbot: retry master 2022-10-25 02:27:40 algitbot: retry master 2022-10-25 05:02:57 algitbot: retry master 2022-10-25 05:55:55 algitbot: retry master 2022-10-25 07:24:13 algitbot: retry master 2022-10-25 08:47:44 algitbot: retry master 2022-10-25 11:15:30 algitbot: retry master 2022-10-25 14:55:13 ah, that was already fixed 2022-10-25 15:01:01 psykose only 4 packages using inaccessible luaforge 2022-10-25 15:01:27 not sure what to replace them with 2022-10-25 15:01:31 that one seems completely dead 2022-10-25 15:01:33 it's like a 2008 package 2022-10-25 15:01:54 https://gitlab.com/craigbarnes/lua-discount/-/tags looks it maintained 2022-10-25 15:02:00 that's not the same thing 2022-10-25 15:02:01 maybe just copy from distfiles to dev.a.o? 2022-10-25 15:02:51 main/lua-discount main/lua-rex main/lua-yaml 2022-10-25 15:06:56 lua-rex is using github 2022-10-25 15:07:05 same for lua-yaml 2022-10-25 15:10:45 algitbot: retry master 2022-10-25 15:35:06 algitbot: retry master 2022-10-25 15:42:28 algitbot: retry master 2022-10-25 16:51:28 algitbot: retry master 2022-10-25 17:25:33 algitbot: retry master 2022-10-25 17:52:53 algitbot: retry master 2022-10-25 18:07:42 algitbot: retry master 2022-10-25 18:32:23 algitbot: retry master 2022-10-25 18:57:47 algitbot: retry master 2022-10-25 18:59:07 algitbot: retry master 2022-10-25 19:08:30 algitbot: retry master 2022-10-25 19:36:50 algitbot: retry master 2022-10-25 20:19:22 algitbot: retry master 2022-10-25 20:49:25 algitbot: retry master 2022-10-25 21:18:00 algitbot: retry master 2022-10-25 21:21:04 I have not seen a release where fail2ban didn't fail 2022-10-25 21:21:28 Something about the name 2022-10-25 21:21:43 this one has failed twice now 2022-10-25 21:21:46 but i still think it's a flake 2022-10-25 21:21:47 weird tests 2022-10-25 21:22:11 release is going much faster this time 2022-10-25 21:22:16 x86 is almost done with main 2022-10-25 21:22:20 last time it took us days 2022-10-25 21:22:56 openjdk will have the hanging problems after i guess on ppc/aarch64 around 10/11 and fail 2022-10-25 21:23:00 that will need a real fix 2022-10-25 21:23:05 still a day or two to fix that 2022-10-25 21:23:47 I think main was done quite quick previously as well 2022-10-25 21:24:45 hm 2022-10-25 21:24:45 well 2022-10-25 21:24:48 bedtime for me almost 2022-10-25 21:24:51 i'll get to the rest tomorrow 2022-10-25 21:25:09 for me as well 2022-10-25 21:25:36 btw some failures were also fixed a bit early with the cmd: provider rebuild 2022-10-25 21:25:55 hmm, did that break somehow? 2022-10-25 21:26:02 the cmd: provider 2022-10-25 21:26:19 abuild started versioning them by default 2022-10-25 21:26:22 yes 2022-10-25 21:26:29 but that was some releases ago already 2022-10-25 21:26:34 but stale packages had the provides unversioned 2022-10-25 21:26:41 so 700+ packages were rebuilt 2022-10-25 21:26:48 ah ok, stale packages in edge 2022-10-25 21:26:51 mhm 2022-10-25 21:30:26 i've rebuilt thousands of things for random shit and cleaned up a ton of stuff 2022-10-25 22:50:04 algitbot: retry master 2022-10-25 23:17:49 algitbot: retry master 2022-10-25 23:38:10 algitbot: retry master 2022-10-26 00:01:21 algitbot: retry master 2022-10-26 00:12:51 algitbot: retry master 2022-10-26 00:16:06 algitbot: retry master 2022-10-26 00:25:58 xdg-utils 2022-10-26 00:26:09 algitbot: retry master 2022-10-26 00:31:26 algitbot: retry master 2022-10-26 00:32:14 algitbot: retry master 2022-10-26 00:38:15 algitbot: retry master 2022-10-26 00:46:37 algitbot: retry master 2022-10-26 00:59:06 algitbot: retry master 2022-10-26 09:45:32 algitbot: retry master 2022-10-26 10:47:38 algitbot: retry master 2022-10-26 10:50:19 algitbot: retry master 2022-10-26 10:55:27 algitbot: retry master 2022-10-26 11:02:17 algitbot: retry master 2022-10-26 11:13:36 algitbot: retry master 2022-10-26 11:15:12 algitbot: retry master 2022-10-26 11:19:45 algitbot: retry master 2022-10-26 11:20:31 algitbot: retry master 2022-10-26 11:31:38 ncopa: what is the abuild.conf for 3.17-s390x? 2022-10-26 11:32:33 $ ssh root@build-3-17-s390x cat /etc/abuild.conf | tpaste 2022-10-26 11:32:33 https://tpaste.us/VvxM 2022-10-26 11:33:01 how so? 2022-10-26 11:34:14 ncopa: anythign specific? 2022-10-26 11:34:35 oh 2022-10-26 11:34:38 nm 2022-10-26 11:35:00 :) 2022-10-26 11:39:20 maybe we should set the GOFLAGS 2022-10-26 11:41:08 shouldn't they come from the package? 2022-10-26 11:41:17 ncopa: that's not the default abuild.conf which it should be 2022-10-26 11:41:48 it's also missing the LDFLAGS with as-needed 2022-10-26 11:41:56 and the -fomit-frame-pointer 2022-10-26 11:42:02 it's in the .apk-new 2022-10-26 11:42:12 :/ 2022-10-26 11:42:36 we really need a better way to set this in a separate file that nobody touches so it's always overwriten by package 2022-10-26 11:42:58 We probably should start using ~/.abuild/abuild.conf for local overrides 2022-10-26 11:43:06 not sure if there are any downsides 2022-10-26 11:43:23 yeah. and/or adding /usr/share/abuild/default.conf so there is no backup 2022-10-26 11:43:46 s/so/as/? 2022-10-26 11:43:54 same effect :)_ 2022-10-26 11:44:56 i updated those on the builders 2022-10-26 11:45:18 im not sure we want -fomit-frame-pointer for s390x 2022-10-26 11:46:05 the default cflags should probably be what we want everywhere 2022-10-26 11:46:10 or we can change it to CFLAGS_$CARCH 2022-10-26 11:48:12 lets follow up on that after the release 2022-10-26 11:53:38 algitbot: retry master 2022-10-26 12:18:52 algitbot: retry master 2022-10-26 12:38:13 algitbot: retry master 2022-10-26 12:54:49 algitbot: retry master 2022-10-26 13:08:57 algitbot: retry master 2022-10-26 13:09:07 algitbot: retry master 2022-10-26 13:15:41 algitbot: retry master 2022-10-26 13:24:50 ikke: think it's time for rust, s390x also reached it 2022-10-26 13:47:08 algitbot: retry master 2022-10-26 13:51:04 algitbot: retry master 2022-10-26 13:54:17 algitbot: retry master 2022-10-26 14:03:41 algitbot: retry master 2022-10-26 14:05:06 algitbot: retry master 2022-10-26 14:15:46 algitbot: retry master 2022-10-26 14:24:06 algitbot: retry master 2022-10-26 14:49:58 algitbot: retry master 2022-10-26 15:07:05 algitbot: retry master 2022-10-26 15:12:16 algitbot: retry master 2022-10-26 15:17:21 algitbot: retry master 2022-10-26 15:23:36 some nice python improvements this release 2022-10-26 15:23:48 python is just 3 for everyone and the locale thing is fixed 2022-10-26 15:27:38 algitbot: retry master 2022-10-26 15:34:08 algitbot: retry master 2022-10-26 15:42:12 algitbot: retry master 2022-10-26 15:54:11 algitbot: retry master 2022-10-26 16:01:48 algitbot: retry master 2022-10-26 16:02:34 algitbot: retry master 2022-10-26 16:05:40 algitbot: retry master 2022-10-26 16:27:19 algitbot: retry master 2022-10-26 16:28:32 algitbot: retry master 2022-10-26 16:39:52 algitbot: retry master 2022-10-26 16:57:46 ikke: i think 3.17-s390x has some stray makedepends (or at least py3-docutils installed somehow) 2022-10-26 16:57:56 this error https://github.com/python/cpython/issues/98634 2022-10-26 17:04:35 algitbot: retry master 2022-10-26 17:08:22 algitbot: retry master 2022-10-26 17:12:21 algitbot: retry master 2022-10-26 17:13:14 algitbot: retry master 2022-10-26 17:19:37 algitbot: retry master 2022-10-26 17:22:29 algitbot: retry master 2022-10-26 17:29:24 algitbot: retry master 2022-10-26 17:30:30 algitbot: retry master 2022-10-26 17:32:00 algitbot: retry master 2022-10-26 17:34:12 algitbot: retry master 2022-10-26 17:39:43 algitbot: retry master 2022-10-26 17:53:06 algitbot: retry master 2022-10-26 17:55:18 algitbot: retry master 2022-10-26 17:59:53 algitbot: retry master 2022-10-26 18:37:20 algitbot: retry master 2022-10-26 19:11:59 algitbot: retry master 2022-10-26 19:27:31 algitbot: retry master 2022-10-26 19:29:49 algitbot: retry master 2022-10-26 19:33:23 psykose: makedepends for gogs and hugo were still installed, one of them pulling py3-docutils in 2022-10-26 19:33:30 :) 2022-10-26 19:33:46 seems when something fails with the go stuff every time there's makedeps left 2022-10-26 19:35:56 hold on 2022-10-26 19:35:59 yep 2022-10-26 19:35:59 going to bootstrap rust 2022-10-26 19:36:03 you can pause everything 2022-10-26 19:36:06 all ready for rust 2022-10-26 19:36:08 whatever didn't have it 2022-10-26 19:36:14 one at a time ofc :) 2022-10-26 19:37:39 working on x86_64 now 2022-10-26 19:39:23 algitbot: retry master 2022-10-26 19:43:52 algitbot: retry master 2022-10-26 19:46:20 algitbot: retry master 2022-10-26 19:48:05 algitbot: retry master 2022-10-26 19:51:03 algitbot: retry master 2022-10-26 20:14:33 algitbot: retry master 2022-10-26 20:43:38 algitbot: retry master 2022-10-26 20:48:57 going to do rust on s390x 2022-10-26 21:04:04 py3-astor: https://github.com/berkerpeksag/astor/issues/212 2022-10-26 21:06:34 no temporary dir found..? 2022-10-26 21:07:06 it checks pythons tempfile.gettempdir() and all the common paths 2022-10-26 21:07:52 maybe timeout? ls /tmp takes quite a bit of time 2022-10-26 21:08:08 /tmp does exist 2022-10-26 21:08:29 hmm 2022-10-26 21:08:34 no timing stuff 2022-10-26 21:08:36 algitbot: retry master 2022-10-26 21:09:48 ah 2022-10-26 21:09:53 https://tpaste.us/nVP9 2022-10-26 21:09:58 it opens proc/self/mountinfo 2022-10-26 21:10:06 reads stuff at specific [offset] 2022-10-26 21:10:12 i'd assume the endianness breaks something 2022-10-26 21:10:33 and the error is always 'no dir', so you get that 2022-10-26 21:10:57 reads the fstype from the mntinfo 2022-10-26 21:11:05 i guess the bytes are backwards in the table 2022-10-26 21:11:18 seems to be just ascii 2022-10-26 21:11:18 ah 2022-10-26 21:11:20 wait 2022-10-26 21:11:36 are all of /tmp /run/shm /dev/shm tmpfs/ramfs or not 2022-10-26 21:11:37 https://tpaste.us/zQY1 2022-10-26 21:11:38 check mount 2022-10-26 21:11:51 dev shm is 2022-10-26 21:12:10 nod 2022-10-26 21:12:32 hmmm 2022-10-26 21:12:39 really not sure if it's broken or not 2022-10-26 21:13:16 ah 2022-10-26 21:16:56 idk, [8] in that is tmpfs for /dev/shm 2022-10-26 21:16:56 hmm 2022-10-26 21:21:37 algitbot: retry master 2022-10-26 21:22:46 hm 2022-10-26 21:22:51 ok it's definitely not endianness 2022-10-26 21:22:54 i have no idea why it wouldn't find it 2022-10-26 21:25:02 that commit message is wrong :P 2022-10-26 21:25:33 lmao 2022-10-26 21:25:41 i accidentally amended 2022-10-26 21:26:04 heh, happens to me as well :D 2022-10-26 21:26:13 how did it not conflict or something 2022-10-26 21:26:15 hahaha 2022-10-26 21:27:11 what is that mutter-dev error on perl-cwd-guard 2022-10-26 21:28:19 hmm 2022-10-26 21:28:57 i assume some disk file issue 2022-10-26 21:29:21 apk manifest accepts the package 2022-10-26 21:29:51 apk verify as well 2022-10-26 21:30:18 mutter-dev-43.0-r0.apk: 0 - OK 2022-10-26 21:30:37 what's the : 0 normally 2022-10-26 21:31:18 seems like it outputs 0 for any package 2022-10-26 21:33:58 i guess it's apk index that fails 2022-10-26 21:34:12 if it passed it would print signing the index 2022-10-26 21:34:17 next line in abuild 2022-10-26 21:34:33 hm, can you send me that apk 2022-10-26 21:34:55 i'm still 98% sure it's just an error due to something truncated due to filespace write and failing 2022-10-26 21:34:59 but i wanna look at it anyway 2022-10-26 21:35:25 yeah, possibly 2022-10-26 21:37:44 too tired atm 2022-10-26 21:39:52 psykose: https://dev.alpinelinux.org/~kevin/mutter-dev-43.0-r0.apk 2022-10-26 21:40:14 thankies 2022-10-26 21:41:14 fails for me too if i copy it 2022-10-26 21:41:18 but extracting looks ok 2022-10-26 21:41:22 i guess there's a magic byte missing 2022-10-26 21:42:19 should I rebuild the package? 2022-10-26 21:43:02 yeah, should fix it 2022-10-26 21:43:13 if you just remove the mutter*.apk files i assume retry picks it up 2022-10-26 21:44:15 abuild -rf 2022-10-26 21:44:24 but might run into the same issue 2022-10-26 21:44:29 or maybe abuild cleanpkg 2022-10-26 21:46:21 I think cleanpkg fixed it 2022-10-26 21:48:58 hmm, no 2022-10-26 21:49:51 it's fine with the package removed, but even rebuild seems to cause issues 2022-10-26 21:50:59 hrm 2022-10-26 21:51:26 algitbot: retry master 2022-10-26 21:51:37 removed the package, started the builder again 2022-10-26 21:52:25 uhh 2022-10-26 21:52:28 building it locally gives that error 2022-10-26 21:52:37 wtf 2022-10-26 21:52:40 oof 2022-10-26 21:58:11 ok 2022-10-26 21:58:14 it's the new apk version 2022-10-26 21:58:18 building with .9 yields no error 2022-10-26 21:58:27 the diff between .9 and .10 isn't large, might be easy to find 2022-10-26 21:59:05 to the bisect machine 2022-10-26 22:16:22 a6126a6f2362ee47e91acb25083e1b112a57640a 2022-10-26 22:16:39 took me a while to realize it still uses system libapk when running as src/apk 2022-10-26 22:23:40 ` 2022-10-26 22:23:40 `depend = pc:gsettings-desktop-schemas>=40.alpha 2022-10-26 22:23:42 holy 2022-10-26 22:23:45 apk is actually right 2022-10-26 22:23:51 that depend is broken 2022-10-26 22:24:00 well, it's also absolute garbage in saying *what* is wrong 2022-10-26 22:24:14 to the point that you have to manually count the amount of lines in gdb :) 2022-10-26 22:24:25 s/lines/times a function was called/ 2022-10-26 22:24:31 but yeah 2022-10-26 22:24:32 abuild also generates it 2022-10-26 22:24:40 isn't the version wrong here? 2022-10-26 22:24:46 it's from meson 2022-10-26 22:24:49 meson translated dep to .pc 2022-10-26 22:24:51 the line is 2022-10-26 22:24:52 oh 2022-10-26 22:24:54 gsettings_desktop_schemas_req = '>= 40.alpha' 2022-10-26 22:24:59 and then in the .pc generation 2022-10-26 22:25:04 it outputs that into the .pc 2022-10-26 22:25:08 even though apk doesn't accept such versions 2022-10-26 22:25:19 and then apk just reads the generated meta file with that depend 2022-10-26 22:25:23 so the pkgconfig file specifies it and abuild adds that thing? 2022-10-26 22:25:30 ye 2022-10-26 22:25:36 cursed 2022-10-26 22:25:40 before that commit i assume it accepted this regardless 2022-10-26 22:25:47 hmm 2022-10-26 22:25:48 no 2022-10-26 22:25:52 ah 2022-10-26 22:25:53 no yeah 2022-10-26 22:25:57 apk doesn't accept these 2022-10-26 22:26:02 pkgconf does 2022-10-26 22:26:18 so.. do we have to fix that in abuild, so it doesn't put invalid versions from .pc files? 2022-10-26 22:26:22 the issue with that is it's going to break like 100 packages 2022-10-26 22:26:29 lots of builds do > something.alpha 2022-10-26 22:26:35 every single one will break like this 2022-10-26 22:26:37 it's the first time it happened though 2022-10-26 22:26:46 at the start of a community build with 4k to go sure 2022-10-26 22:26:47 so maybe if we fix it asap in abuild.. 2022-10-26 22:27:08 i can patch it in mutter for now 2022-10-26 22:28:48 hm no still fails 2022-10-26 22:28:58 ah 2022-10-26 22:28:59 didnt work 2022-10-26 22:30:07 qah 2022-10-26 22:30:09 it does 2022-10-26 22:30:12 weird 2022-10-26 22:30:18 weh 2022-10-26 22:30:19 oh well 2022-10-26 22:30:24 ptrc: make an issue somewhere i guess 2022-10-26 22:30:27 ty 2022-10-26 22:30:37 is it `grep gnome.org -l | grep .alpha` time 2022-10-26 22:30:40 nah 2022-10-26 22:30:44 it fails on end of build 2022-10-26 22:30:52 the moment anything builds with a broken .pc ver it will fail the build 2022-10-26 22:30:54 ah, okay 2022-10-26 22:30:59 even in ci i think? it does apk index there 2022-10-26 22:31:04 that's an abuild issue, right? 2022-10-26 22:31:09 sure 2022-10-26 22:31:16 though fixing it in abuild isn't very friendly 2022-10-26 22:31:19 how come 2022-10-26 22:31:36 because at the end of the day these versions aren't invalid 2022-10-26 22:31:41 pkgconf even compares them fine 2022-10-26 22:31:46 it would be better if apk could just support them 2022-10-26 22:32:03 doesn't apk follow some gentoo(?) version format where they are invalid? 2022-10-26 22:32:10 probably yes 2022-10-26 22:32:18 so yeah, abuild has to report it 2022-10-26 22:32:21 tsc issue to change alpine version format /s 2022-10-26 22:32:24 i think there is just no check for .pc's 2022-10-26 22:32:27 or something 2022-10-26 22:32:30 hm 2022-10-26 22:32:31 no, there is 2022-10-26 22:32:34 iirc 2022-10-26 22:32:40 when i make stuff with 40.alpha it fails 2022-10-26 22:32:45 so it checks the pkgver= 2022-10-26 22:32:50 but maybe not every line of a .pc 2022-10-26 22:32:55 go open an issue first 2022-10-26 22:34:00 algitbot: retry master 2022-10-26 22:34:46 https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10083 2022-10-26 22:34:50 feel free to bikeshed about wording 2022-10-26 22:42:47 ptrc: i think you should have used better words. 2022-10-26 22:43:10 it's always better to use the better words instead of the worse ones. 2022-10-26 22:43:10 the words i used were certainly some of the words ever used 2022-10-26 22:44:41 algitbot: retry master 2022-10-26 22:50:40 algitbot: retry master 2022-10-26 23:00:29 ikke: also you can put aarch64/s390x back now 2022-10-26 23:55:21 algitbot: retry 3.16-stable 2022-10-26 23:57:04 algitbot: retry 3.16-stable 2022-10-27 00:04:36 algitbot: retry master 2022-10-27 00:51:06 algitbot: retry master 2022-10-27 01:21:32 algitbot: retry master 2022-10-27 01:53:47 algitbot: retry master 2022-10-27 03:25:54 algitbot: retry master 2022-10-27 05:26:33 algitbot: retry master 2022-10-27 05:27:21 psykose: started both builders again 2022-10-27 05:27:39 :) 2022-10-27 11:28:23 algitbot: retry 3.16-stable 2022-10-27 13:35:33 algitbot: retry master 2022-10-27 13:38:21 algitbot: retry 3.16-stable 2022-10-27 14:24:30 ikke: can you check the 3.16-x86 builder? i'm not really sure why that rebuilt to begin with 2022-10-27 14:24:54 and the gcc version seems wrong 2022-10-27 14:26:31 algitbot: retry master 2022-10-27 14:27:38 algitbot: retry master 2022-10-27 14:45:08 algitbot: retry master 2022-10-27 14:58:28 algitbot: retry master 2022-10-27 15:02:02 psykose: do I still need to check 3-16-x86? 2022-10-27 15:02:09 yeah 2022-10-27 15:02:13 i fixed it but it seemed weird 2022-10-27 15:02:36 maybe the repos are wrong or something again 2022-10-27 15:19:44 algitbot: retry master 2022-10-27 16:08:07 algitbot: retry master 2022-10-27 16:19:09 algitbot: retry master 2022-10-27 17:09:18 psykose: don't see anything strange our out of place 2022-10-27 17:09:32 weird 2022-10-27 17:09:36 strange how it rebuilt at all 2022-10-27 17:09:39 something deleted the file 2022-10-27 17:09:48 and the errors were definitely caused by a different gcc version 2022-10-27 17:09:56 maybe it was just never built before for some reason during 3.16 bootstrap? 2022-10-27 17:10:01 would make sense 2022-10-27 17:10:07 it is something that would fail with gcc11 2022-10-27 17:28:47 algitbot: retry master 2022-10-27 17:48:52 algitbot: retry master 2022-10-27 18:05:42 algitbot: retry master 2022-10-27 18:15:59 algitbot: retry master 2022-10-27 18:28:10 algitbot: retry master 2022-10-27 19:26:00 algitbot: retry master 2022-10-27 19:29:21 ikke: is edge-ppc missing the distfiles mirror 2022-10-27 19:29:25 doesn't look like it tries to fetch it 2022-10-27 19:51:20 psykose: correct 2022-10-27 19:51:44 algitbot: retry master 2022-10-27 21:26:27 algitbot: retry master 2022-10-27 22:41:05 algitbot: retry master 2022-10-27 22:47:17 algitbot: retry master 2022-10-27 23:23:33 algitbot: retry master 2022-10-28 15:47:21 ahuh 'fix test' :P 2022-10-28 15:49:10 :) 2022-10-28 15:49:25 lots of those 2022-10-28 15:51:13 ikke: you should restart aarch64-edge as it's stuck and there was the openjdk fixes 2022-10-28 15:51:47 psykose: it looks like py3-defcon dependency missing 2022-10-28 15:52:00 not the issue 2022-10-28 15:52:13 that's a skipped test 2022-10-28 15:52:16 algitbot: retry master 2022-10-28 16:18:56 algitbot: retry master 2022-10-28 17:10:12 algitbot: retry master 2022-10-28 17:26:35 algitbot: retry master 2022-10-28 17:45:38 algitbot: retry master 2022-10-28 18:09:08 algitbot: retry master 2022-10-28 18:16:07 algitbot: retry master 2022-10-28 18:24:52 hmm, 12 year old post: https://www.linuxquestions.org/questions/slackware-14/xf86-video-vmware-doesn%27t-built-in-current-4175715331/ 2022-10-28 18:25:19 has -Werror=address been recently enabled? 2022-10-28 18:32:17 gcc12 change 2022-10-28 18:32:23 more checks and stuff 2022-10-28 18:32:58 (they add werror=address, it became more strict) 2022-10-28 18:34:58 openjdk still funny there 2022-10-28 19:13:26 algitbot: retry master 2022-10-28 19:18:14 ikke: 3.17 s390x telepathy-glib looks stuck 2022-10-28 19:18:38 same for armhf i guess 2022-10-28 19:19:32 hanging on make check doing a lot of nothing 2022-10-28 19:20:53 yep 2022-10-28 19:22:10 ah 2022-10-28 19:22:12 have to build ghc 2022-10-28 19:25:20 algitbot: retry master 2022-10-28 19:28:31 algitbot: retry master 2022-10-28 21:44:25 algitbot: retry master 2022-10-28 22:07:49 ikke: edge-ppc and 3.17-x86_64 are stuck 2022-10-28 22:08:00 algitbot: retry master 2022-10-29 00:10:25 algitbot: retry master 2022-10-29 00:32:35 algitbot: retry master 2022-10-29 02:56:44 algitbot: retry master 2022-10-29 04:44:33 algitbot: retry master 2022-10-29 04:44:54 algitbot: retry master 2022-10-29 05:57:20 algitbot: retry master 2022-10-29 09:08:59 algitbot: retry master 2022-10-29 15:08:55 ikke: fyi 3.17 x86_64/s390x/ppc64le edge ppc64le are stuck for over 12 hours 2022-10-29 15:10:54 Will look at it when I'm back homw 2022-10-29 15:20:45 algitbot: retry master 2022-10-29 15:31:04 algitbot: retry master 2022-10-29 17:21:20 algitbot: retry master 2022-10-29 20:30:25 drivers/platform/x86/amd/pmc.c:640:22: error: implicit declaration of function 'amd_pmc_get_smu_version' [-Werror=implicit-function-declaration] 2022-10-29 20:32:52 https://lore.kernel.org/all/20210916124002.2529-1-Sanket.Goswami@amd.com/ 2022-10-29 20:32:54 mps: ^ 2022-10-29 20:35:19 oh, that's the original patch, follow-up is someone reporting the error 2022-10-29 20:43:57 uh 2022-10-29 20:44:26 I knew that the patches in kernels are bad idea 2022-10-29 20:45:42 that's not a patch? 2022-10-29 20:46:00 it's just part of 6.0.6 2022-10-29 20:46:10 ahh 2022-10-29 20:46:13 I see 2022-10-29 20:48:10 ACTION don't work anything when you are tired 2022-10-29 20:55:55 trying to build with reverted patch on lxc, if succeed will push fix 2022-10-29 21:04:15 i don't think reverting it is correct 2022-10-29 21:06:33 if it pass builder it is 'correct' 2022-10-29 21:08:09 ACTION is not gkh to fix everything in kernel 2022-10-29 21:13:12 algitbot: retry master 2022-10-29 21:28:23 algitbot: retry master 2022-10-29 21:29:05 hmm, it doesn't work 2022-10-29 21:29:15 ikke: ^ 2022-10-29 21:29:37 mps: it doesn't restart running jobs 2022-10-29 21:30:14 and not failed? 2022-10-29 21:30:28 mps: x86_64 is currently building 2022-10-29 21:31:10 I see, but it stays on failed linux-edge, not really building 2022-10-29 21:31:40 It just mentioned the last package that failed 2022-10-29 21:31:48 But it also shows it's currently building the same package 2022-10-29 21:32:04 aha, ok 2022-10-29 21:32:10 lets see 2022-10-29 21:32:42 If you pushed a commit, you don't need to manually restart the builders 2022-10-29 21:33:30 I thought so, but had impression it didn't restarted 2022-10-29 21:36:00 ahem, finished. sorry for annoyance ikke 2022-10-29 21:36:06 no worry 2022-10-29 22:26:55 ikke: still have to kick the stuck builders 2022-10-29 23:16:57 also java-jna and stunnel 2022-10-29 23:53:18 algitbot: retry master 2022-10-29 23:58:42 ikke: there was stunnel and java-jna stuck too :) 2022-10-30 01:54:07 algitbot: retry master 2022-10-30 02:51:40 algitbot: retry master 2022-10-30 02:56:02 algitbot: retry master 2022-10-30 07:34:01 algitbot: retry master 2022-10-30 11:49:17 hmm, strange that s390x randomly keeps rebuilding py3-pyldap 2022-10-30 11:52:46 Seems like 3.17/armv7 is finished 2022-10-30 13:27:55 bootstrapping ghc on x86_64 2022-10-30 16:23:52 algitbot: retry master 2022-10-30 16:43:02 algitbot: retry master 2022-10-30 18:21:32 huh, is py3-pendulum a DST offset bug? 2022-10-30 18:43:31 it fails at random times of day 2022-10-30 18:45:53 fun 2022-10-30 19:11:34 algitbot: retry master 2022-10-31 00:21:38 algitbot: retry master 2022-10-31 04:37:35 algitbot: retry master 2022-10-31 17:36:32 algitbot: retry master 2022-10-31 17:45:35 algitbot: retry master 2022-10-31 17:53:30 algitbot: retry master 2022-10-31 18:47:14 algitbot: retry master 2022-10-31 20:58:44 algitbot: retry master