#archlinux32 | Logs for 2023-06-13

[00:08:09] <sunshavi> girls: You know sometimes I cross-compile the archlinux-arm krnel on x86-64. But when i do that the scripts fail. Because scripts are compiled according to the host where the compilation is taken place
[00:08:58] <KitsuWhooa> :p
[00:09:02] <KitsuWhooa> whoops, sorry
[00:09:05] <sunshavi> girls: So I found several links about the issue. And It seems linaro has solved it using the variable KBUILD_SCRIPTROOT
[00:09:43] <sunshavi> girl: But I do not know exactly how to use that Var on the PKGBUILD
[02:31:46] -!- kiska3 has quit [*.net *.split]
[02:31:46] -!- heartburn has quit [*.net *.split]
[02:31:46] -!- KitsuWhooa has quit [*.net *.split]
[02:33:50] -!- KitsuWhooa has joined #archlinux32
[02:36:29] -!- heartburn has joined #archlinux32
[04:03:08] -!- abouvier has quit [Read error: Connection reset by peer]
[04:07:20] -!- drathir_tor has quit [Ping timeout: 240 seconds]
[04:08:58] -!- abouvier has joined #archlinux32
[04:19:57] -!- kiska3 has joined #archlinux32
[04:21:05] -!- drathir_tor has joined #archlinux32
[04:45:03] <girls> KitsuWhooa: this message means, you can restart your builder. The package, that it currently builds, is no longer needed, because there's a newer version in the buildlist, now.
[04:45:22] <KitsuWhooa> Ah
[04:45:34] <KitsuWhooa> A restart isn't needed though, right?
[04:45:43] <girls> yes
[04:46:42] <girls> this is only a shortcoming between the synchronous and asynchronous part of the builder
[04:47:07] <girls> the slave regularly pings the master about what it's doing, but this ping process does not have the power to abort the build
[04:47:32] <girls> mainly, because archbuild is sudo'ed to root, so kill would need root privilages, too
[04:55:28] <girls> sunshavi: the PKGBUILD is just a script, you can export a variable therein, if make needs it
[06:21:58] -!- drathir_tor has quit [Remote host closed the connection]
[06:27:31] -!- drathir_tor has joined #archlinux32
[06:42:42] -!- drathir_tor has quit [Remote host closed the connection]
[06:44:20] -!- drathir_tor has joined #archlinux32
[06:48:56] -!- drathir_tor has quit [Ping timeout: 240 seconds]
[06:49:11] -!- Loops213_ has joined #archlinux32
[06:54:32] -!- Loops213_ has quit [Quit: Leaving]
[07:00:53] -!- Loops213_ has joined #archlinux32
[07:20:15] -!- drathir_tor has joined #archlinux32
[07:32:00] -!- Loops213_ has quit [Ping timeout: 255 seconds]
[09:14:21] -!- finsternis has quit [Read error: Connection reset by peer]
[10:28:10] WHATYEARISTHIS is now known as T`aZ
[10:44:01] <sunshavi> girls: Those are the links that talk about that var. But I am not sure which value should be given to that variable https://termbin.com
[13:55:34] -!- abaumann has joined #archlinux32
[13:55:34] <buildmaster> Hi abaumann!
[13:55:35] <buildmaster> !rq abaumann
[13:55:35] <phrik> buildmaster: <abaumann> huh. then I suddenly have to finish and maintain it. ;-)
[13:56:06] <abaumann> archlinux32-keyring-v20230201.tar.gz ... FAILED (invalid public key 33CA3597B0D161AAE4173F65C17F1214114574A4)
[13:56:10] <abaumann> is it just me? :-)
[14:11:17] <abaumann> uh.. we build a lot.. and a lot fails :-)
[14:44:45] -!- Loops213_ has joined #archlinux32
[15:27:08] <abaumann> :: Import PGP key E4D41569196B1160, "TasosSah <arch32@tasossah.com>"? [Y/n] error: key "E4D41569196B1160" could not be looked up remotely
[15:27:20] <abaumann> oups, when installing fresh chroots
[15:27:53] <abaumann> maybe also a keyserver issue? is the key pushed to the ubuntu keyserver for instance
[15:27:56] <abaumann> ?
[15:28:34] <abaumann> let me import it into the keyring of the user calling build-packages
[15:29:17] <abaumann> nope.
[15:29:24] <abaumann> something is broken in the archlinux32 keyring
[15:30:57] <abaumann> yep, also calling core-staging-pentium4-build manually fails equally
[15:32:56] <abaumann> so, build slaves calling clean_chroot will fail afterwards..
[15:33:20] -!- abaumann has quit [Quit: leaving]
[15:54:20] -!- bdju has quit [Ping timeout: 268 seconds]
[15:54:30] <girls> yes, the new keyring is not yet build on arch32 :(
[15:56:07] -!- bdju has joined #archlinux32
[15:56:21] <girls> let's see, if thuringiabuild1 can do the trick :)
[15:56:59] <girls> abaumann: did you install the recent archlinux32-keyring on the host?
[15:57:09] <girls> I don't see clean-chroot failures on my boxes
[15:59:45] <girls> Finished making: archlinux32-keyring 20230609-1.0
[16:00:31] <girls> ok, the keyring should now be available :)
[16:12:06] -!- abaumann has joined #archlinux32
[16:12:07] <buildmaster> Hi abaumann!
[16:12:07] <buildmaster> !rq abaumann
[16:12:07] <phrik> buildmaster: <abaumann> I have a theory: Linux decided they want to take over the Windows market, but this is of course only possible by getting the same quality and bugs as Windows has.. ;-)
[16:12:21] <abaumann> Some preliminary pkgct repo clone --arch32 is available..
[16:13:28] -!- abaumann has quit [Client Quit]
[16:45:24] <girls> \o/
[17:41:27] -!- eschwartz has quit [Ping timeout: 265 seconds]
[17:55:39] -!- eschwartz has joined #archlinux32
[18:29:48] -!- abaumann has joined #archlinux32
[18:29:49] <buildmaster> Hi abaumann!
[18:29:49] <buildmaster> !rq abaumann
[18:29:49] <phrik> buildmaster: <abaumann> gogo-gadgeto-strace
[18:30:03] <abaumann> https://aur.archlinux.org
[18:30:05] <phrik> Title: AUR (en) - archlinux32-keyring (at aur.archlinux.org)
[18:30:20] <abaumann> well, those keys could be stale
[18:31:19] <abaumann> https://aur.archlinux.org
[18:31:21] <phrik> Title: AUR (en) - archlinux32-keyring-git (at aur.archlinux.org)
[18:31:25] <abaumann> has no conflict directive
[18:37:51] <abaumann> mmh. archlinux32-keyring in AUR and ours is conflicting too.
[18:38:13] <abaumann> ok, it's conflicting since 2017-11-19 00:03 (UTC), so I guess that's ok. :-)
[18:42:22] <abaumann> maybe it's an important information that I have to put archlinux32-keyring-git onto all hosts running build slaves..
[18:43:32] <abaumann> mmh. shouldn't archlinux32-keyring be in i486/stable?
[18:44:56] -!- drathir_tor has quit [Ping timeout: 240 seconds]
[18:46:04] <girls> a recent archlinux32-keyring is in core-testing for all architectures
[18:46:10] <girls> this should be the one to use
[18:46:18] <girls> I was not aware, that there is a keyring in aur
[18:46:31] <abaumann> me neither. and that it is quite stale too. :-(
[18:47:18] <abaumann> pushed archlinux32-keyring to i486/stable
[18:47:30] <girls> why?
[18:47:32] <abaumann> this might be some speciality of the 486 vms failing. I have to check.
[18:47:33] <girls> who needs that?
[18:47:41] <abaumann> me :-)
[18:47:44] <abaumann> to update the machines.
[18:47:45] <girls> ok, fine :D
[18:47:51] <abaumann> I might run them on testing or so..
[18:47:55] <abaumann> and not on stable.
[18:48:18] <girls> all good, the keyring is fine in core :)
[18:48:27] <girls> maybe do it for all architectures, though
[18:48:33] <abaumann> ok.
[18:48:49] <girls> otherwise, we will have surprises, when the first packages of KitsuWhooa hit extra/core and the keyring is still in core-testing :D
[18:49:02] <abaumann> true :-)
[18:49:13] <KitsuWhooa> The keyring package worked for me when I installed it
[18:49:15] <abaumann> but.. then he gets known to the community ;-)
[18:49:21] <abaumann> ah. good. :-)
[18:49:31] <KitsuWhooa> My builder tried to install a package of mine and complained about the key, so I did Syu and it fixed it
[18:50:50] <abaumann> I have to adapt some of my small helper scripts.. then I might even go back to Python issues.. :-)
[18:51:01] <girls> sounds like fun :D
[18:51:19] <abaumann> BTW: I think ArchlinuxARM also got hit by the git move.. I didn't see too many updates lately on ARM.
[19:02:46] <girls> can't say, I'm blocked on archlinuxArm updates for quite a while, because my arch build farm is broken since quite some time, too :'-(
[19:10:44] -!- drathir_tor has joined #archlinux32
[19:19:17] -!- abaumann has quit [Quit: leaving]
[19:21:44] -!- drathir_tor has quit [Ping timeout: 240 seconds]
[19:32:32] -!- drathir_tor has joined #archlinux32