2023-07-01 12:07:18 <ikke> algitbot: retry master
2023-07-01 12:15:45 <ikke> algitbot: retry master
2023-07-01 12:18:56 <ikke> algitbot: retry 3.18-stable
2023-07-01 12:45:25 <ikke> ^ mv: can't rename '/home/buildozer/aports/main/curl/pkg/curl/usr/share/fish/completions': No such file or directory
2023-07-01 12:46:28 <psykose> just abuild somehow not being upgraded yet
2023-07-01 12:46:35 <psykose> well, it happened cause it died before main finished before
2023-07-01 16:42:58 <ikke> algitbot: retry 3.17-stable
2023-07-02 09:10:03 <ikke> algitbot: retry master
2023-07-02 10:45:30 <ikke> algitbot: retry master
2023-07-02 14:12:53 <andypost[m]> algitbot: retry master
2023-07-02 15:34:46 <andypost[m]> algitbot: retry master
2023-07-03 05:20:14 <ikke> algitbot: retry master
2023-07-03 18:32:24 <ikke> algitbot: retry master
2023-07-03 19:03:55 <andypost[m]> algitbot: retry master
2023-07-03 22:48:26 <andypost[m]> algitbot: retry master
2023-07-04 01:13:32 <andypost[m]> algitbot: retry master
2023-07-04 04:48:23 <ikke> algitbot: retry master
2023-07-04 14:56:38 <psykose> ncopa: that requires rebuilds and they are broken
2023-07-04 14:57:02 <ncopa> hum, ok
2023-07-04 14:57:12 <psykose> on just aarch64 anyway
2023-07-04 14:57:18 <psykose> you can see by building efitools with it
2023-07-04 14:57:31 <psykose> the rebuilds part is because it emits .a's so you need to rebuild to do anything with the new version
2023-07-04 15:01:01 <ncopa> are there any upstream reports?
2023-07-04 15:01:33 <psykose> https://sourceforge.net/p/gnu-efi/bugs/37/
2023-07-04 15:01:45 <psykose> probably
2023-07-04 15:03:06 <psykose> https://github.com/rhboot/gnu-efi/commit/9e6cb2150bee08e83ec0cdfb8d6c2f83975dd3df might fix it
2023-07-04 15:09:47 <ncopa> how can i test it?
2023-07-04 15:12:52 <psykose> by rebuilding things against it
2023-07-04 15:14:53 <psykose> the patch doesn't fix it either, efitools built against it still fails on aarch64
2023-07-04 15:14:54 <psykose> unlucky
2023-07-04 15:15:03 <ncopa> actually, rebuilding against 3.0.17 appeared to work. but it was reported that the EFI binaries didnt run
2023-07-04 15:15:34 <ncopa> ah, it didnt actually build efitools. you're right
2023-07-04 15:16:13 <ncopa> the backport fix broke armv7: /home/buildozer/aports/main/gnu-efi/src/gnu-efi-3.0.17//gnuefi/crt0-efi-arm.S:145: Error: cannot represent BFD_RELOC_16_PCREL relocation in this object file format
2023-07-04 15:16:16 <psykose> yea
2023-07-04 16:40:00 <ikke> algitbot: retry master
2023-07-04 16:40:04 <ikke> algitbot: retry 3.18-stable
2023-07-04 16:40:30 <psykose> the aarch64 one too
2023-07-04 16:41:03 <ikke> algitbot: retry 3.18-stable
2023-07-06 10:27:18 <ikke> algitbot: retry master
2023-07-06 12:22:08 <ikke> better than stop fixing
2023-07-06 14:32:12 <ikke> algitbot: retry 3.17-stable
2023-07-07 05:11:08 <ikke> algitbot: retry master
2023-07-07 10:21:52 <ikke> algitbot: retry master
2023-07-08 05:12:18 <ikke> algitbot: retry master
2023-07-08 05:19:50 <psykose> love how the exact same firefox build of the same version with the same settings passes but that one doesn't
2023-07-08 05:21:24 <psykose> ah yes
2023-07-08 05:52:17 <ikke> algitbot: retry master
2023-07-08 05:59:32 <psykose> algitbot: retry master
2023-07-08 06:11:26 <ikke> still fails
2023-07-08 06:12:15 <psykose> ah right
2023-07-08 06:12:17 <psykose> now i remember
2023-07-08 07:43:24 <ikke> 
ACTION looks forward to the next revert :P

