2024-10-01 02:06:50 <cely> algitbot: retry master
2024-10-01 02:16:38 <cely> algitbot: retry master
2024-10-01 03:44:56 <cely> algitbot: retry master
2024-10-01 04:04:56 <mio> algitbot: retry master
2024-10-01 04:12:00 <cely> algitbot: retry master
2024-10-01 04:13:03 <cely> algitbot: retry master
2024-10-01 04:18:07 <mio> algitbot: retry master
2024-10-01 04:28:08 <cely> algitbot: retry master
2024-10-01 04:34:04 <cely> algitbot: retry master
2024-10-01 04:44:56 <cely> algitbot: retry master
2024-10-01 04:47:58 <cely> algitbot: retry master
2024-10-01 05:02:19 <cely> algitbot: retry master
2024-10-01 09:40:28 <cely> algitbot: retry master
2024-10-01 12:43:23 <PureTryOut> wut, I removed the wip... Did I seriously merge too quickly, even though locally git said everything was pushed? wtf
2024-10-01 13:02:08 <ptrc> PureTryOut: GitLab has an issue where for the first 5-15 seconds it will not update the MR after pushing
2024-10-01 13:02:16 <ptrc> and afaict it's not only ours
2024-10-01 13:06:18 <PureTryOut> fun
2024-10-01 15:49:36 <mio> algitbot: retry master
2024-10-01 15:49:44 <omni> mm...
2024-10-01 15:50:36 <mio> lol was going to ping you if a retry failed
2024-10-01 15:57:27 <omni> meh
2024-10-01 15:57:58 <omni> algitbot: retry master
2024-10-01 16:05:58 <cely> algitbot: retry master
2024-10-01 16:12:35 <cely> algitbot: retry master
2024-10-01 16:22:59 <cely> algitbot: retry master
2024-10-01 16:39:05 <cely> algitbot: retry master
2024-10-01 17:38:22 <mio> algitbot: retry master
2024-10-01 17:38:46 <mio> algitbot: retry 3.20
2024-10-01 17:38:51 <mio> algitbot: retry v3.20
2024-10-01 17:39:32 <mio> algitbot: retry 3.20-stable
2024-10-01 17:40:23 <omni> thanks
2024-10-01 17:40:33 <omni> other error this time...
2024-10-01 17:40:34 <mio> you're welcome :)
2024-10-01 17:41:13 <mio> ah. just noticed it went through on edge after a few tries
2024-10-01 18:01:35 <fossdd[m]> algitbot: retry master
2024-10-01 18:47:05 <mio> algitbot: retry master
2024-10-01 18:47:41 <mio> okay, good
2024-10-01 18:54:40 <mio> almost done with dnssec-tools, just need to adjust something embedding rpath
2024-10-01 19:21:59 <mio> algitbot: retry 3.17-stable
2024-10-01 19:45:58 <mio> algitbot: retry 3.19-stable
2024-10-01 19:46:09 <ikke> algitbot: retry master
2024-10-01 19:46:53 <ikke> mio: oh, thanks, was not every retrying the right branch :P
2024-10-01 19:49:04 <mio> lol np
2024-10-01 20:30:49 <mio> algitbot: retry master
2024-10-01 20:33:27 <ikke> algitbot: retry master
2024-10-01 20:45:36 <mio> algitbot: retry master
2024-10-01 23:14:11 <mio> algitbot: retry master
2024-10-01 23:28:56 <mio> algitbot: retry master
2024-10-01 23:30:32 <mio> ^ needs a bump of libc crate to have a chance of building successfully on loongarch64
2024-10-01 23:30:55 <mio> guess no testing/ ci for loongarch64 to catch that
2024-10-01 23:31:12 <mio> s/ci/ci at the moment/
2024-10-01 23:41:29 <mio> tried to notify the maintainer, hopefully it will be fixed
2024-10-01 23:50:49 <mio> s/will/could/
2024-10-02 04:28:56 <cely> algitbot: retry master
2024-10-02 06:05:32 <cely> algitbot: retry master
2024-10-02 06:39:03 <cely> algitbot: retry master
2024-10-02 06:58:13 <cely> algitbot: retry master
2024-10-02 15:11:45 <ikke> soo greeen
2024-10-02 15:12:26 <PureTryOut> love it
2024-10-02 15:31:21 <cely> algitbot: retry master
2024-10-02 18:36:29 <PureTryOut> ncopa: according to the git log you already tried to fix the fortify-headers issue that networkmanager is now failing on, did the package not build somehow?
2024-10-02 18:36:51 <PureTryOut> or do builders need to be manually updated for this? it does not seem to be installed by apk according to that build log
2024-10-02 18:37:34 <ncopa> dont know
2024-10-02 18:37:45 <ikke> https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/aports-build/aports-build#L197
2024-10-02 18:38:57 <ikke> Installed:                                Available:
2024-10-02 18:38:59 <ikke> fortify-headers-2.3.1-r4                = 2.3.1-r4
2024-10-02 18:39:01 <ikke> on armhf
2024-10-02 18:39:46 <ncopa> ok. we need help with this i think
2024-10-02 18:41:35 <PureTryOut> Huh, ok
2024-10-02 18:44:51 <ncopa> there is also https://build.alpinelinux.org/buildlogs/build-edge-loongarch64/community/networkmanager/networkmanager-1.48.10-r1.log
2024-10-02 18:45:12 <ncopa> and this https://gitlab.alpinelinux.org/Celeste/aports/-/jobs/1541735
2024-10-02 18:47:11 <ncopa> wrong channel
2024-10-02 18:50:40 <ncopa> algitbot: retry master
2024-10-02 21:21:57 <mio> algitbot: retry master
2024-10-02 21:22:31 <mio> algitbot: retry master
2024-10-02 21:39:25 <mio> algitbot: retry master
2024-10-02 21:40:01 <mio> algitbot: retry master
2024-10-02 21:40:37 <mio> algitbot: retry master
2024-10-02 21:41:38 <mio> algitbot: retry master
2024-10-02 22:05:54 <omni> I wonder if !72916 is enough
2024-10-02 22:06:51 <omni> nope, something more
2024-10-02 22:06:56 <omni> is missing
2024-10-03 00:57:12 <celie> omni: Will you be merging the fortify-headers fix?
2024-10-03 01:08:37 <celie> algitbot: retry 3.20-stable
2024-10-03 01:10:12 <omni> I would prefer if someone who knew what they were doing did
2024-10-03 01:11:08 <celie> I think it's fair game now, if it doesn't work, the whole upgrade may have to be reverted
2024-10-03 01:11:20 <celie> again
2024-10-03 01:12:28 <celie> algitbot: retry 3.20-stable
2024-10-03 01:22:18 <omni> perhaps you're right
2024-10-03 01:22:44 <omni> celie: what do you think of my backd^Wpatch then?
2024-10-03 01:26:09 <cely> I think that while it may not necessarily fix every aport, something is better than nothing
2024-10-03 01:27:35 <omni> I saw that my arti test upgade failed with the same fortify-headers issue
2024-10-03 01:28:51 <cely> It will fix quite a number of aports
2024-10-03 01:30:21 <cely> Maybe together with https://github.com/jvoisin/fortify-headers/commit/f2e7f24daa it will fix even more
2024-10-03 01:32:21 <omni> examples of things currently failing that that would fix?
2024-10-03 01:32:49 <cely> Maybe the warning in libindi, but now i see it's just a warning
2024-10-03 01:35:07 <cely> Anyway, i think in the end, the fortify-headers upgrade will have to be reverted, yet again, as the last time it was tried, we didn't have GCC 14, so we didn't have to deal with the interaction between fortify and GCC 14
2024-10-03 01:37:03 <cely> algitbot: retry master
2024-10-03 01:38:03 <cely> algitbot: retry master
2024-10-03 01:38:20 <cely> algitbot: 3.20-stable
2024-10-03 01:40:16 <omni> let's see then...
2024-10-03 01:45:43 <cely> algitbot: retry master
2024-10-03 01:46:41 <cely> algitbot: retry master
2024-10-03 01:48:31 <mio> looks like it worked?
2024-10-03 01:50:07 <cely> Probably not for libindi
2024-10-03 01:50:15 <cely> but that was expected
2024-10-03 01:50:32 <cely> At least some archs are now unblocked for community/
2024-10-03 01:54:00 <cely> algitbot: 3.20-stable
2024-10-03 01:54:03 <cely> algitbot: rerty 3.20-stable
2024-10-03 01:54:06 <cely> algitbot: retry 3.20-stable
2024-10-03 01:54:07 <cely> lol
2024-10-03 01:56:25 <cely> Great, armhf is also done
2024-10-03 01:56:27 <cely> algitbot: retry 3.20-stable
2024-10-03 01:56:35 <cely> algitbot: retry master
2024-10-03 01:58:37 <cely> and now armv7 too
2024-10-03 01:58:41 <cely> algitbot: retry master
2024-10-03 01:59:03 <cely> algitbot: retry master
2024-10-03 02:00:18 <cely> community/R will probably have to be built -U_FORTIFY_SOURCE
2024-10-03 02:00:50 <cely> main/rust seems alright now, at least on x86_64
2024-10-03 02:00:53 <cely> algitbot: retry master
2024-10-03 02:01:08 <cely> algitbot: retry master
2024-10-03 02:01:37 <cely> algitbot: retry master
2024-10-03 02:02:49 <cely> algitbot: retry master
2024-10-03 02:04:54 <mio> algitbot: retry master
2024-10-03 02:06:06 <mio> algitbot: retry master
2024-10-03 02:06:55 <mio> algitbot: retry master
2024-10-03 02:08:46 <cely> The other aport is probably indi-3rdparty
2024-10-03 02:09:38 <mio> okay
2024-10-03 02:21:19 <omni> cely: perhaps you're right, that that other upstream fortify-headers commit would fix that
2024-10-03 02:23:18 <cely> I don't think so
2024-10-03 02:23:23 <cely> It will fix the warning
2024-10-03 02:23:28 <cely> but not the FD_ISSET error
2024-10-03 02:25:06 <cely> Though i guess it's worth a try in the upgrade MR you just opened
2024-10-03 02:27:38 <omni> yeah
2024-10-03 02:29:45 <omni> oh, no, it was already applied
2024-10-03 02:30:53 <cely> Hmm, i would've expected it to silence the warning
2024-10-03 02:34:00 <cely> So, i think the consideration now becomes, does this issue need to be fix in libindi or fortify-headers
2024-10-03 02:45:31 <mio> algitbot: retry master
2024-10-03 02:47:05 <mio> algitbot: retry master
2024-10-03 03:07:26 <omni> the only thing I found when searching for "fortify-headers" and "FD_ISSET"
2024-10-03 03:11:37 <cely> Did you paste a link? I didn't see anything
2024-10-03 03:13:34 <omni> https://www.openwall.com/lists/musl/2024/08/19/4
2024-10-03 03:13:42 <omni> it got delayed
2024-10-03 03:15:43 <cely> Ok
2024-10-03 03:16:58 <cely> https://android.googlesource.com/platform/bionic/+/ref/heads/main/libc/include/sys/select.h#77
2024-10-03 03:17:10 <cely> There's a `const` there
2024-10-03 03:18:48 <cely> Ugh, typoed the link
2024-10-03 03:18:53 <cely> https://android.googlesource.com/platform/bionic/+/refs/heads/main/libc/include/sys/select.h#77
2024-10-03 03:21:47 <omni> I'm about to check out
2024-10-03 03:22:09 <omni> chimera also package fortify-headers 2.3.1 with patches https://github.com/chimera-linux/cports/tree/master/main/fortify-headers
2024-10-03 03:23:30 <omni> but not indilib
2024-10-03 03:28:24 <cely> Chimera uses Clang
2024-10-03 03:33:02 <omni> so they're to blame?
2024-10-03 03:35:17 <omni> https://github.com/jvoisin/fortify-headers/commit/fe149628eaae9748be08815d726cc56e8e492c73
2024-10-03 03:41:11 <cely> Blame what?
2024-10-03 03:42:02 <omni> I'm just not making sense, never mind
2024-10-03 03:42:29 <cely> I don't see FD_ISSET in that commit
2024-10-03 03:42:57 <cely> I think it is a new addition in this upgrade, but it is not from that commit
2024-10-03 03:54:24 <cely> algitbot: retry master
2024-10-03 03:57:45 <cely> algitbot: retry master
2024-10-03 03:59:17 <cely> algitbot: retry master
2024-10-03 04:00:06 <cely> algitbot: retry master
2024-10-03 04:03:05 <cely> algitbot: retry master
2024-10-03 04:07:47 <cely> algitbot: retry master
2024-10-03 04:27:25 <cely> algitbot: retry master
2024-10-03 04:34:51 <cely> algitbot: retry 3.20-stable
2024-10-03 07:15:55 <cely> algitbot: retry master
2024-10-03 07:18:05 <cely> algitbot: retry master
2024-10-03 07:22:17 <cely> algitbot: retry master
2024-10-03 13:01:41 <omni> ptrc: your fwupd-efi depends on py3-pefile that just got upgraded, it's probably fine
2024-10-03 13:09:10 <ptrc> omni: thanks for the notice ^^
2024-10-03 13:11:04 <PureTryOut> Uh, ok one of the deps is missing a rebuild...
2024-10-03 13:11:27 <omni> why were tests disabled for cloud-init?
2024-10-03 13:12:27 <PureTryOut> omni: oh shit I didn't mean to, that was for local testing. I'll undo it
2024-10-03 13:13:38 <omni> ok
2024-10-03 13:14:55 <ptrc> PureTryOut: you can use `ABUILD_BOOTSTRAP=1` env to skip tests
2024-10-03 13:15:06 <PureTryOut> oh thanks that's useful!
2024-10-03 15:24:28 <cely> Does that need a pkgrel bump?
2024-10-03 15:36:29 <ikke> Should be bumped to 7 
2024-10-03 15:37:18 <cely> What happened to 6?
2024-10-03 15:42:41 <ikke> that's the 'faulty' one
2024-10-03 15:42:58 <ikke> it got reverted  from 6 to 5
2024-10-03 15:43:02 <ikke> the new one should be 7
2024-10-03 15:43:46 <cely> Not really following
2024-10-03 15:43:52 <cely> 2.3.1-r6
2024-10-03 15:43:56 <cely> 1.1-r5
2024-10-03 15:43:57 <cely> Anyway, i've purged fortify-headers with repo-tools
2024-10-03 15:44:12 <ikke> Oh, sorry, you are right
2024-10-03 15:44:17 <ikke> Didn't take the version into account
2024-10-03 15:44:26 <ikke> ok, fine as well
2024-10-03 15:44:37 <cely> What will happen to the people that have already got 2.3.1 installed?
2024-10-03 15:44:45 <cely> apk won't downgrade without --available, right?
2024-10-03 15:44:49 <ikke> correct
2024-10-03 15:46:13 <cely> Ok
2024-10-03 19:07:35 <mio> algitbot: retry 3.20-stable
2024-10-03 21:56:54 <ptrc> algitbot: retry master
2024-10-04 02:13:08 <omni> dammit!
2024-10-04 02:13:18 <omni> I should have squashed that commit
2024-10-04 06:47:30 <ncopa> algitbot: retry 3.20-stable