#archlinux32 | Logs for 2023-02-04
Back
[00:03:15] -!- epony has joined #archlinux32
[01:13:56] -!- drathir_tor has quit [Remote host closed the connection]
[01:24:17] -!- drathir_tor has joined #archlinux32
[07:27:34] -!- abaumann has joined #archlinux32
[07:27:34] <buildmaster> Hi abaumann!
[07:27:34] <buildmaster> !rq abaumann
[07:27:35] <phrik> buildmaster: <abaumann> let me stop my slaves, they need a new-year cleaning anyway. :-)
[07:28:05] <abaumann> deep42thought: locking sounds good, the force-move didn't break things it seems, I didn't find any issues so far while updating machines..
[08:41:18] -!- drathir_tor has quit [Remote host closed the connection]
[08:45:30] <abaumann> mmh, just updating some more machines and I have issues with keys, I consider making FS32#318 an announcment (the double curl thingy from bill-auger)..
[09:01:55] -!- drathir_tor has joined #archlinux32
[09:48:52] -!- drathir_tor has quit [Remote host closed the connection]
[09:54:05] -!- drathir_tor has joined #archlinux32
[10:39:59] <abaumann> There is a small messup between glibc-libs and *linux*headers, so I retriggered linux kernel builds..
[10:40:16] <abaumann> ..and I'm trying to fix the Gnome issue (currently stuck in pipewire issues)
[13:09:34] <abaumann> sweet. the buildmaster fell apart again.. :-)
[13:11:00] <abaumann> https://buildmaster.archlinux32.org
[13:11:02] <phrik> Title: result of archlinux32 build master's sanity checksanity of the buildmaster's mysql database (at buildmaster.archlinux32.org)
[13:11:02] -!- abaumann has quit [Quit: leaving]
[14:29:08] -!- JerryXiao has quit [Quit: Bye]
[16:12:43] -!- cypa has joined #archlinux32
[16:13:25] <cypa> Hi, any chance to have x86-64 v1 build?
[16:21:08] <cypa> anyway my VIA Nano L2007 won't boot i486 iso-image
[16:22:03] <cypa> initrd to not see any disk/partitions
[16:22:14] <cypa> *do not
[16:23:56] <bill-auger> the "32" in archlinux32 stands for 32-bit - im quite sure there is not going to be 64-bit port of archlinux32 - that is archlinux
[16:26:17] <cypa> look upstream archlinux provide builds for x86-64-v2 which do not boot on older x86-64-v1 CPUs
[16:27:20] <cypa> so x86-64-v1 CPUs have no arhclinux 64 build option
[16:30:00] <T`aZ> wat
[16:32:00] <bill-auger> cypa: if the CPU is 64bit, then why would you want to run a 486 system?
[16:33:00] <bill-auger> archlinux32 also has ports for 686 and pentium4 - both of thoe are better supported than 486
[16:38:46] <cypa> https://gitlab.archlinux.org
[16:38:48] <phrik> Title: Provide a x86_64_v3 microarchitecture level port (!2) · Merge requests · Arch Linux / RFCs · GitLab (at gitlab.archlinux.org)
[16:39:43] <cypa> my VIA Nano L2007 do not boot archlinux or archlinux32 i686 it shows kernel panic
[16:41:05] <cypa> i486 archlinux32 is the only successfully booted initrd
[16:50:29] -!- JerryXiao has joined #archlinux32
[16:51:14] <pants> I don't think it's true that arch linux is built for x86_64-v2
[16:51:19] <pants> see e.g. https://bbs.archlinux.org
[16:51:21] <phrik> Title: [closed] Will Arch transition to x86-64-v2 CPU requirement? / Arch Discussion / Arch Linux Forums (at bbs.archlinux.org)
[16:55:33] <cypa> OK, maybe it is not, but mine show kernel panics something about MSR
[17:04:48] <pants> sounds like something to bring up with the arch kernel packager, or with the upstream kernel developers...
[17:22:29] -!- cypa has quit [Quit: leaving]
[17:24:32] <girls> In principle, I'm not against fetching more x86 architectures, that upstream arch neglects - even if they're not 32 bit. However, we would need to think of a new name, then :D and I think we're not yet at that point ;)
[17:25:22] <girls> abaumann: no idea, what the buildmaster did wrong, the database simply missed some packages that had been moved from (community-)staging to (community-)testing for i486.
[22:17:24] -!- drathir_tor has quit [Remote host closed the connection]
[22:27:35] -!- drathir_tor has joined #archlinux32
[22:33:33] -!- drathir_tor has quit [Remote host closed the connection]
[22:48:54] -!- drathir_tor has joined #archlinux32