2024-03-01 20:12:41 <ikke> algitbot: retry master
2024-03-01 20:16:12 <nmeum> puhh, hopefully that test is just racy
2024-03-01 20:16:37 <nmeum> the 1.22 release has really had a suprising number of regressions on different architectures so far
2024-03-01 20:24:11 <ikke> algitbot: retry master
2024-03-01 20:28:10 <ikke> algitbot: retry master
2024-03-01 20:33:11 <ikke> so now hare is the only thing left
2024-03-01 20:33:15 <ikke> algitbot: retry master
2024-03-01 20:38:22 <nmeum> algitbot: retry master
2024-03-01 23:13:41 <andypost[m]> algitbot: retry master
2024-03-02 00:27:16 <andypost[m]> algitbot: retry master
2024-03-02 02:05:23 <andypost[m]> algitbot: retry master
2024-03-02 02:06:44 <andypost[m]> algitbot: retry master
2024-03-02 04:06:33 <andypost[m]> algitbot: retry master
2024-03-02 04:35:36 <ptrc> ikke: could you check for any leftover packages on the builders? the nomacs build process seems to install a lot of unrelated stuff on x86_64 for some reason
2024-03-02 04:36:22 <ptrc> for example, tiledb
2024-03-02 04:37:42 <ptrc> https://tpaste.us/b1LD
2024-03-02 04:37:46 <ptrc> here's a diff between x86_64 and armv7
2024-03-02 04:37:55 <ptrc> and i feel like aws-cpp or google-cloud-cpp should *not* be there
2024-03-02 04:42:16 <ptrc> nevermind, went through the graph and somehow this dependency hell makes sense...
2024-03-02 05:03:29 <celie> algitbot: retry master
2024-03-02 06:44:17 <celie> algitbot: retry master
2024-03-02 07:27:03 <ikke> oauth2-proxy has CGO_ENABLED=0 in the Makefile
2024-03-02 07:41:47 <ikke> !61551
2024-03-02 12:08:38 <celie> algitbot: retry master
2024-03-02 14:32:51 <ikke> algitbot: retry master
2024-03-02 17:16:54 <andypost[m]> algitbot: retry master
2024-03-03 01:06:07 <ptrc> algitbot: retry master
2024-03-03 02:04:40 <celie> algitbot: retry master
2024-03-03 02:06:22 <celie> algitbot: retry master
2024-03-03 03:35:12 <celie> algitbot: retry master
2024-03-03 03:36:23 <celie> algitbot: retry master
2024-03-03 06:56:00 <celie> algitbot: retry master
2024-03-03 06:57:45 <celie> algitbot: retry master
2024-03-03 06:58:34 <celie> algitbot: retry master
2024-03-03 07:01:29 <celie> algitbot: retry master
2024-03-03 07:02:47 <celie> algitbot: retry master
2024-03-03 07:03:45 <celie> algitbot: retry master
2024-03-03 07:18:12 <ikke> 🎉
2024-03-03 07:18:18 <ikke> w00t
2024-03-03 12:41:43 <PureTryOut> algitbot: retry master
2024-03-03 13:17:41 <PureTryOut> algitbot: retry master
2024-03-03 13:51:07 <PureTryOut> algitbot: retry master
2024-03-03 14:22:44 <PureTryOut> algitbot: retry master
2024-03-03 15:48:29 <PureTryOut> algitbot: retry master
2024-03-03 16:06:26 <PureTryOut> algitbot: retry master
2024-03-03 16:27:02 <PureTryOut> algitbot: retry master
2024-03-03 17:02:19 <PureTryOut> algitbot: retry master
2024-03-03 17:13:18 <PureTryOut> algitbot: retry master
2024-03-03 18:11:18 <PureTryOut> what...
2024-03-03 18:11:34 <ptrc> the pkgname is gone apparently 
2024-03-03 18:11:48 <PureTryOut> yeah how the hell lol
2024-03-03 18:20:51 <PureTryOut> algitbot: retry master
2024-03-03 18:32:45 <andypost[m]> algitbot: retry master
2024-03-03 18:35:08 <ptrc> PureTryOut: there's a lot of stuff on armv7 that won't build because there's no qt6-qtwebengine
2024-03-03 18:35:13 <ptrc> and i mean like, 30+ packages
2024-03-03 18:35:26 <PureTryOut> yeah I know 😢
2024-03-03 18:35:45 <ptrc> may i disable them, or would there be a chance to get qt6-qtwebengine there?
2024-03-03 18:36:59 <PureTryOut> you can disable them
2024-03-03 18:37:08 <PureTryOut> we'll probably get webengine there at some point, but not now
2024-03-03 18:39:21 <ptrc> alrighty
2024-03-03 18:47:18 <ptrc> okay i didn't deduplicate my list, it should be only 14 of them
2024-03-03 18:50:54 <clandmeter> i think i will need to wait a while for my kernel build?
2024-03-03 18:51:30 <ptrc> poor khelpcenter :/
2024-03-03 18:52:04 <ptrc> algitbot: retry master
2024-03-03 18:54:37 <andypost[m]> algitbot: retry master
2024-03-03 18:57:29 <ptrc> PureTryOut: btw why did the commit switching KDE to qt6 remove poppler-qt5?
2024-03-03 18:57:35 <ptrc> we have other non-kde aports depending on it
2024-03-03 18:57:41 <ptrc> that are will now be brokem
2024-03-03 18:57:43 <ptrc> broken*
2024-03-03 18:58:04 <PureTryOut> because I did not realize that 😛 Will re-add it
2024-03-03 18:58:08 <PureTryOut> algitbot: retry master
2024-03-03 19:00:29 <PureTryOut> oh actually removing that was a mistake entirely, it's not even a KDE package
2024-03-03 19:00:38 <PureTryOut> wildcard messed up there
2024-03-03 19:02:09 <andypost[m]> algitbot: retry master
2024-03-03 19:05:46 <PureTryOut> aarch64 is getting close now
2024-03-03 19:07:04 <andypost[m]> algitbot: retry master
2024-03-03 19:10:32 <ptrc> PureTryOut: same thing with networkmanager-qt5 btw
2024-03-03 19:10:35 <ptrc> we have nm-tray in testing
2024-03-03 19:11:16 <PureTryOut> ugh
2024-03-03 19:11:19 <ptrc> algitbot: retry master
2024-03-03 19:16:24 <PureTryOut> algitbot: retry master
2024-03-03 19:39:50 <PureTryOut> algitbot: retry master
2024-03-03 20:16:11 <PureTryOut> algitbot: retry master
2024-03-03 20:21:11 <andypost[m]> algitbot: retry master
2024-03-03 20:41:56 <ptrc> slightly wondering how many of those skipped/disabled tests are actual failures that we'll see in the following days
2024-03-03 20:43:34 <PureTryOut> a bunch probably
2024-03-03 21:32:44 <andypost[m]> algitbot: retry master
2024-03-03 22:09:14 <PureTryOut> algitbot: retry master
2024-03-04 02:11:53 <clandmeter> algitbot: retry master
2024-03-04 02:25:08 <celie> algitbot: retry master
2024-03-04 02:27:14 <celie> algitbot: retry master
2024-03-04 02:28:31 <celie> algitbot: retry master
2024-03-04 02:31:20 <celie> algitbot: retry master
2024-03-04 02:31:29 <celie> algitbot: retry master
2024-03-04 02:34:45 <celie> algitbot: retry master
2024-03-04 02:36:19 <celie> algitbot: retry master
2024-03-04 02:38:05 <celie> algitbot: retry master
2024-03-04 02:39:14 <celie> algitbot: retry master
2024-03-04 02:41:17 <celie> algitbot: retry master
2024-03-04 02:44:00 <celie> algitbot: retry master
2024-03-04 02:45:10 <celie> algitbot: retry master
2024-03-04 02:46:32 <celie> algitbot: retry master
2024-03-04 02:47:46 <celie> algitbot: retry master
2024-03-04 02:49:09 <celie> algitbot: retry master
2024-03-04 02:50:35 <celie> algitbot: retry master
2024-03-04 02:51:49 <celie> algitbot: retry master
2024-03-04 02:55:24 <celie> algitbot: retry master
2024-03-04 02:56:48 <celie> algitbot: retry master
2024-03-04 03:02:10 <celie> algitbot: retry master
2024-03-04 03:06:34 <celie> algitbot: retry master
2024-03-04 03:08:45 <celie> algitbot: retry master
2024-03-04 08:45:20 <PureTryOut> algitbot: retry master
2024-03-04 08:48:10 <PureTryOut> algitbot: retry master
2024-03-04 09:26:31 <PureTryOut> algitbot: retry master
2024-03-04 10:34:32 <andypost[m]> algitbot: retry master
2024-03-04 12:11:23 <andypost[m]> algitbot: retry master
2024-03-04 12:13:07 <andypost[m]> algitbot: retry master
2024-03-04 12:15:55 <andypost[m]> algitbot: retry master
2024-03-04 12:17:00 <andypost[m]> algitbot: retry master
2024-03-04 12:20:10 <andypost[m]> algitbot: retry master
2024-03-04 12:23:39 <andypost[m]> algitbot: retry master
2024-03-04 12:36:55 <andypost[m]> algitbot: retry master
2024-03-04 14:53:43 <andypost[m]> algitbot: retry master
2024-03-04 16:05:18 <iggy> looking at all this kde6 stuff in here, I think I picked a bad time to upgrade one of my edge systems
2024-03-04 17:44:29 <PureTryOut> currently it's just x86 and armv7 left, it's not that bad
2024-03-04 17:46:41 <iggy> most of the system settings (kcm stuff) isn't showing up
2024-03-04 19:26:34 <andypost[m]> algitbot: retry master
2024-03-04 21:55:56 <andypost[m]> algitbot: retry master
2024-03-04 22:08:46 <andypost[m]> algitbot: retry master
2024-03-04 23:48:45 <andypost[m]> algitbot: retry master
2024-03-04 23:49:43 <andypost[m]> algitbot: retry master
2024-03-05 00:06:13 <andypost[m]> algitbot: retry master
2024-03-05 00:07:26 <andypost[m]> algitbot: retry master
2024-03-05 00:20:50 <andypost[m]> algitbot: retry master
2024-03-05 00:27:56 <andypost[m]> algitbot: retry master
2024-03-05 00:32:51 <andypost[m]> algitbot: retry master
2024-03-05 00:47:32 <andypost[m]> algitbot: retry master
2024-03-05 00:49:46 <andypost[m]> algitbot: retry master
2024-03-05 00:52:50 <andypost[m]> algitbot: retry master
2024-03-05 00:57:18 <andypost[m]> algitbot: retry master
2024-03-05 03:06:37 <celie> algitbot: retry master
2024-03-05 03:07:42 <celie> algitbot: retry master
2024-03-05 03:08:07 <celie> algitbot: retry master
2024-03-05 03:09:50 <celie> algitbot: retry master
2024-03-05 03:10:08 <celie> algitbot: retry master
2024-03-05 03:11:51 <celie> algitbot: retry master
2024-03-05 03:12:36 <celie> algitbot: retry master
2024-03-05 03:14:19 <celie> algitbot: retry master
2024-03-05 03:15:29 <celie> algitbot: retry master
2024-03-05 03:17:01 <celie> algitbot: retry master
2024-03-05 03:18:24 <celie> algitbot: retry master
2024-03-05 03:20:44 <celie> algitbot: retry master
2024-03-05 03:22:49 <celie> algitbot: retry master
2024-03-05 03:26:04 <celie> algitbot: retry master
2024-03-05 03:27:57 <celie> algitbot: retry master
2024-03-05 03:29:29 <celie> algitbot: retry master
2024-03-05 03:31:40 <celie> algitbot: retry master
2024-03-05 03:32:33 <celie> algitbot: retry master
2024-03-05 03:34:08 <celie> algitbot: retry master
2024-03-05 03:36:30 <celie> algitbot: retry master
2024-03-06 16:05:34 <nmeum> rebuild time 🚀
2024-03-06 16:37:31 <ikke> Does that check just failed because a year pased? about 2 years ago vs about 3 years ago?
2024-03-06 16:51:17 <nmeum> ikke: yea looks like it :D
2024-03-06 18:00:57 <ikke> https://github.com/cli/cli/issues/8452
2024-03-06 18:08:47 <ikke> hmm, there is another test that fails
2024-03-06 18:09:12 <ikke> json control characters, that's due to a golang change
2024-03-06 18:09:38 <ikke> yeah, that one was fixed in edge
2024-03-06 20:08:50 <ikke> algitbot: retry master
2024-03-06 22:06:27 <ptrc> algitbot: retry master
2024-03-06 22:06:36 <ptrc> why does it try to build calendarsupport before akonadi?? i don't get it
2024-03-06 22:07:17 <ikke> no loop?
2024-03-06 22:07:28 <ptrc> not as far as i can check
2024-03-06 22:07:43 <ikke> or is the dependency declared in a subpackage?
2024-03-06 22:08:30 <ptrc> it's a depends_dev
2024-03-06 22:08:36 <ptrc> then put in makedepends
2024-03-06 22:08:44 <ptrc> so it should get picked up as usual
2024-03-06 22:09:57 <ptrc> algitbot: retry master
2024-03-06 22:12:27 <ikke> according to ap builddirs, akonadi should be built before calendarsupport
2024-03-06 22:12:36 <ptrc> and yet
2024-03-06 22:25:25 <ptrc> algitbot: retry master
2024-03-06 22:41:41 <omni> algitbot: retry master
2024-03-06 22:43:51 <omni> dammit
2024-03-06 22:49:27 <omni> algitbot: retry master
2024-03-06 22:50:21 <omni> w00t! \o/
2024-03-06 23:42:46 <omni> algitbot: retry 3.19-stable
2024-03-07 05:56:25 <celie> algitbot: retry master
2024-03-07 05:58:30 <celie> algitbot: retry master
2024-03-07 06:00:05 <celie> algitbot: retry master
2024-03-07 15:50:39 <ikke> algitbot: retry master
2024-03-08 02:02:51 <ptrc> algitbot: retry master
2024-03-08 02:31:08 <ptrc> algitbot: retry master
2024-03-08 08:09:09 <celie> algitbot: retry master
2024-03-08 08:10:38 <celie> algitbot: retry master
2024-03-08 08:11:56 <celie> algitbot: retry master
2024-03-08 08:12:54 <celie> algitbot: retry master
2024-03-08 08:13:35 <celie> algitbot: retry master
2024-03-08 14:57:50 <andypost[m]> algitbot: retry master
2024-03-08 16:30:42 <ptrc> algitbot: retry master
2024-03-08 18:04:01 <ptrc> algitbot: retry master
2024-03-08 22:29:57 <ptrc> algitbot: retry master
2024-03-08 23:51:56 <andypost[m]> algitbot: retry master
2024-03-09 00:00:12 <andypost[m]> algitbot: retry master
2024-03-09 00:34:24 <ptrc> oh you've gotta be kidding me
2024-03-09 00:34:33 <ptrc> ikke: any chance of getting the coredump from that?
2024-03-09 05:12:22 <celie> algitbot: retry master
2024-03-09 05:17:21 <celie> algitbot: retry master
2024-03-09 14:00:30 <celie> algitbot: retry master
2024-03-09 15:40:51 <celie> algitbot: retry master
2024-03-09 16:40:47 <ikke> algitbot: retry master
2024-03-09 17:36:45 <ikke> ptrc: still need a coredump?
2024-03-09 18:50:07 <ptrc> ikke: not anymore, since it built correctly :)
2024-03-09 19:02:13 <ikke> ok, good
2024-03-09 19:02:24 <ikke> I had a suspicion
2024-03-09 23:48:06 <omni> algitbot: retry master
2024-03-10 14:25:01 <cely> algitbot: retry master
2024-03-10 14:26:33 <cely> algitbot: retry master
2024-03-10 14:27:59 <cely> algitbot: retry master
2024-03-10 15:23:21 <celie> For ktistec, looks like the slang repository was modified about an hour ago, maybe that's causing it to fail
2024-03-10 15:23:24 <celie> algitbot: retry master
2024-03-10 15:24:08 <celie> but i am going AFK, so won't be around to look deeper into that unfortunately
2024-03-10 15:24:25 <celie> algitbot: retry master
2024-03-10 15:25:29 <celie> I guess this means disabling ktistec would be the best way forward until i find some time in a few days' time
2024-03-10 15:25:29 <celie> algitbot: retry master
2024-03-10 15:41:07 <ikke> celie: ok, I'll disable it for now
2024-03-10 19:09:28 <ptrc> ~50 down, 20 more to go
2024-03-10 19:10:22 <ptrc> that should fix another 4
2024-03-10 19:56:47 <ptrc> algitbot: retry master
2024-03-10 20:07:12 <ptrc> algitbot: retry master
2024-03-10 20:15:53 <ptrc> ikke: uhhh could you check why x86 isn't picking the correct version of libaccounts-qt for kaccounts-integration?
2024-03-10 20:16:27 <ptrc> the _git version should be picked instead of the 1.16-r3, and i can see on buildlogs that it's been built on x86
2024-03-10 20:16:36 <ikke> AccountsQt6 (required version >= 1.16),
2024-03-10 20:17:01 <ikke> let me check
2024-03-10 20:17:11 <ptrc> yeah, the 1.16-r3 is qt5
2024-03-10 20:17:29 <ikke> at least no spurious makedepends left
2024-03-10 20:18:05 <ikke> https://tpaste.us/4anX 
2024-03-10 20:18:28 <ikke> _git is older than without
2024-03-10 20:19:23 <ptrc> that's.. weird
2024-03-10 20:19:24 <ikke> I think the 'old' packages are only purged at the end
2024-03-10 20:19:35 <ptrc> $ apk version -t 1.16-r3 1.16_git20231124-r0
2024-03-10 20:19:37 <ptrc> M
2024-03-10 20:19:39 <ptrc> err
2024-03-10 20:19:39 <ptrc> <
2024-03-10 20:19:56 <ptrc> so _git should be treated by apk as newer
2024-03-10 20:20:15 <ptrc> it's a post prefix in the code as well
2024-03-10 20:20:17 <ikke> yeah
2024-03-10 20:20:21 <ikke> you're right
2024-03-10 20:22:42 <ikke> https://tpaste.us/MRrP 
2024-03-10 20:22:47 <ikke> If I force the _git version to be installed
2024-03-10 20:23:38 <ikke> Something with signon 
2024-03-10 20:23:47 <ptrc> ah
2024-03-10 20:24:04 <ptrc> okay, yeah, makes sense
2024-03-10 20:24:05 <ptrc> found out why
2024-03-10 21:53:16 <ptrc> wait no it doesn't make sense
2024-03-10 21:58:00 <ptrc> signon-ui should not affect libaccounts-qt, unless it's installed and left on the builders for some reason
2024-03-10 22:01:04 <ikke> no, it tries to install it when installing the deps
2024-03-10 22:03:02 <ptrc> hm, hold on, lemme look through the dep tree again
2024-03-10 22:03:53 <ptrc> ohhhh
2024-03-10 22:04:05 <ptrc> signon-ui was built against older version of libaccounts-qt on x86..?
2024-03-10 22:04:53 <ptrc> *is*
2024-03-10 22:05:01 <ptrc> because the new version doesn't seem to be built
2024-03-10 22:05:11 <ptrc> because it's disabled
2024-03-10 22:05:12 <ptrc> oh god
2024-03-10 22:07:52 <ptrc> ok let's try that
2024-03-10 22:08:42 <ptrc> algitbot: retry master
2024-03-10 22:12:30 <ptrc> a
2024-03-10 22:12:31 <ptrc> algitbot: retry master
2024-03-10 22:21:09 <ptrc> ikke: would you be able to get the backtrace for the tests of either plasma-desktop or the libkcddb?
2024-03-10 22:21:13 <andypost[m]> algitbot: retry master
2024-03-10 22:24:09 <ptrc> actually
2024-03-10 22:24:16 <ptrc> i could just disable them so community/* uploads
2024-03-10 22:58:34 <andypost[m]> ptrc: maybe armv7 needs the same?
2024-03-10 22:58:39 <ptrc> probably, yeah
2024-03-10 22:59:05 <ptrc> i'm hoping that once x86 uploads, i can try building it locally with all the dependencies
2024-03-10 22:59:12 <ptrc> and then debug what instruction it fails on
2024-03-10 22:59:26 <ptrc> 🎉
2024-03-10 23:00:44 <ptrc> now just a matter of waiting for the mirrors to update
2024-03-11 00:11:32 <ptrc> fingers crossed!
2024-03-11 00:17:04 <ptrc> algitbot: retry master
2024-03-11 00:29:59 <ptrc> okay, so that somehow didn't quite work on armv7
2024-03-11 00:30:11 <ptrc> wait, no, it still gets the old kio
2024-03-11 00:30:24 <ptrc> .
2024-03-11 00:32:07 <ptrc> ;_;
2024-03-11 00:32:27 <ptrc> dealing with this kde bullshit has aged me 20 years in a single week
2024-03-11 00:35:33 <ptrc> >>> plasma-desktop: Updating the community/armv7 repository index...
2024-03-11 00:35:34 <ptrc> !!
2024-03-11 02:40:29 <celie> algitbot: retry master
2024-03-11 02:41:40 <celie> I think plasma-desktop-meta needs to be disabled, so the new index can be uploaded
2024-03-11 02:44:37 <celie> Oh wait, that wouldn't mean it cannot be re-enabled, because kdeplasma-addons is now disabled on armv7
2024-03-11 02:44:56 <celie> s/wouldn't/would/
2024-03-11 02:49:08 <celie> (i was thinking plasma-desktop-meta could be re-enabled like x86, but x86 still has kdeplasma-addons)
2024-03-11 02:52:00 <ptrc> it can't be re-enabled anyway unless we get the kde-flavoured chromium to build on armv7
2024-03-11 02:52:16 <ptrc> but if we do, we can revert most of the "disable on armv7" commits that happened right after the update
2024-03-11 02:53:14 <ptrc> ah
2024-03-11 02:53:23 <ptrc> !61931 seems to have built on armv7!
2024-03-11 02:57:04 <celie> So, after this, re-enable kdeplasma-addons, then plasma-desktop-meta should finally build successfully?
2024-03-11 02:57:15 <ptrc> kdeplasma-addons, and probably a few other things
2024-03-11 02:58:03 <ptrc> kaccounts-integration, for purpose5
2024-03-11 02:58:51 <ptrc> aaand signon-ui
2024-03-11 02:59:00 <ptrc> and that should be all to get plasma-desktop built, i think? :)
2024-03-11 03:00:14 <ptrc> still need to boot up an armv7 device to check if the patched qt6-qtwebengine actually runs properly
2024-03-11 03:00:32 <celie> Hasn't plasma-desktop already been built for armv7?
2024-03-11 03:00:48 <celie> plasma-desktop 6.0.0, that is
2024-03-11 03:01:19 <ptrc> err, yes
2024-03-11 03:01:43 <celie> Were you thinking about plasma-desktop-meta but typed plasma-desktop?
2024-03-11 03:02:06 <ptrc> i thought that plasma-desktop itself depended on something currently disabled
2024-03-11 03:02:10 <ptrc> but no, it's just the -meta
2024-03-11 03:02:30 <ptrc> plasma-desktop built on armv7 today around 00:30 CET
2024-03-11 03:02:57 <celie> -meta is failing due to kdeplasma-addons being disabled (and so it installs the old one with conflicting files), right?
2024-03-11 03:03:43 <ptrc> yeah, not even sure why some qml stuff under "usr/share/kwin" was owned by the old kdeplasma-addons
2024-03-11 03:03:59 <ptrc> was moved to kwin in 6.0
2024-03-11 03:04:11 <ptrc> and so now they conflict
2024-03-11 03:07:44 <celie> That might have something to do with "Thumbnail Grid" being the new default Task Switcher style (from https://kde.org/announcements/megarelease/6/), maybe it was an addon before that
2024-03-11 03:11:16 <celie> https://invent.kde.org/plasma/kwin/-/merge_requests/4074 ("grabs Thumbnail Grid verbatim from where it currently lives in kdeplasma-addons-repo")
2024-03-11 03:12:11 <celie> So, that's probably the reason the files switched packages
2024-03-11 03:15:11 <ptrc> huh! nice find
2024-03-11 03:15:40 <ptrc> that makes sense
2024-03-11 03:31:34 <celie> Ok, qt6-qtwebengine is done
2024-03-11 03:48:28 <ptrc> oh, went afk and didn't notice
2024-03-11 03:50:56 <celie> xvfb failed to start
2024-03-11 03:51:03 <celie> I wonder if it needs -a again
2024-03-11 03:51:45 <celie> algitbot: retry master
2024-03-11 03:54:02 <celie> algitbot: retry master
2024-03-11 04:16:18 <ptrc> sigh
2024-03-11 04:16:19 <ptrc> yeah
2024-03-11 04:20:18 <celie> Yay, armv7/community is now uploading
2024-03-11 04:20:45 <ptrc> !!
2024-03-11 04:20:48 <ptrc> 🎉
2024-03-11 04:21:09 <ptrc> now the only things left are basically:
2024-03-11 04:21:19 <ptrc> - enabling.. most of kde that was disabled previously
2024-03-11 04:21:27 <ptrc> on armv7 and partially x86
2024-03-11 04:21:40 <ptrc> - fixing the missing packages
2024-03-11 04:22:49 <celie> Yeah, i saw #15859 you opened
2024-03-11 06:03:13 <ikke> ptrc: thank you do much taking care of this mess
2024-03-11 09:12:29 <ptrc> ikke: you're welcome ^^ it's been one hell of a journey so far, but highly rewarding to see all the pieces slowly fall back into place
2024-03-11 09:13:33 <ptrc> especially with the kio SIGILL stuff
2024-03-11 09:50:14 <nmeum> rebuild time
2024-03-11 09:50:22 <nmeum> will do testing after the community rebuild completed
2024-03-11 09:55:55 <celie> I am not sure if the old version of Tootik builds with Go 1.22, but if there is any problem with that, i have !61878
2024-03-11 10:00:09 <nmeum> there is probably a lot of stuff that doesn't build with Go 1.22
2024-03-11 10:00:40 <celie> As for community, i wonder if Go 1.22.1 solves the Ginkgo ppc64le issue mentioned in !61262 (discovered when Buildah's Makefile tried building its own Ginkgo)
2024-03-11 12:39:17 <PureTryOut> algitbot: retry master
2024-03-11 13:14:15 <celie> algitbot: retry master
2024-03-11 13:26:51 <celie> algitbot: retry master
2024-03-11 13:27:46 <celie> Seems libkscreen also needs xvfb -a
2024-03-11 13:28:02 <ptrc> yup :p
2024-03-11 13:32:13 <celie> algitbot: retry master
2024-03-11 13:32:36 <celie> algitbot: retry master
2024-03-11 13:33:32 <celie> Tailscale test failure is likely addressed in !61036
2024-03-11 13:34:14 <celie> algitbot: retry master
2024-03-11 13:39:58 <celie> lego CGO_ENABLED=0 is removed in !61147
2024-03-11 13:40:43 <celie> It was requested that lego be excluded from the larger community/ CGO_ENABLED=0 MR
2024-03-11 13:42:13 <celie> (that request was made in #alpine-devel last month)
2024-03-11 13:52:38 <celie> algitbot: retry master
2024-03-11 13:54:07 <celie> Ah, switching abuild-fetch from curl to busybox wget is flushing out all those prometheus-*-exporter Makefiles that want to download their own prebuilt binary
2024-03-11 14:01:42 <celie> algitbot: retry master
2024-03-11 14:02:32 <celie> algitbot: retry master
2024-03-11 14:07:16 <celie> algitbot: retry master
2024-03-11 15:21:21 <celie> algitbot: retry master
2024-03-11 16:34:57 <andypost[m]> algitbot: retry master
2024-03-11 16:40:41 <andypost[m]> algitbot: retry master
2024-03-11 17:46:13 <andypost[m]> algitbot: retry master
2024-03-11 17:47:12 <andypost[m]> algitbot: retry master
2024-03-11 17:48:37 <andypost[m]> algitbot: retry master
2024-03-11 17:53:06 <andypost[m]> algitbot: retry master
2024-03-11 18:23:24 <omni> I assume there are a lot of CGO_ENABLED being set to something in upstream build scripts
2024-03-11 18:23:35 <omni> I'll have a look at nebula to start with
2024-03-11 18:31:23 <omni> maybe that's not what's going on with nebula, but I'll try
2024-03-11 19:30:32 <ikke> omni: explicitly CGO_ENABLED=0
2024-03-11 19:30:46 <ikke> which breaks on some earches now in combination with -buildmode=pie
2024-03-11 22:43:34 <omni> I'm sorry, I got too distracted by other things to look properly at this and I don't think I will right now
2024-03-12 01:13:09 <celie> algitbot: retry master
2024-03-12 02:46:47 <andypost[m]> algitbot: retry master
2024-03-12 02:48:45 <andypost[m]> algitbot: retry master
2024-03-12 02:54:03 <andypost[m]> algitbot: retry master
2024-03-12 03:04:57 <celie> lego !61147, kubernetes on x86 !61975
2024-03-12 03:05:40 <celie> Maybe i should create another MR with the kubernetes fix but without the upgrade?
2024-03-12 03:13:26 <andypost[m]> I think it's bugfix release so it's fine to merge
2024-03-12 03:15:35 <andypost[m]> algitbot: retry master
2024-03-12 03:16:01 <andypost[m]> algitbot: retry master
2024-03-12 03:16:26 <andypost[m]> algitbot: retry master
2024-03-12 03:21:38 <ptrc> algitbot: retry master
2024-03-12 03:23:34 <celie> Thanks, so that's 2 more Go aports taken care of
2024-03-12 03:24:17 <ptrc> have you had a chance to take a look at the prometheus-postgres-exporter? not quite sure where the CGO_ENABLED=0 comes from there
2024-03-12 03:24:22 <ptrc> unless i missed some makefile stuff
2024-03-12 03:24:50 <celie> I think the prometheus-*-exporter stuff was failing because curl is no longer installed
2024-03-12 03:24:56 <celie> s/think/thought/
2024-03-12 03:25:09 <ptrc> yeah, but the postgres one is a different beast
2024-03-12 03:25:09 <celie> It wants to download a prebuilt binary
2024-03-12 03:25:14 <celie> Oh ok
2024-03-12 03:25:19 <ptrc> that one's failing with the usual "cannot do pie with cgo disabled"
2024-03-12 03:25:43 <ptrc> > -buildmode=pie requires external (cgo) linking, but cgo is not enabled
2024-03-12 03:26:07 <celie> I wonder if it will start failing with the curl thing after cgo is fixed
2024-03-12 03:26:24 <ptrc> we'll see :p
2024-03-12 03:27:36 <ptrc> ohhhh
2024-03-12 03:27:37 <ptrc> no
2024-03-12 03:27:40 <ptrc> it *has* curl
2024-03-12 03:27:43 <ptrc> that's why it's failing
2024-03-12 03:27:52 <ptrc> and that's why i couldn't find where the flags are coming from
2024-03-12 03:28:02 <ptrc> eugh
2024-03-12 03:30:15 <ptrc> do we need to package promu separately or what
2024-03-12 03:33:48 <celie> I think so, having a promu aport was also suggested in #15860
2024-03-12 03:34:06 <celie> Anyway, i may have found what's causing postgres-exporter to fail, will open an MR shortly
2024-03-12 03:35:36 <ptrc> i was thinking of just copying what promu does
2024-03-12 03:35:43 <ptrc> and putting that raw `go build` command in the APKBUILD
2024-03-12 03:44:13 <celie> I guess the builders still have curl installed
2024-03-12 03:44:56 <andypost[m]> celie: better to add as json-exporter doing
2024-03-12 03:45:16 <andypost[m]> and it missing export GOFLAGS="$GOFLAGS -modcacherw"
2024-03-12 03:45:57 <celie> Yes, i've added curl
2024-03-12 03:47:28 <celie> -modcacherw is already in /usr/share/abuild/default.conf
2024-03-12 03:49:33 <andypost[m]> celie: commented, looks it needs more fixes
2024-03-12 03:51:57 <andypost[m]> maybe bump to 0.15.0?
2024-03-12 04:03:23 <celie> Wow, the promu thing is really annoying
2024-03-12 04:03:29 <celie> Is anyone working on packaging promu?
2024-03-12 04:35:22 <celie> I've packaged promu, but used `go build` directly instead of `make` in build(), i guess if it builds prometheus-postgres-exporter fine, it should be good enough
2024-03-12 05:04:52 <celie> Ok, i've updated !62000 with the promu i packaged, and tried rebuilding prometheus-postgres-exporter and prometheus-json-exporter with it
2024-03-12 05:10:23 <celie> Ok !62000 has passed, but i see andypost has asked me to bump postgres exporter, i will try that and see if i can enable tests on 32-bit with the new version
2024-03-12 06:11:24 <celie> I think 62000 should be quite ready to merge, by building with a proper promu aport, we no longer need to:
2024-03-12 06:12:53 <celie> (1) add curl to makedepends, (2) patch Makefile to use `$(PROMU) build -cgo`, (3) remove ",hardfloat" from GO_BUILD_PLATFORM for 32-bit ARM
2024-03-12 09:22:00 <celie> algitbot: retry master
2024-03-12 09:22:50 <celie> algitbot: retry master
2024-03-12 09:23:02 <celie> algitbot: retry master
2024-03-12 09:23:56 <celie> algitbot: retry master
2024-03-12 09:25:40 <celie> testing/etcd is still setting CGO_ENABLED=0 somewhere :/
2024-03-12 09:25:59 <celie> algitbot: retry master
2024-03-12 09:28:12 <celie> algitbot: retry master
2024-03-12 10:54:48 <nmeum> so nebula needs a new gvisor version, because the old one doesn't work with Go 1.22
2024-03-12 16:54:51 <celie> algitbot: retry master
2024-03-12 17:12:28 <celie> algitbot: retry master
2024-03-12 17:14:14 <celie> algitbot: retry master
2024-03-12 19:58:37 <ikke> 🔴
2024-03-12 21:49:59 <andypost[m]> algitbot: retry master
2024-03-12 21:50:41 <andypost[m]> algitbot: retry master
2024-03-12 21:51:21 <andypost[m]> algitbot: retry master
2024-03-12 21:52:25 <andypost[m]> algitbot: retry master
2024-03-12 21:53:20 <andypost[m]> algitbot: retry master
2024-03-12 21:54:23 <andypost[m]> algitbot: retry master
2024-03-12 21:55:20 <andypost[m]> algitbot: retry master
2024-03-12 22:00:28 <andypost[m]> algitbot: retry master
2024-03-13 00:13:28 <andypost[m]> algitbot: retry master
2024-03-13 00:17:09 <andypost[m]> algitbot: retry master
2024-03-13 00:26:57 <andypost[m]> algitbot: retry master
2024-03-13 00:54:55 <andypost[m]> algitbot: retry master
2024-03-13 01:00:03 <celie> Oh dear
2024-03-13 01:00:12 <celie> Tootik is failing just as i feared?
2024-03-13 01:00:49 <ptrc> seems to be failing on some random tests
2024-03-13 01:02:50 <ptrc> would !61878 fix it?
2024-03-13 01:02:54 <celie> Yes, i think its tests are pretty picky, and require some conditions to be met
2024-03-13 01:02:56 <celie> Of course
2024-03-13 01:03:12 <celie> I mentioned it here before the testing/ rebuild
2024-03-13 01:03:22 <ptrc> ah, didn't notice
2024-03-13 01:03:47 <celie> I was just about to look that up from the IRC logs
2024-03-13 01:04:33 <celie> Nice to see that promu is coming in handy
2024-03-13 01:04:55 <ptrc> yeah, thanks for that ^^
2024-03-13 01:05:06 <celie> No problem
2024-03-13 01:05:30 <celie> Thanks for merging the newer Tootik :)
2024-03-13 01:06:27 <andypost[m]> algitbot: retry master
2024-03-13 01:20:13 <andypost[m]> algitbot: retry master
2024-03-13 01:41:53 <andypost[m]> algitbot: retry master
2024-03-13 01:54:58 <cely> Hmm, biome is Rust, not Go
2024-03-13 01:55:04 <cely> algitbot: retry master
2024-03-13 02:03:14 <andypost[m]> algitbot: retry master
2024-03-13 02:03:56 <andypost[m]> algitbot: retry master
2024-03-13 02:09:19 <andypost[m]> algitbot: retry master
2024-03-13 02:13:45 <andypost[m]> algitbot: retry master
2024-03-13 02:17:47 <cely> !62066
2024-03-13 02:18:06 <cely> but CI is busy building Chromium for x86_64 and aarch64
2024-03-13 02:18:30 <cely> and armv7 too
2024-03-13 02:33:19 <andypost[m]> algitbot: retry master
2024-03-13 02:36:42 <andypost[m]> algitbot: retry master
2024-03-13 02:37:12 <andypost[m]> algitbot: retry master
2024-03-13 02:38:14 <andypost[m]> algitbot: retry master
2024-03-13 02:38:48 <andypost[m]> algitbot: retry master
2024-03-13 02:39:57 <andypost[m]> algitbot: retry master
2024-03-13 02:42:00 <andypost[m]> algitbot: retry master
2024-03-13 02:42:27 <andypost[m]> algitbot: retry master
2024-03-13 02:55:35 <cely> !62068
2024-03-13 02:59:23 <cely> Maybe !62069 will solve the test failure on aarch64
2024-03-13 02:59:39 <andypost[m]> algitbot: retry master
2024-03-13 03:00:14 <andypost[m]> algitbot: retry master
2024-03-13 03:10:46 <andypost[m]> algitbot: retry master
2024-03-13 03:13:33 <andypost[m]> algitbot: retry master
2024-03-13 03:16:53 <cely> Hopefully !62070 will solve the last failing aport on x86
2024-03-13 03:29:54 <andypost[m]> celeste: thank you! x86 done)
2024-03-13 03:30:25 <cely> I'm looking into zot, it is the usual lfs64 in the Go sqlite binding
2024-03-13 03:32:55 <andypost[m]> algitbot: retry master
2024-03-13 03:58:23 <andypost[m]> algitbot: retry master
2024-03-13 04:00:40 <cely> For zot, i managed to come up with !62071, maybe there's an easier way..
2024-03-13 04:04:29 <cely> Hmm, testing/maddy fails on s390x due to test timeout, maybe it will pass with a retry, or the timeout needs to be increased
2024-03-13 04:04:47 <cely> algitbot: retry master
2024-03-13 04:06:54 <cely> Oh no, zot has yet another problem
2024-03-13 04:34:05 <cely> !62071 it took quite a bit of patching..
2024-03-13 04:37:43 <cely> I wonder what's up with the "expected 5 addresses, found 4" test error in testing/btcd
2024-03-13 04:38:35 <cely> algitbot: retry master
2024-03-13 04:46:46 <cely> algitbot: retry master
2024-03-13 04:55:10 <cely> algitbot: retry master
2024-03-13 04:56:56 <cely> Let's see if !62074 will fix the scaleway-cli test failures
2024-03-13 04:58:30 <cely> and !62071 has passed CI
2024-03-13 05:01:11 <cely> Hmm, why do i see npm output in scaleway-cli tests
2024-03-13 05:04:51 <cely> algitbot: retry master
2024-03-13 05:06:24 <cely> algitbot: retry master
2024-03-13 05:06:29 <andypost[m]> algitbot: retry master
2024-03-13 05:11:14 <andypost[m]> algitbot: retry master
2024-03-13 05:14:22 <andypost[m]> algitbot: retry master
2024-03-13 05:14:59 <andypost[m]> algitbot: retry master
2024-03-13 05:17:34 <cely> opa has !61506
2024-03-13 05:17:58 <cely> algitbot: retry master
2024-03-13 05:18:38 <cely> algitbot: retry master
2024-03-13 05:21:06 <cely> scaleway-cli tests seem to succeed on latest upstream master, now we just have to find out which of the 34 commits between v2.27.0 and master fixed things (or maybe they just skipped the failing tests?)
2024-03-13 05:25:20 <cely> algitbot: retry master
2024-03-13 05:30:25 <cely> I am working on disabling the failing certstrap tests, seems the certificate expired today...of all days
2024-03-13 05:31:51 <andypost[m]> algitbot: retry master
2024-03-13 05:32:35 <andypost[m]> armv7 uploading 🥳
2024-03-13 05:34:40 <andypost[m]> algitbot: retry master
2024-03-13 05:36:37 <cely> !62076
2024-03-13 05:48:09 <andypost[m]> algitbot: retry master
2024-03-13 05:50:22 <andypost[m]> algitbot: retry master
2024-03-13 06:10:15 <andypost[m]> algitbot: retry master
2024-03-13 06:13:16 <andypost[m]> algitbot: retry master
2024-03-13 06:16:48 <andypost[m]> algitbot: retry master
2024-03-13 06:16:59 <cely> Not sure how "correct" this fix is (!62077), but it is upstream's decision
2024-03-13 06:18:14 <ikke> that is one big patch
2024-03-13 06:19:09 <cely> Oh, alright, so maybe the test should be disabled, or we can upgrade to https://github.com/tetratelabs/wazero/releases/tag/v1.7.0-pre.1 ?
2024-03-13 06:27:48 <andypost[m]> algitbot: retry master
2024-03-13 06:32:33 <cely> I've updated !62077
2024-03-13 06:41:26 <cely> algitbot: retry master
2024-03-13 06:42:06 <cely> !62079
2024-03-13 06:47:24 <andypost[m]> celeste: the cause 20c1bf07870
2024-03-13 06:47:52 <andypost[m]> commit 20c1bf07870c961d1b506e6d6861329910e2f1df
2024-03-13 06:48:27 <andypost[m]> maybe arm builders are only ones without curl
2024-03-13 06:54:49 <cely> Yes, i am aware of the curl removal, it is why some of the prometheus exporters started failing
2024-03-13 06:55:09 <cely> i have updated the commit message of !62079 to mention that commit
2024-03-13 06:58:39 <cely> Oops, automatic merge won't work because the commit it was used on did not clean up the betula process, and so CI hangs
2024-03-13 06:59:49 <cely> the betula process started by test-web.sh*
2024-03-13 07:01:29 <cely> Yes, looking at the MR that added betula as a new aport, it seems the pipeline didn't finish there too
2024-03-13 07:01:52 <cely> but it was merged anyway
2024-03-13 07:06:13 <cely> I've mentioned the usql build error on #15862
2024-03-13 07:13:00 <cely> I wonder if biome is failing because previous builds have leftover some test files that should be deleted
2024-03-13 07:13:07 <cely> algitbot: retry master
2024-03-13 07:14:15 <cely> algitbot: retry master
2024-03-13 07:17:13 <cely> No seems, to be a diff between `<TIME>` and `2s`
2024-03-13 07:18:15 <cely> algitbot: retry master
2024-03-13 07:22:34 <cely> For wazero, !62077
2024-03-13 07:22:37 <cely> algitbot: retry master
2024-03-13 07:30:11 <cely> algitbot: retry master
2024-03-13 07:34:54 <cely> algitbot: retry master
2024-03-13 07:36:53 <cely> sing-box is also affected by #15862
2024-03-13 07:36:55 <cely> algitbot: retry master
2024-03-13 07:39:56 <cely> algitbot: retry master
2024-03-13 07:41:48 <cely> algitbot: retry master
2024-03-13 07:52:27 <cely> algitbot: retry master
2024-03-13 07:55:43 <cely> algitbot: retry master
2024-03-13 07:59:06 <cely> ikke: i think testing/atlas that is failing a test on ppc64le with "git diff: exit status 128" may be due to something in the .git directory on the builder, could you try running `git diff` on that and see if you get the same exit code?
2024-03-13 07:59:41 <cely> testing/atlas passes on the CI
2024-03-13 08:00:06 <cely> algitbot: retry master
2024-03-13 08:01:15 <cely> algitbot: retry master
2024-03-13 08:06:05 <cely> algitbot: retry master
2024-03-13 08:07:55 <cely> algitbot: retry master
2024-03-13 08:11:37 <cely> algitbot: retry master
2024-03-13 08:16:29 <cely> algitbot: retry master
2024-03-13 08:18:56 <cely> algitbot: retry master
2024-03-13 08:21:11 <cely> algitbot: retry master
2024-03-13 08:23:45 <cely> aarch64 and ppc64le both have 6 aports left for testing, i wouldn't be surprised if most of those contain failures
2024-03-13 08:23:53 <cely> algitbot: retry master
2024-03-13 08:27:10 <cely> For ppc64le, i can see heplify-server, atlas, usql, sing-box
2024-03-13 08:27:12 <cely> algitbot: retry master
2024-03-13 08:29:10 <cely> For aarch64: opa, wazero, kstars, biome
2024-03-13 08:29:26 <cely> algitbot: retry master
2024-03-13 08:34:15 <cely> algitbot: retry master
2024-03-13 08:35:05 <cely> algitbot: retry master
2024-03-13 08:38:25 <cely> algitbot: retry master
2024-03-13 08:44:26 <cely> algitbot: retry master
2024-03-13 08:44:57 <cely> algitbot: retry master
2024-03-13 08:46:51 <cely> algitbot: retry master
2024-03-13 08:47:49 <cely> algitbot: retry master
2024-03-13 08:49:04 <cely> algitbot: retry master
2024-03-13 08:56:25 <cely> algitbot: retry master
2024-03-13 08:57:14 <cely> algitbot: retry master
2024-03-13 08:57:44 <cely> algitbot: retry master
2024-03-13 08:58:52 <cely> algitbot: retry master
2024-03-13 09:01:12 <cely> So, for anyone watching this, the last 4 aports should be heplify-server, atlas, usql, sing-box (the latter 2 affected by #15862) for ppc64le, and opa, wazero, kstars, biome for aarch64
2024-03-13 09:02:36 <cely> For wazero, i have !62077, i think it should be alright to disable the test while waiting for upstream to release 1.7.0 (that removes gojs that test is a part of)
2024-03-13 09:07:10 <ptrc>    Actual   (d->getDetectedStars()): 125
2024-03-13 09:07:10 <ptrc>    Expected (NSTARS)               : 126
2024-03-13 09:07:10 <ptrc> FAIL!  : TestFitsData::testComputeHFR(NGC4535-3-FOCUS) Compared values are not the same
2024-03-13 09:07:18 <ptrc> we're.. missing a star?
2024-03-13 09:07:24 <cely> 1 star disappeared!
2024-03-13 09:14:25 <cely> algitbot: retry master
2024-03-13 09:18:06 <cely> armv7 is on the last aport for testing :)
2024-03-13 09:44:56 <PureTryOut> algitbot: retry master
2024-03-13 09:46:08 <PureTryOut> algitbot: retry master
2024-03-13 11:39:52 <ikke> cely: no issues with running git diff on the ppc64le builder
2024-03-13 13:24:20 <cely> ikke: Thanks, that makes the test failure more mysterious, as it seems it only happens for atlas on ppc64le (on the builder, not the CI)
2024-03-13 13:27:29 <cely> algitbot: retry master
2024-03-13 13:37:20 <cely> algitbot: retry master
2024-03-13 13:46:43 <cely> algitbot: retry master
2024-03-13 13:56:17 <cely> algitbot: retry master
2024-03-13 13:58:13 <cely> algitbot: retry master
2024-03-13 14:00:14 <cely> algitbot: retry master
2024-03-13 14:10:15 <cely> algitbot: retry master
2024-03-13 14:11:18 <cely> algitbot: retry master
2024-03-13 14:13:55 <cely> So, popeye builds on x86_64, and the 3 failing aports are: simpleiot, biome, opa
2024-03-13 14:18:08 <cely> opa has !61506, as for simpleiot, i am having trouble reproducing the error seen on the builder on the CI, because it seems to be failing somewhere else
2024-03-13 14:19:37 <cely> ("elm-spa failed to understand an error")
2024-03-13 14:19:45 <cely> Not sure what's happening there
2024-03-13 14:44:10 <cely> and the simpleiot errors seem to be from golangci-lint, not sure if we should be running that in the first place
2024-03-13 16:16:45 <ikke> cely: I don't think it makes sense for us to run golangci-lint
2024-03-13 16:20:25 <cely> Alright, that can probably be patched out of envsetup.sh, but on the CI it seems to be failing on something else
2024-03-13 16:23:51 <cely> Anyway, i'll make a patch, and maybe you can see if it fixes things on the builders
2024-03-13 16:23:59 <ikke> I'm checking atlas now
2024-03-13 16:26:58 <cely> !62099
2024-03-13 16:27:37 <cely> As expected, it fails on CI
2024-03-13 16:27:56 <cely> Probably the builders have some cached nodejs/npm/elm files
2024-03-13 16:37:17 <cely> Build log mentions /home/buildozer/.elm/elm-tooling probably the files cached there are preventing it from failing like in CI
2024-03-13 16:40:33 <ikke> cely: what arch?
2024-03-13 16:42:24 <cely> x86_64
2024-03-13 16:42:34 <cely> That's the only arch simpleiot is enabled for
2024-03-13 16:42:53 <ikke> cely: fatal: ambiguous argument 'master': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\n
2024-03-13 16:43:01 <ikke> That's the error
2024-03-13 16:43:23 <cely> Is that atlas on ppc64le or simpleiot on x86_64?
2024-03-13 16:43:31 <ikke> atlas on ppc64le
2024-03-13 16:47:18 <cely> Could it be that the builder has "defaultBranch = main" in ~/.gitconfig ?
2024-03-13 16:48:09 <ikke> ahuh
2024-03-13 16:48:37 <cely> *sighs*
2024-03-13 16:48:49 <ikke> yup
2024-03-13 16:48:54 <cely> All these tests that keep modifying ~/.gitconfig
2024-03-13 16:49:13 <ikke> Should probably make that file immutable
2024-03-13 16:49:30 <ikke> Anythign that touches it should fail
2024-03-13 16:50:30 <cely> That would be good...hopefully it doesn't result in too many new failures
2024-03-13 16:53:41 <ikke> algitbot: retry master
2024-03-13 16:56:55 <cely> algitbot: retry master
2024-03-13 16:57:07 <ikke> cely: should I remove the .elm dir (ie, do you want it to fail?
2024-03-13 16:57:31 <cely> If it fails, we would have to disable simpleiot
2024-03-13 16:58:04 <cely> So, i'm not so sure about that
2024-03-13 16:58:21 <ikke> ok
2024-03-13 16:59:29 <cely> I would be interested to see if patching out golangci-lint (!62099) would allow it to pass (with whatever is currently in .elm)
2024-03-13 16:59:40 <ikke> can check that
2024-03-13 16:59:50 <cely> algitbot: retry master
2024-03-13 17:01:28 <cely> The biome failure is another thing that didn't turn up in CI, !61869 passed
2024-03-13 17:03:19 <cely> I took a brief look, and there is some code that uses regex to replace something like "2s" with "<TIME>", don't know why it doesn't work on the builder
2024-03-13 17:03:40 <cely> algitbot: retry master
2024-03-13 17:06:01 <cely> algitbot: retry master
2024-03-13 17:09:02 <ikke> cely: seems to succeed with that patch
2024-03-13 17:09:16 <cely> Alright
2024-03-13 17:10:18 <cely> algitbot: retry master
2024-03-13 17:16:18 <ikke>    Actual   (d->getDetectedStars()): 125
2024-03-13 17:16:20 <ikke>    Expected (NSTARS)               : 126
2024-03-13 17:16:33 <ikke> off-by-one 😑
2024-03-13 17:16:39 <cely> Yes, ptrcnull mentioned that
2024-03-13 17:16:45 <cely> I think it passes on the other archs
2024-03-13 17:17:16 <cely> So, aarch64 is somehow omitting 1 star
2024-03-13 17:18:45 <cely> Anyway, as i'll be going AFK now, i'll leave it up to you whether to apply that patch to simpleiot or not, i don't use simpleiot
2024-03-13 17:19:19 <cely> So, if it doesn't suddenly start succeeding in CI, then on the next upgrade, its maintainer will have to look into it
2024-03-13 17:20:01 <cely> I think it's downloading a prebuilt Elm toolchain, which probably means it's better for Elm to be added as an aport
2024-03-13 17:20:21 <ikke> sounds like a good idea in general
2024-03-13 17:27:19 <cely> I see simpleiot's maintainer has replied to the MR, i've sent a short reply before going AFK
2024-03-13 17:30:43 <ikke> I replied to the comment
2024-03-14 02:40:23 <celie> algitbot: retry master
2024-03-14 03:51:39 <cely> Hmm, ptrc, would it be better to split the Python speech-dispatcher stuff into subpackages?
2024-03-14 03:52:34 <ptrc> hm, do you think so?
2024-03-14 03:52:50 <ptrc> i didn't really think much about it, especially since i'm not too sure which part is being used by Firefox
2024-03-14 03:52:58 <ptrc> for all i know, it could be both
2024-03-14 03:54:00 <cely> Hmm, let me see how other distros do it
2024-03-14 03:55:14 <cely> Debian has https://packages.debian.org/python3-speechd
2024-03-14 03:57:10 <cely> But it seems Arch and Void don't bother, and just include it in the main package
2024-03-14 03:58:09 <ptrc> arch rarely bothers
2024-03-14 03:58:21 <ptrc> as in, with splitting stuff
2024-03-14 03:58:26 <ptrc> not sure if makepkg even supports it
2024-03-14 04:04:58 <cely> //usr/bin/spd-conf is a Python script, so will need to go into the Python subpackage, if you choose add that
2024-03-14 04:05:04 <cely> -/
2024-03-14 04:27:14 <cely> I wonder if biome tests should just be disabled for the time being, at least the failing ones
2024-03-14 04:48:51 <cely> algitbot: retry master
2024-03-14 04:51:35 <cely> algitbot: retry master
2024-03-14 04:57:05 <cely> I will prepare an MR for the ppc64le failures
2024-03-14 05:22:23 <cely> !62126 hopefully i got it right this time, and CI passes
2024-03-14 05:22:33 <cely> algitbot: retry master
2024-03-14 05:50:52 <cely> Ok, !62126 should be good to go unless there is anyone else who wants to try out some other solution
2024-03-14 05:51:47 <cely> The workaround for sing-box and usql is temporary anyway, and will be removed once #15862 is properly fixed
2024-03-14 06:06:45 <cely> Now that the failing biome tests are skipped, i think the only aports left are opa and kstars (kstars only on aarch64)
2024-03-14 08:15:19 <cely> ncopa: i see you've disabled heplify-server on ppc64le, i have !62126, i'll be going AFK now, so i've rebased it and removed the heplify-server commit
2024-03-14 08:18:36 <cely> (i actually had a fix for heplify-server there which involved running tests without -race and enabling -buildmode=pie (for tests) on all architectures)
2024-03-14 08:28:23 <ncopa> Awesome!
2024-03-14 13:37:43 <cely> Now all that's left is the 1 missing star in kstars tests on aarch64
2024-03-14 13:41:01 <ikke> waiting for opa to finish building
2024-03-14 16:52:23 <ikke> algitbot: retry master
2024-03-14 16:56:38 <cely> Err
2024-03-14 16:56:51 <cely> Am i seeing this right...you added the patch to builddir=?
2024-03-14 16:57:29 <ikke> yup 😶
2024-03-14 17:00:27 <cely> and sha512sums? :)
2024-03-14 17:01:36 <cely> I mean, that didn't get updated
2024-03-14 17:04:00 <cely> Interesting, it seems the kstars patch MR had a different error for each arch
2024-03-14 17:04:49 <cely> aarch64 was probably due to testing not yet being uploaded, s390x was the builddir error, but x86 has a bad signature for kplotting5-dev
2024-03-14 17:05:01 <ikke> lol
2024-03-14 17:05:19 <cely> However, kplotting5 is okay..
2024-03-14 17:23:10 <ikke> 🥳
2024-03-15 00:03:20 <andypost[m]> algitbot: retry master
2024-03-15 01:06:03 <celie> algitbot: retry master
2024-03-15 01:09:16 <celie> Here we go with the element-web on armhf retry frenzy
2024-03-15 01:09:19 <celie> algitbot: retry master
2024-03-15 01:13:07 <celie> algitbot: retry master
2024-03-15 01:15:55 <celie> algitbot: retry master
2024-03-15 01:17:41 <celie> algitbot: retry master
2024-03-15 01:20:00 <celie> algitbot: retry master
2024-03-15 01:22:48 <celie> algitbot: retry master
2024-03-15 01:25:31 <celie> algitbot: retry master
2024-03-15 01:28:31 <celie> algitbot: retry master
2024-03-15 01:35:18 <celie> So, apparently the libjasper.a undefined reference to jpc_decode/encode/validate in jas_init.c, undefined reference to jpc_decode/encode in jp2_dec/enc.c solved themselves after some retries?
2024-03-15 01:36:55 <celie> Oh no, i think 2.4.15.4 and 2.4.15.5 of mod_auth_openidc got yanked...
2024-03-15 01:37:58 <celie> algitbot: retry master
2024-03-15 01:38:20 <celie> Tags are still on Github, but the APKBUILD uses the release artifacts which are gone
2024-03-15 01:40:27 <celie> algitbot: retry master
2024-03-15 01:46:00 <cely> algitbot: retry master
2024-03-15 01:49:17 <cely> algitbot: retry master
2024-03-15 01:55:30 <cely> algitbot: retry master
2024-03-15 01:59:03 <cely> algitbot: retry master
2024-03-15 02:05:08 <cely> algitbot: retry master
2024-03-15 02:05:50 <cely> !62186 for openidc (tarball of previous version has been deleted)
2024-03-15 02:10:42 <cely> algitbot: retry master
2024-03-15 02:11:02 <cely> algitbot: retry master
2024-03-15 02:15:02 <cely> algitbot: retry master
2024-03-15 02:30:35 <cely> algitbot: retry master
2024-03-15 02:34:15 <cely> algitbot: retry master
2024-03-15 02:43:01 <cely> algitbot: retry master
2024-03-15 02:48:48 <cely> algitbot: retry master
2024-03-15 02:56:45 <cely> algitbot: retry master
2024-03-15 02:57:52 <cely> So, given enough retries, netbpm tests that failed on ppc64le will pass
2024-03-15 02:58:12 <cely> Probably the same thing with aarch64
2024-03-15 02:59:24 <cely> algitbot: retry master
2024-03-15 02:59:36 <cely> Now when will this magic work on armhf's element-web
2024-03-15 03:10:36 <cely> algitbot: retry master
2024-03-15 03:13:20 <cely> algitbot: retry master
2024-03-15 03:24:59 <cely> algitbot: retry master
2024-03-15 03:56:23 <cely> Wow, the netpbm tests sure are flaky
2024-03-15 03:56:31 <cely> algitbot: retry master
2024-03-15 03:56:51 <cely> Hopefully they will pass after some retries just like the other archs
2024-03-15 03:59:01 <cely> algitbot: retry master
2024-03-15 04:02:05 <cely> algitbot: retry master
2024-03-15 04:10:33 <cely> algitbot: retry master
2024-03-15 04:18:20 <cely> algitbot: retry master
2024-03-15 04:39:15 <cely> algitbot: retry master
2024-03-15 04:56:32 <cely> algitbot: retry master
2024-03-15 05:04:48 <cely> algitbot: retry master
2024-03-15 05:08:51 <cely> algitbot: retry master
2024-03-15 05:13:36 <cely> algitbot: retry master
2024-03-15 06:08:57 <cely> algitbot: retry master
2024-03-15 06:27:09 <cely> algitbot: retry master
2024-03-15 06:29:37 <cely> algitbot: retry master
2024-03-15 06:32:21 <cely> algitbot: retry master
2024-03-15 06:35:46 <cely> I wonder if we've run out of luck with regards to constant retries getting element-web to build on armhf
2024-03-15 06:36:52 <cely> Maybe armhf should finally follow armv7, and be disabled for element-web
2024-03-15 06:44:39 <cely> algitbot: retry master
2024-03-15 06:47:47 <cely> algitbot: retry master
2024-03-15 06:56:00 <cely> algitbot: retry master
2024-03-15 06:58:07 <cely> algitbot: retry master
2024-03-15 07:00:45 <cely> algitbot: retry master
2024-03-15 07:03:24 <cely> algitbot: retry master
2024-03-15 07:06:23 <cely> Probably not worth retrying anymore :/
2024-03-15 07:25:51 <cely> algitbot: retry master
2024-03-15 07:48:55 <ncopa> algitbot: retry master
2024-03-16 12:57:46 <andypost[m]> algitbot: retry master
2024-03-16 13:00:26 <andypost[m]> algitbot: retry master
2024-03-16 13:06:22 <andypost[m]> algitbot: retry master
2024-03-16 13:09:47 <andypost[m]> algitbot: retry master
2024-03-16 15:23:41 <PureTryOut> Waat....
2024-03-16 15:23:58 <ikke> oof
2024-03-16 15:24:08 <PureTryOut> Bot messed up there, there definitely weren't 1075 commits merged lol
2024-03-16 15:24:28 <ikke> that's not a merge
2024-03-16 15:24:30 <ikke> just pushign a branch
2024-03-16 15:24:39 <PureTryOut> oh, yeah I rebased one
2024-03-16 15:24:40 <PureTryOut> Lol ok
2024-03-16 15:25:27 <ikke> You pushed to alpine/aports instead of the original fork
2024-03-16 15:26:09 <PureTryOut> the author of the MR just made it on the wrong remote 🤷
2024-03-16 15:26:12 <PureTryOut> https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/61545
2024-03-16 15:26:27 <ikke> heh
2024-03-16 15:27:13 <PureTryOut> Nothing to worry about then 😄
2024-03-16 15:27:21 <ikke> nope
2024-03-17 03:12:36 <cely> Hi, qaqland
2024-03-17 03:20:48 <qaqland> hello~
2024-03-17 03:21:14 <qaqland> o/
2024-03-17 11:14:52 <andypost[m]> algitbot: retry master
2024-03-17 22:47:19 <ptrc> sigh
2024-03-17 22:55:42 <ptrc> oh god
2024-03-17 22:55:45 <ptrc> i forgot to squash it
2024-03-17 22:55:49 <ptrc> sorry everyone
2024-03-17 23:53:24 <ptrc> algitbot: retry master
2024-03-18 01:21:53 <andypost[m]> algitbot: retry master
2024-03-18 01:40:02 <cely> algitbot: retry master
2024-03-18 02:39:10 <cely> algitbot: retry master
2024-03-18 03:37:24 <andypost[m]> algitbot: retry master
2024-03-18 04:33:50 <cely> algitbot: retry master
2024-03-18 05:26:01 <cely> algitbot: retry master
2024-03-18 05:59:59 <cely> algitbot: retry master
2024-03-18 07:58:26 <cely> algitbot: retry master
2024-03-18 08:31:32 <cely> algitbot: retry master
2024-03-18 08:31:39 <cely> algitbot: retry 3.19-stable
2024-03-18 08:56:10 <cely> algitbot: retry master
2024-03-18 10:31:07 <PureTryOut> algitbot: retry master
2024-03-18 13:43:46 <ptrc> ..oops
2024-03-18 13:43:49 <ptrc> wrong remote
2024-03-18 13:44:05 <ptrc> removed
2024-03-18 14:03:32 <andypost[m]> algitbot: retry master
2024-03-18 14:17:03 <andypost[m]> algitbot: retry master
2024-03-18 15:40:50 <cely> algitbot: retry master
2024-03-19 01:12:14 <celie> algitbot: retry master
2024-03-19 01:35:03 <celie> algitbot: retry master
2024-03-19 01:36:21 <omni> algitbot: retry master
2024-03-19 01:37:03 <celie> Can't connect to static.crates.io, that's not good..
2024-03-19 01:39:18 <celie> Ok, a retry fixed it
2024-03-19 01:42:01 <celie> I wonder if removing -D_GLIBCXX_ASSERTIONS=1 will allow webkit2gtk to build on x86, but that's probably not something that can be removed without looking closer into the issue
2024-03-19 01:42:28 <celie> without first*
2024-03-19 02:50:44 <cely> algitbot: retry master
2024-03-19 03:46:42 <cely> algitbot: retry master
2024-03-19 05:59:56 <cely> algitbot: retry master
2024-03-19 07:13:05 <rnalrd> algitbot: retry master
2024-03-19 07:13:40 <cely> The tarball is unversioned
2024-03-19 07:14:05 <rnalrd> ah right thanks
2024-03-19 07:14:19 <cely> Np
2024-03-19 07:19:21 <cely> algitbot: retry master
2024-03-19 09:10:53 <celie> algitbot: retry master
2024-03-19 12:40:25 <celie> algitbot: retry master
2024-03-19 13:42:17 <cely> algitbot: retry master
2024-03-19 15:38:54 <andypost[m]> algitbot: retry master
2024-03-19 18:21:27 <ptrc> algitbot: retry master
2024-03-19 18:21:29 <ptrc> come on, build
2024-03-19 21:08:46 <ikke> ptrc: I guess ^ needs the same patch
2024-03-19 21:16:38 <andypost[m]> ptrc: ikke: ^^ backported
2024-03-19 21:17:02 <ikke> s/back/forward :P
2024-03-19 21:17:30 <andypost[m]> ))
2024-03-19 22:31:09 <andypost[m]> algitbot: retry master
2024-03-20 01:53:23 <celie> algitbot: retry master
2024-03-20 02:18:24 <ptrc> andypost[m]: thanks!
2024-03-20 02:43:22 <andypost[m]> ptrc: thank you) 
2024-03-20 06:58:12 <cely> algitbot: retry master
2024-03-20 09:54:21 <ptrc> algitbot: retry master
2024-03-20 16:16:21 <celie> nmeum: github-cli also has a ppc64le workaround (it disables CGO for that arch)
2024-03-20 16:17:38 <nmeum> celie: removed that as well now, thanks!
2024-03-20 16:18:13 <celie> You're welcome
2024-03-20 20:00:26 <andypost[m]> algitbot: retry master
2024-03-21 00:36:33 <celie> algitbot: retry master
2024-03-21 04:49:30 <celie> algitbot: retry master
2024-03-22 00:52:38 <celie> algitbot: retry master
2024-03-22 02:13:08 <celie> algitbot: retry master
2024-03-22 02:45:27 <celie> Rust 1.77.0 is available for ARM \o/
2024-03-22 02:46:07 <celie> and ppc64le
2024-03-22 02:57:11 <celie> That leaves only s390x and riscv64
2024-03-22 11:38:55 <ikke> algitbot: retry 3.19-stable
2024-03-22 11:39:00 <ikke> algitbot: retry 3.19-stable
2024-03-22 19:56:52 <ptrc> algitbot: kick build-edge-riscv64
2024-03-22 19:56:54 <ptrc> is that how it works
2024-03-22 19:56:58 <ptrc> algitbot: retry master
2024-03-22 19:57:08 <ptrc> nope
2024-03-22 19:57:12 <ptrc> doesn't seem to do anything
2024-03-22 19:57:18 <ikke> Don't think that still works
2024-03-22 19:59:18 <ikke> You want it to build the latest version?
2024-03-22 19:59:37 <ptrc> i want it to stop building the 4.1 webkit
2024-03-22 19:59:41 <ptrc> because i know that's gonna fai
2024-03-22 20:00:36 <ptrc> thanks!
2024-03-22 20:01:04 <ikke> np
2024-03-22 21:05:30 <ikke> algitbot: retry master
2024-03-23 06:00:07 <celie> algitbot: retry master
2024-03-23 07:22:13 <ptrc> hah, armv7 purpose5 was build against a package that was already gone, just not removed yet
2024-03-23 07:22:52 <ptrc> on x86_64 it ( correctly ) skipped kaccounts stuff
2024-03-23 07:22:53 <ptrc> https://ptrc.gay/EZvWwPyU
2024-03-23 07:24:02 <ptrc> this is silly
2024-03-23 07:24:08 <ptrc> but well
2024-03-23 09:51:40 <ptrc> algitbot: retry master
2024-03-23 13:07:33 <ptrc> ikke: does the aarch64 builder have some Qt6 stuff left over in world?
2024-03-23 13:07:53 <ptrc> looking at makedepends, it very much should not install qt6-qtcore
2024-03-23 13:07:57 <ptrc> and it does not, but it's present
2024-03-23 13:09:38 <ikke> https://tpaste.us/xyxr 
2024-03-23 13:12:22 <ptrc> ikke: `apk dot --installed | grep qt6`?
2024-03-23 13:12:32 <ptrc> but well, that's odd
2024-03-23 13:15:00 <ptrc> wait no i'm blind
2024-03-23 13:15:07 <ptrc> it literally has qt6 in the "Installing" list
2024-03-23 13:15:08 <ptrc> also oops
2024-03-23 19:57:08 <omni> boom
2024-03-23 19:58:49 <omni> worried you'd kickban yourself due to flooding, algitbot?
2024-03-23 22:45:03 <andypost[m]> algitbot: retry master
2024-03-24 00:13:52 <omni> algitbot: retry master
2024-03-24 00:21:58 <omni> wat
2024-03-24 00:26:15 <omni> algitbot: retry master
2024-03-24 00:28:01 <omni> algitbot: retry master
2024-03-24 00:29:48 <omni> oh well, I'm not sure I know how to fix that
2024-03-24 00:29:57 <omni> nor why it failed
2024-03-24 00:44:04 <omni> hmm, same issue...
2024-03-24 00:44:09 <omni> algitbot: retry master
2024-03-24 00:44:46 <omni> algitbot: retry master
2024-03-24 01:19:24 <celie> algitbot: retry master
2024-03-24 01:20:17 <celie> algitbot: retry master
2024-03-24 01:21:00 <celie> algitbot: retry master
2024-03-24 01:21:29 <celie> algitbot: retry master
2024-03-24 01:22:38 <celie> algitbot: retry master
2024-03-24 01:24:43 <celie> algitbot: retry master
2024-03-24 01:26:27 <celie> algitbot: retry master
2024-03-24 01:27:01 <celie> algitbot: retry master
2024-03-24 12:58:35 <omni> ikke: what's up with clojure on build-3-19-ppc64le?
2024-03-24 13:22:34 <ikke> omni: not sure, it hangs for some reason: https://tpaste.us/YY54 
2024-03-24 14:23:36 <omni> oh, I actually commented on this https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/61863#note_383209
2024-03-24 14:24:06 <omni> what if we upgraded maven in 3.19?
2024-03-24 14:24:43 <omni> I'll try in an MR since the clojure tests issue seemed reproducible for ppc64le there
2024-03-24 14:41:52 <omni> hmmm https://gitlab.alpinelinux.org/alpine/aports/-/jobs/1317274
2024-03-24 18:55:22 <omni> algitbot: retry master
2024-03-24 19:06:28 <omni> omg, restored nerd fonts, so cool
2024-03-25 05:27:11 <celie> algitbot: retry master
2024-03-25 05:33:59 <celie> fscrypt was last rebuilt on 13 March in the big Go 1.22.1 rebuild, and most of the package versions remain the same, with the exception of libxml2 that got upgraded to 2.12.6, but the other archs also built fscrypt-0.3.4-r8 with libxml2 2.12.6, so that's probably not causing the issue
2024-03-25 05:51:24 <ikke> another change is that the builder has moved to real rv64 hw
2024-03-25 06:13:12 <celie> I wonder if that error from the multiprocessing Python lib could be related to that move
2024-03-25 06:14:16 <celie> or rather, the warnings from py3-pebble
2024-03-25 06:14:19 <celie> Not sure if they're related to the test failure
2024-03-25 06:14:26 <celie> algitbot: retry master
2024-03-25 06:18:58 <ikke> Tests have been enabled as well, so we could expect additional errors from that
2024-03-25 06:27:26 <celie> Ah, that's probably it
2024-03-25 06:27:31 <celie> Enabling tests
2024-03-25 06:27:32 <celie> algitbot: retry master
2024-03-25 06:28:58 <ikke> mnt.Device wasn't set to source device
2024-03-25 06:29:36 <celie> Seems like it's looking through all the mountpoints on the builder?
2024-03-25 06:31:01 <celie> algitbot: retry master
2024-03-25 06:31:22 <ikke> Nothing special on that builder
2024-03-25 06:32:02 <celie> I think i'll go prepare an MR to disable TestLoadSourceDevice on riscv64
2024-03-25 06:32:23 <celie> Btw, just wondering, did you leave #alpine-loongarch?
2024-03-25 06:32:43 <celie> algitbot: retry master
2024-03-25 06:32:47 <celie> One last retry
2024-03-25 06:33:06 <ikke> celie: oh, not on purpose, forgot to rejoin
2024-03-25 06:47:12 <celie> algitbot: retry master
2024-03-25 06:53:13 <celie> !62820
2024-03-25 06:54:51 <celie> It also seems to be failing consistently on one of the CI runners (nbBrusBKa pioneer2), on the other one (JZnuypS7T pioneer1) it passes
2024-03-25 06:55:09 <celie> I guess the one it fails on is the one that also hosts the builder
2024-03-25 06:56:51 <ikke> pioneer2 indeed has the builder
2024-03-25 11:58:23 <omni> ikke: is it https://milkv.io/pioneer ?
2024-03-25 11:59:44 <ikke> omni: yes
2024-03-25 11:59:48 <ikke> afaik
2024-03-25 12:00:28 <omni> cool
2024-03-25 12:00:29 <omni> want
2024-03-27 13:15:43 <celie> algitbot: retry master
2024-03-27 18:31:33 <ncopa> algitbot: retry master
2024-03-27 19:13:29 <ikke> algitbot: retry master
2024-03-27 19:14:16 <ikke> stdlol.h? :D
2024-03-27 20:41:32 <ikke> err ppoll should not be accessible without _GNU_SOURCE
2024-03-27 20:41:39 <ikke> 🤔
2024-03-27 20:58:05 <nmeum> probably a bug with the has_header_symbol implementation in moun, musl only defines ppoll in poll.h if either _GNU_SOURCE or _BSD_SOURCE is defined
2024-03-27 20:58:19 <ikke> yes, I checked
2024-03-27 20:58:31 <ikke> Just curious why it fails now
2024-03-27 20:58:46 <nmeum> yea, that's also a mystery to me
2024-03-27 20:59:08 <nmeum> need to debug the has_header_symbol function to figure that out I suppose
2024-03-27 21:10:15 <nmeum> ah
2024-03-27 21:17:40 <nmeum> ikke: ^ (idk how this past previously, maybe different gcc version)
2024-03-27 21:18:02 <ikke> yeah, that would be my guess
2024-03-27 21:18:40 <omni> \o/
2024-03-27 21:18:55 <ikke> nmeum: thanks
2024-03-27 21:19:09 <nmeum> np
2024-03-27 21:19:26 <nmeum> these kinds of failures are always fun to debug :3
2024-03-27 21:20:56 <ikke> nmeum: maybe report it here? https://todo.sr.ht/~lattis/muon/
2024-03-27 21:22:10 <nmeum> the aport package maintainer is also the upstream developer so i just CC'ed them on the commit https://gitlab.alpinelinux.org/alpine/aports/-/commit/b0dac731b77c4f313bb7ee19a2deedb8c8dcf800#note_388993
2024-03-27 21:22:33 <nmeum> hopefully they see that so that I don't have to write a proper bug report
2024-03-27 21:22:50 <ikke> 🙂
2024-03-27 23:52:50 <andypost[m]> algitbot: retry master
2024-03-27 23:59:36 <ptrc> shouldn't have merged the openfire stuff
2024-03-27 23:59:41 <ptrc> no idea how i missed that it fails everywhere
2024-03-28 00:14:26 <ptrc> algitbot: retry master
2024-03-28 01:03:58 <ptrc> on one hand: yes, i forgot to rebuild all of these
2024-03-28 01:04:13 <ptrc> on the other hand though: we don't need to do that until 3.12! and when we do 3.12, we'll rebuild everything anyway :)
2024-03-28 01:05:15 <celie> No gpep517 as well?
2024-03-28 01:06:52 <ptrc> that is a bit more effort than just removing a few lines :p but yeah, i'm also ( once in a while ) slowly trying to migrate everything
2024-03-28 01:07:17 <ptrc> hopefully we'll collectively manage to do that before setuptools removes setup.py support
2024-03-28 01:07:46 <celie> Wow, are there plans to do that already?
2024-03-28 01:08:07 <ptrc> i mean, that's what the massive deprecation notice is for, isn't it?
2024-03-28 01:08:18 <ptrc> deprecated = it's bound to be removed at some point
2024-03-28 01:08:21 <celie> I mean, plans to remove setup.py support
2024-03-28 01:08:36 <ptrc> at least that's how i interpret it
2024-03-28 01:09:46 <celie> My impression was that directly calling setup.py is deprecated, but at least it should continue to work if done through gpep517? (unless the legacy backend on gpep517 not use setup.py at all...)
2024-03-28 01:10:18 <ptrc> err, yes
2024-03-28 01:10:31 <ptrc> s/removes setup.py support/removes support for calling setup.py directly/
2024-03-28 01:11:31 <celie> Ok, that would be another crazy change to handle when it does happen
2024-03-28 01:13:52 <celie> Hmm sbcl is failing on x86
2024-03-28 01:15:42 <celie> Maybe it has something to do with the "perfect hash file is missing a needed entry" error
2024-03-28 09:35:40 <ptrc> algitbot: retry master
2024-03-28 09:39:32 <ptrc> algitbot: retry master
2024-03-28 11:43:28 <ptrc> algitbot: retry master
2024-03-28 11:47:38 <ptrc> algitbot: retry master
2024-03-28 11:52:59 <ptrc> algitbot: retry master
2024-03-28 12:01:27 <ptrc> algitbot: retry master
2024-03-28 12:38:54 <ikke> ^ seems to fail due to warning output
2024-03-28 14:22:08 <cely> algitbot: retry master
2024-03-28 15:45:40 <ptrc> algitbot: retry master
2024-03-28 17:44:37 <cely> algitbot: retry master
2024-03-28 17:44:46 <cely> algitbot: retry master
2024-03-28 17:44:59 <cely> Hmm, aarch64 fails to pull git?
2024-03-28 17:46:38 <ikke> cely: I have moved it, but some permission errors
2024-03-28 17:47:03 <cely> Ok
2024-03-28 17:47:51 <ikke> algitbot: retry master
2024-03-28 17:48:00 <ikke> cely: fixed
2024-03-28 21:13:04 <omni> ffs
2024-03-28 21:13:55 <omni> algitbot: retry master
2024-03-28 21:15:53 <ikke> hmm, let me check
2024-03-28 21:16:52 <ikke> algitbot: retry master
2024-03-28 21:16:59 <ikke> should be fixed now
2024-03-28 21:17:21 <omni> I don't see it running at https://build.alpinelinux.org/
2024-03-28 21:19:48 <ikke> now it is
2024-03-28 21:19:58 <omni> cool, thanks
2024-03-29 00:28:51 <celie> omni: So, does this mean you'll have to use qt-chromium's vendored re2?
2024-03-29 00:31:30 <omni> celie: "this" as in my comment in my MR? yes
2024-03-29 00:31:48 <celie> Yes
2024-03-29 00:32:22 <omni> I would prefer to use our system libs, if possible
2024-03-29 00:32:44 <omni> but don't think I'll put to much effort into patching that into happening
2024-03-29 00:34:29 <omni> upstream is quite friendly, they hang out in #qtwebengine@libera and have helped out before
2024-03-29 00:35:59 <celie> I think i've seen a discussion about this in #alpine-devel a while back
2024-03-29 00:35:59 <celie> about Chromium and re2
2024-03-29 00:36:15 <omni> I don't know why it doesn't pick up "libxml2 and libxslt" when libxml2-dev and libxslt-dev are added as makedepends
2024-03-29 00:36:45 <omni> also "Use System Ninja ....................... no"
2024-03-29 00:36:53 <celie> Does it even yes
2024-03-29 00:37:06 <celie> I was just about to ask about that
2024-03-29 00:37:06 <celie> :P
2024-03-29 00:37:17 <celie> Probably it wants ninja-is-really-ninja instead of samurai
2024-03-29 00:37:29 <omni> oh, huh
2024-03-29 00:38:53 <omni> subpackages="ninja-is-really-ninja:reallyreally"
2024-03-29 00:39:24 <omni> but as in not samurai then
2024-03-29 00:39:57 <celie> "Please use this ninja, really really please"
2024-03-29 00:43:17 <celie> I think i once tried running cmake tests, only to find that it is expecting ninja-is-really-ninja instead of samurai output
2024-03-29 00:44:46 <celie> but ninja-is-really-ninja is in community, and built with cmake and samurai (so would result in a circular dependency if added to cmake's checkdeps)
2024-03-29 00:45:34 <omni> this sounds more and more like something that I am not going to dive into anytime soon
2024-03-29 00:48:11 <celie> Could it be that qt-chromium's build system is checking for some libxml2/libxslt thing that we've moved to a subpackage? Perhaps libxml2-utils, py3-libxml2...or maybe libxml2/libxslt-static?
2024-03-29 00:48:50 <celie> Ok, libxml2-dev already depends on libxml2-utils
2024-03-29 00:51:38 <omni> I mostly try to pull in backported security fixes to qt{5,6}-qtwebengine every now and then
2024-03-29 00:53:57 <omni> but that's just my level of ambition
2024-03-29 00:54:22 <omni> and then I might try to nudge things outside of that scope sometimes
2024-03-29 01:56:59 <cely> Hmm, so jitsi-videobridge finished building on ppc64le after all
2024-03-30 06:32:55 <ikke> algitbot: retry master
2024-03-30 06:37:59 <ikke> algitbot: retry master
2024-03-30 13:12:58 <celie> algitbot: retry master
2024-03-30 13:15:41 <celie> Hmm, "Permision denied: /var/tmp/.cache/borg"
2024-03-30 13:54:19 <ikke> will fix it
2024-03-30 13:54:50 <ikke> Due to shared directories, and different uids I need to fix permissions to match the other build host
2024-03-30 13:55:25 <celie> Alright
2024-03-30 13:56:24 <ikke> algitbot: retry master