#archlinux32 | Logs for 2024-03-07

Back
[07:39:54] -!- drathir_tor has quit [Remote host closed the connection]
[07:50:32] -!- drathir_tor has joined #archlinux32
[09:19:01] -!- bdju has quit [Ping timeout: 264 seconds]
[10:01:27] -!- bdju has joined #archlinux32
[10:19:47] -!- bdju has quit [Ping timeout: 264 seconds]
[10:26:48] -!- bdju has joined #archlinux32
[10:35:13] -!- bdju has quit [Ping timeout: 264 seconds]
[10:35:57] -!- bdju has joined #archlinux32
[10:47:21] -!- bdju has quit [Ping timeout: 272 seconds]
[10:52:44] -!- bdju has joined #archlinux32
[11:04:51] -!- bdju has quit [Ping timeout: 260 seconds]
[11:10:57] -!- bdju has joined #archlinux32
[11:19:41] -!- bdju has quit [Ping timeout: 240 seconds]
[11:21:43] -!- bdju has joined #archlinux32
[11:34:13] -!- bdju has quit [Ping timeout: 272 seconds]
[15:50:43] <KitsuWhooa> I think I see the issue. python-build doesn't build.
[15:50:59] -!- bdju has joined #archlinux32
[17:41:38] -!- drathir_tor has quit [Ping timeout: 260 seconds]
[17:48:27] -!- drathir_tor has joined #archlinux32
[18:26:25] <KitsuWhooa> so, systemd can't be installed because it depends on dbus-units but dbus can't build because systemd can't be installe
[18:27:01] <KitsuWhooa> d
[18:33:03] <bill-auger> somewhat related. i should ask, do we think that arch32 can upgrade to mkinitcpio 38 in the near future - WRT https://archlinux.org
[18:33:03] <phrik> Title: Arch Linux - News: mkinitcpio hook migration and early microcode (at archlinux.org)
[18:33:49] <bill-auger> systemd will need to be rebuilt; but we tried and it is not possble to build systemd because arch32 is pythonically broken
[18:35:47] <bill-auger> i must ask though because it could cause breakage for us, if we do not know the exact day this will happen
[18:37:23] <bill-auger> i am freezing our i686 for now, to ensure that this will not happen; but if this wil not happen soon, i can switch the importer back on until then
[18:39:51] <bill-auger> i noticed mkinitcpio-38 on the "build list" on the packages website; but i dont know if that is significant - it should fail with the older systemd
[19:15:24] <KitsuWhooa> bill-auger: I don't think there's an exact answer to that
[19:15:40] <KitsuWhooa> Everything is so broken
[19:16:10] <KitsuWhooa> At some point it'll probably try to build it, and the planets will align and it'll go to staging
[19:16:13] <KitsuWhooa> But that's about it
[19:50:28] <bill-auger> ok i will consult the magic 8-ball occasionally, and confer with our resident astrologer
[19:53:34] <KitsuWhooa> I'm only now getting around to sorting out the dbus-broker situtation
[19:53:36] <KitsuWhooa> *situation
[19:54:19] <KitsuWhooa> I think what you can do is check for when all the packages get updated/built
[19:54:33] <KitsuWhooa> but I suspect only one of them will end up building and updating, and it'll cause even more chaos in staging
[20:00:48] <KillerWasp> bill-auger: I also depended on 8-ball my whole life, and it has led me to be very winner as I am now!!! HAHAHAHAHAHA!!!!!
[21:11:47] -!- dmc has joined #archlinux32
[21:22:49] <KitsuWhooa> well, llvm16 built
[21:23:01] <KitsuWhooa> hopefully this doesn't break anything
[21:45:50] <KitsuWhooa> clang doesn't build because of python :)
[22:32:15] -!- bdju has quit [Ping timeout: 272 seconds]
[22:33:46] -!- bdju has joined #archlinux32
[22:51:28] <KitsuWhooa> Okay
[22:51:33] <KitsuWhooa> bootstrapping python in 2024 requires rust
[23:14:13] <KillerWasp> lol
[23:16:11] <KillerWasp> in python it is using rust everywhere, not just for bootstrapping. I really don't understand this strange change. What happened to the pride of the snakes?
[23:18:11] <KitsuWhooa> I think I might be wrong