16:00:05 #startmeeting Fedora ARM and AArch64 Status Meeting 16:00:05 Meeting started Tue Jan 18 16:00:05 2022 UTC. 16:00:05 This meeting is logged and archived in a public location. 16:00:05 The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:05 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 16:00:05 #chair pwhalen pbrobinson coremodule jlinton 16:00:05 #topic roll call 16:00:05 Current chairs: coremodule jlinton pbrobinson pwhalen 16:00:12 * jlinton waves 16:00:13 Good morning folks, who's here today? 16:00:24 * coremodule is here. Good morning pwhalen, jlinton 16:00:35 howdy jlinton, coremodule 16:01:04 * pbrobinson is here 16:01:26 OK, the usual suspects are here, lets get started 16:01:35 #topic 1) ==== Userspace Status ==== 16:01:45 ANy new userspace issues? 16:02:02 #info F-36 mass rebuild for gcc-12 and friends due to kick off soon 16:03:30 #info Bug 2019579 - dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf' 16:03:47 https://bugzilla.redhat.com/show_bug.cgi?id=2019579 16:04:55 I saw nirik hit this on armhfp trying to provision the builders with F35 with updates enabled, I reproduced. It doesnt happen when using the release 16:05:13 Others have hit it on x86_64 16:05:31 oh yeah... 16:05:38 was gonna file that, thanks for doing so 16:08:40 np, someone beat me to it, affects x86 too. 16:09:13 C#18 "This happens when installing from Fedora 34 repository where /etc/resolv.conf created by NM is replaced by symlink created by systemd rpm post script." 16:09:45 Doesn't seem right, this was using the f35 repo 16:11:01 Any other issues? 16:12:34 #topic 2) ==== Kernel Status ==== 16:12:44 #info kernel-5.16.1-200.fc35 16:12:44 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1878500 16:13:32 I've started to test this, no issues so far. Not sure when its queued to hit F35 but I imagine soon. Be great if everyone could test it as well. 16:13:46 #info Please test and report any issues to the list or #fedora-arm. 16:15:07 I duplicated 2033016, the circular locking warning, I think I understand it a bit more now, no patch yet, soon hopefully 16:15:45 jlinton: excellent news, thanks again for looking at it 16:16:32 #topic 3) ==== Bootloader Status ==== 16:16:44 #info uboot-tools-2022.01-1.fc36 16:16:44 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1876475 16:17:26 iiuc, there is still an issue with the Raspberry Pi series 16:18:10 Anything else to mention? 16:19:53 #topic 4) ==== Fedora 36 ==== 16:20:14 as pbrobinson mentioned, mass rebuild to start soon 16:20:24 #info OpenQA testing - https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20220118.n.0&groupid=5 16:21:32 Todays compose is nominated, if you have some cycles testing is always appreciated - https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20220118.n.0_Summary 16:21:46 #info Bug 2038289 - systemd-boot-update.service fails to start on AArch64 16:21:46 #info Fixed in systemd-250.3-1.fc36 16:23:37 Anything else for F36? 16:24:05 #topic 5) == Open Floor == 16:25:07 the issue with RPi series and firmware should only be armhf, I believe arch64 is resolved 16:25:24 at least in my testing it is, and it may just be the rpi2 16:25:27 ok, I'll verify today 16:25:36 thx 16:25:53 I've tested with all the others on aarch64 with the latest firmware and they appear to be OK 16:26:16 If there's interest, I'd like to volunteer to work on Fedora ARM wiki instructions to get ARM boards working successfully. 16:27:29 walicki: sounds good, was the a board in particular? Wiki work is always welcome :) 16:28:37 we need to also move the generic arm install instructions to docs.fp.o and not the wiki 16:31:53 Right. walicki let us know what you want to work on in #fedora-arm 16:32:03 if nothing else, I'll close the meeting.. 16:33:18 #endmeeting