2024-10-01 01:47:19 <qaqland> huajingyun: fix in !72792
2024-10-01 01:49:04 <cely> It's been merged
2024-10-01 01:49:27 <cely> Thanks to J0WI
2024-10-01 04:40:04 <ikke> 7 packages remaining
2024-10-01 04:42:02 <cely> Most with open MRs
2024-10-01 04:42:05 <mio> 6 ... "why is it always xsane" :)
2024-10-01 04:42:12 <mio> so haven't cycled the builder
2024-10-01 04:45:15 <mio> the main one left to unblock is dnssec-tools, asteroid-launcher is already bundled in the asteroid-* MR but it may take a few days for maintainer to complete it
2024-10-01 04:47:04 <mio> lipstick-asteroidos in the same MR is already temporarily disabled on loongarch64, if need be could ask for the same with asteroid-launcher
2024-10-01 04:47:51 <mio> the other 4 as cely said have MRs pending
2024-10-01 04:48:31 <mio> apt-dater cri-o libretro-daphne xsane
2024-10-01 22:21:22 <mio> last one needed to unblock testing/ is in the MR queue
2024-10-02 11:50:09 <ncopa> the build-edge-loongarch64 is done! \o/
2024-10-02 12:16:27 <ikke> \o/
2024-10-02 12:17:37 <mps> now can change /etc/apk/repositorirs to CDN
2024-10-02 12:37:10 <ncopa> and we can decomission the 	build-edge-tmp-loongarch64
2024-10-02 13:51:28 <mio> \o/
2024-10-02 16:02:03 <cely> Would now be the time to remove `allow_failure: true` for the Loongarch CI?
2024-10-02 16:02:19 <ikke> probably yes
2024-10-02 17:03:17 <cely> New fortify-headers broke Rust again: https://gitlab.alpinelinux.org/Celeste/aports/-/jobs/1541687
2024-10-02 17:05:18 <cely> As usual, ppc64le seems unaffected, and this time, s390x also seems unaffected
2024-10-02 17:05:40 <cely> I have a very strong suspicion that fortify-headers isn't being applied at all to ppc64le
2024-10-02 17:24:06 <cely> but that's for tomorrow
2024-10-02 17:24:10 <cely> Going AFK now, bye
2024-10-02 17:27:38 <ikke> o/
2024-10-02 17:40:54 <ncopa> which is the PR for that job?
2024-10-02 17:42:49 <celie> Back for a very short while, there is no PR, it is upgrade-rust-1.82 (the next release) on my fork of aports
2024-10-02 17:43:04 <ncopa> i pushed update to fortify-headers
2024-10-02 17:43:17 <ikke> celie: how is the pipeline triggered? For aports we only have pipelines for MRs
2024-10-02 17:43:39 <celie> Through glab
2024-10-02 17:44:46 <celie> I figured out an incantation for that a while ago, can give it to you tomorrow, if you're interested
2024-10-02 17:44:51 <ikke> ok
2024-10-02 17:45:30 <ikke> Curious how that works, because everything assumes there is an MR
2024-10-02 17:45:40 <celie> Anyway, i think rebuilding main/rust should also give you the same error, though maybe something could've changed as Rust 1.82 vendors LLVM19
2024-10-02 17:48:04 <celie> From memory, it is https://manpages.debian.org/unstable/glab/glab-ci-run.1.en.html with some --variables set
2024-10-02 17:48:35 <celie> Ok, AFK for real now, bye
2024-10-02 17:48:50 <ikke> aha, ok, so you then provide something like CI_MERGE_REQUEST_TARGET_BRANCH_NAME manually
2024-10-02 18:29:50 <clandmeter> ncopa: i guess you could add edge to releases.json?
2024-10-02 18:30:11 <ncopa> i guess i could
2024-10-02 18:30:22 <ikke> reason is that the new pkgs.a.o looks at that
2024-10-02 18:30:29 <clandmeter> pkgs should then auto update
2024-10-02 18:30:38 <clandmeter> i hope :)
2024-10-02 18:36:27 <ncopa> pushed new alpine-releases.conf.yaml
2024-10-02 18:38:22 <clandmeter> thx, lets see in a couple of minutes
2024-10-02 18:38:36 <clandmeter> well it will take a bit longer to process all pkgs
2024-10-02 18:48:34 <clandmeter> yup, loongarch is popping up on pkgs.a.o
2024-10-02 18:48:39 <ikke> nice
2024-10-02 18:49:14 <clandmeter> now i just hope it finished without errors
2024-10-02 18:49:23 <clandmeter> cause the logic is not perfect for larger updates
2024-10-02 18:49:33 <clandmeter> but similar to previous
2024-10-02 18:50:38 <clandmeter> ikke: fyi, if the update is partially failed, you could set update to true in the config. and it will not check the apkindex version and process the whole index again.
2024-10-02 18:50:54 <ikke> ok, good to kn ow
2024-10-02 18:51:27 <clandmeter> its not a big issue, cause when the index does get an update, it will continue where it was
2024-10-02 18:52:37 <clandmeter> oh this is not infra channel.
2024-10-03 01:08:07 <celie> Am i seeing this right, and the ppc64le builder is idle? That's why i suspect fortify-headers is not being applied on that arch, as i've seen many times that it is unaffected when other archs are erroring out on fortify..
2024-10-03 01:25:05 <cely> ikke: (Regarding `glab ci run`) Yes, i'm manually specifying that through --variables-env, along with CI_MERGE_REQUEST_PROJECT_URL and CI_PIPELINE_SOURCE