2023-07-08 07:44:18 <psykose> nah
2023-07-08 07:44:22 <psykose> can't think of any others
2023-07-08 07:44:25 <psykose> well
2023-07-08 07:44:27 <psykose> maybe ghc broke
2023-07-08 07:45:27 <psykose> seems ok
2023-07-09 06:29:55 <ikke> algitbot: retry master
2023-07-11 09:36:21 <mps> psykose: it build fine in my lxc
2023-07-11 09:36:41 <psykose> you had bash in your lxc then, probably
2023-07-11 09:37:25 <mps> ah yes
2023-07-11 09:37:53 <mps> strays from something
2023-07-11 09:39:58 <mps> anyway u-boot have EXTRAVERSION = -rc6 in Makefile, uhm
2023-07-11 09:40:23 <psykose> you could just `make EXTRAVERSION=` to not set it
2023-07-11 09:57:20 <mps> psykose: I posted your fix for u-boot on their irc channel
2023-07-11 09:58:24 <psykose> i didn't check if it actually works haha
2023-07-11 09:58:31 <psykose> generally that works for make tho
2023-07-11 10:07:33 <mps> I tested it on aarch64 without bash and it worked
2023-07-11 11:28:24 <ikke> algitbot: retry master
2023-07-11 11:29:22 <ikke> psykose: ^?
2023-07-11 11:29:29 <ikke> complains about patch files not being able to be read
2023-07-11 11:31:42 <ikke> checksum failures
2023-07-11 11:51:46 <psykose> ah right
2023-07-11 11:51:56 <psykose> forgot to update that part
2023-07-11 12:50:00 <ikke> just s390x and rv64 left
2023-07-11 13:50:47 <ikke> rust removed from everything except rv64
2023-07-11 13:51:20 <ikke> although, I can just remove the dep from world, it will be cleaned up once built :)
2023-07-11 13:51:31 <ikke> so, removed everywhere again
2023-07-11 13:51:40 <ncopa> so rust moved to main?
2023-07-11 13:53:27 <ikke> ncopa: yes
2023-07-11 14:40:27 <ncopa> awesome! opens up for writing alpine tooling in rust
2023-07-11 14:44:32 <psykose> everything set for anything kernel/mesa related too, though ofc those have their own challenges eventually given the versioning stuff
2023-07-11 14:44:41 <psykose> next lts is hopefully good
2023-07-12 07:21:24 <ikke> algitbot: retry master
2023-07-13 07:11:02 <ikke> algitbot: retry master
2023-07-13 07:29:01 <ikke> algitbot: retry master
2023-07-13 07:45:11 <ikke> algitbot: retry master
2023-07-13 07:45:18 <ikke> litespeed fails on missing libopenssl.a
2023-07-13 07:45:24 <ikke> libssl.a*
2023-07-13 07:46:11 <psykose> nah it fails before that
2023-07-13 07:46:39 <ikke> -Wdangling-pointer
2023-07-13 08:32:14 <psykose> yeah it's just werror being set in general on the ancient vendored copy of boringssl
2023-07-13 10:01:53 <psykose> algitbot: retry master
2023-07-14 14:45:59 <ikke> algitbot: retry master
2023-07-22 20:07:44 <andreasare> ciao a tutti
2023-07-22 20:16:49 <psykose> github moment
2023-07-25 17:34:33 <psykose> huh
2023-07-25 17:34:51 <psykose> ikke: can you `apk policy g++` on the builder
2023-07-25 17:35:14 <psykose> i can run this same thing fine with the compiler from the repos that just uploaded and it passes lol
2023-07-25 19:20:09 <psykose> ikke: those also fail because of the g+s on ~ on the builder which should probably not be there
2023-07-25 19:20:49 <ikke> That's set by default by something, iirc adduser 
2023-07-25 19:21:49 <psykose> yeah, though we unset it everywhere after
2023-07-25 19:22:03 <psykose> not sure why it got re-set actually
2023-07-25 19:23:51 <psykose> could you also run the `apk policy gcc g++` on aarch64
2023-07-25 19:46:24 <ikke> psykose: https://tpaste.us/KEZn
2023-07-25 19:47:02 <ikke> psykose: these builders were created from scratch again
2023-07-25 19:47:46 <psykose> ah
2023-07-25 19:47:47 <psykose> yeah
2023-07-25 19:48:01 <psykose> ikke: it didn't upgrade
2023-07-25 19:48:13 <psykose> -r1 is the new one
2023-07-25 19:48:18 <psykose> but it has r0
2023-07-25 19:48:26 <psykose> why does apk upgrade at the end of main/ not upgrade it
2023-07-25 19:48:35 <psykose> gotta debug that
2023-07-25 19:48:46 <ikke> apk says latest available is r0
2023-07-25 19:48:59 <psykose> also for the g+s you have to run `chmod -R g-s ~`, should do it since there's quite a few tests that break with it
2023-07-25 19:48:59 <psykose> hmm
2023-07-25 19:49:01 <psykose> but 
2023-07-25 19:49:04 <psykose> it uploaded -r1
2023-07-25 19:49:10 <ikke> after apk update it's available
2023-07-25 19:49:27 <psykose> uhh
2023-07-25 19:49:41 <ikke> psykose: I already ran that chmod command on aarch :-)
2023-07-25 19:49:41 <psykose> but how
2023-07-25 19:49:51 <psykose> 		log "upgrading system"
2023-07-25 19:49:51 <psykose> 		abuild-apk upgrade -U -a --quiet || log 'failed to apk upgrade'
2023-07-25 19:50:00 <psykose> this would update automatically at some point
2023-07-25 19:50:04 <psykose> with -U like after a minute at best
2023-07-25 19:50:55 <psykose> there's no failure case before that
2023-07-25 19:51:02 <psykose> it's the build and then it continues to that
2023-07-25 19:51:05 <psykose> why didn't it work
2023-07-25 19:51:06 <psykose> strange
2023-07-25 19:51:28 <ikke> did it finish the build sequence?
2023-07-25 19:52:56 <ikke> now it's on r1
2023-07-25 19:53:00 <ikke> without me doing anything
2023-07-25 19:56:05 <psykose> you ran the update
2023-07-25 19:56:10 <psykose> so it upgraded next round
2023-07-25 19:56:12 <psykose> just.. weird
2023-07-25 19:56:33 <psykose> i guess i could put `apk update && apk upgrade` in aports-build but like.. that should not be needed
2023-07-25 19:56:38 <psykose> there's some bug there :D
2023-07-25 20:05:53 <ikke> algitbot: retry master
2023-07-25 20:06:22 <psykose> thanks for fixes
2023-07-25 20:09:10 <ikke> np
2023-07-27 10:51:41 <ikke> algitbot: retry master
2023-07-27 10:52:11 <ikke> algitbot: retry master
2023-07-27 10:53:14 <ikke> strip: Unable to recognise the format of the input file `./usr/share/metricbeat/module/linux/rapl/msr_test'
2023-07-27 18:10:41 <ikke> Is firefox stuck in x86_64?
2023-07-27 18:11:38 <ikke> nope
2023-07-29 17:15:53 <ikke> algitbot: retry master
2023-07-29 17:37:54 <ikke> algitbot: retry master
2023-07-29 18:45:05 <ikke> algitbot: retry master
2023-07-29 19:03:47 <ikke> algitbot: retry master
2023-07-29 20:11:31 <ikke> algitbot: retry master
2023-07-30 16:37:56 <ikke> nmeum: was just looking at that package :D
2023-07-30 16:38:14 <ikke> need to update the sha1collissiondetection crate and was figuring out how to do that
2023-07-31 18:00:50 <ikke> algitbot: retry master