15:00:59 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:59 <zodbot> Meeting started Tue Aug 27 15:00:59 2019 UTC.
15:00:59 <zodbot> This meeting is logged and archived in a public location.
15:00:59 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:59 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:01:00 <pwhalen> #chair pwhalen pbrobinson jlinton
15:01:00 <pwhalen> #topic roll call
15:01:00 <zodbot> Current chairs: jlinton pbrobinson pwhalen
15:01:21 <pwhalen> Good morning folks, who's here today?
15:02:11 * jlinton waves
15:02:58 <pwhalen> howdy jlinton
15:03:00 * pbrobinson o/
15:03:05 * tdawson is sorta here.
15:04:48 <pwhalen> #topic 1) ==== Userspace Status  ====
15:04:54 <pwhalen> any new issues?
15:05:50 <pbrobinson> none I can think of
15:06:02 <pwhalen> #info No new issues reported.
15:06:15 <pwhalen> #topic 2) ==== Kernel Status ====
15:06:25 <pwhalen> #info F31: kernel-5.3.0-0.rc6.git0.1.fc31
15:06:25 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1364299
15:06:52 <pwhalen> I've started to look at rc6, nothing so far.
15:07:50 <pwhalen> has anyone else had a chance to do testing on their favourite board?
15:07:52 <pbrobinson> I'm running rc5 and rc6 across a number of devices and mostly looks sane
15:08:03 <jlinton> Other than the usual platform issues (DAWN) it seems to be working ok.
15:08:20 <pwhalen> excellent
15:08:48 <pwhalen> #info F30: kernel-5.2.10-200.fc30
15:08:48 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1364657
15:10:05 <pwhalen> The BeagleBone black isn't booting with 5.2
15:10:16 <pwhalen> #info Kernel oops on BeagleBone Black
15:10:22 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=1740605
15:10:24 <pbrobinson> I need to retest the db410c with both 5.2 and 5.3, there was issues therer
15:11:01 <pwhalen> the reporter also tested 5.3 on the BBB with the same result. Will try to track down where it broke
15:12:03 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:12:34 <pwhalen> #topic 3) ==== Bootloader Status ====
15:12:45 <pwhalen> #info uboot-tools-2019.10-0.2.rc2.fc31
15:12:45 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1364289
15:12:55 <pbrobinson> there's a rc3 building ATM
15:13:01 <pwhalen> new uboot available for testing
15:13:15 <pwhalen> #info uboot-tools-2019.10-0.3.rc3.fc31 (still building)
15:13:15 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1365901
15:13:23 <pwhalen> there's rc3 too
15:13:59 <pwhalen> This is hot off the presses so I havent had a chance to test at all. Will do so today
15:14:40 <pwhalen> any other bootloader news? issues?
15:15:06 <pbrobinson> we'll need to get this added into freeze
15:15:06 <jlinton> (more of a question) did we get a grub image for armv7?
15:15:42 <pbrobinson> jlinton: there is but it's got issues, I think we need some patches, there was a list of those sent out to I think cross-distro list
15:16:00 <pbrobinson> I need to have a look at that and see what our grub2 is missing
15:16:19 <pbrobinson> F-32 has been rebased to grub 2.04 upstream plus our remaining patch set
15:16:37 <pbrobinson> so that should be fine, although that doesn't help with f31
15:18:52 <pwhalen> #topic 4) ==== Fedora 31 ====
15:19:06 <pwhalen> #info Fedora 31 Beta Freeze is today!
15:19:34 <pbrobinson> yay (boo)
15:20:05 <pwhalen> #info AArch64 Xfce Desktop image added to F31/Rawhide. Testing appreciated!
15:20:19 <pwhalen> #info Fedora 31 Beta Blockers
15:20:20 <pwhalen> #link https://qa.fedoraproject.org/blockerbugs/milestone/31/beta/buglist
15:20:39 <jlinton> I've got a couple graphical systems, that I need to install with F31, I will try the hikey/etc in the next couple days
15:21:19 <pwhalen> we've not had a nominated compose for testing in some time.
15:21:50 <pbrobinson> jlinton: thanks
15:22:07 <pwhalen> The compose today failed due to dep issues
15:22:11 <jlinton> does that mean the composes are failing?
15:22:22 <pwhalen> yesterdays looked almost complete, not sure why it wasnt nominated
15:23:15 <pbrobinson> there was a library that soname bumped and sssd rebuild didn't land
15:23:22 <pwhalen> #info Workstation image for armhfp is fixed and should be available going forward.
15:23:49 <pwhalen> #info Server image for armhfp and aarch64 fixed last week.
15:24:08 <pbrobinson> nice
15:25:17 <pwhalen> any other F31 news? issues?
15:26:17 <pwhalen> #topic 5)  == EPEL ==
15:27:02 <pbrobinson> so RHEL with the RHEL-ALT had basically been EOL on aarch64 (and Power9) with the release of el8
15:27:15 <pbrobinson> so there's a proposal to kill aarch64 on EPEL
15:27:24 <pbrobinson> or EPEL on aarch64 for el7 even
15:27:28 <jlinton> right, which begs the question of where centos 8 is...
15:28:30 <tdawson> I've been told the official stance on CentOS 8 is "Any day now"
15:28:45 <pbrobinson> yes, that's the official stance
15:29:30 <jlinton> Yah, lots of the builds are named with "release"...
15:31:17 <tdawson> Is the EPEL committee asking your opinion pbrobinson? ... I'm just wondering if this is a statement giving a heads up, or wanting to start a conversation about whether it's a good idea or not.
15:31:33 <pbrobinson> no idea
15:31:42 <pbrobinson> I saw smooge's email, not had time to read it
15:31:55 <pbrobinson> I am not subscribed to EPEL mailing lists any more
15:32:58 <tdawson> https://pagure.io/epel/issue/74
15:33:58 <tdawson> Looks like it is still up in the air, and will probrubly be discussed at the EPEL board meeting, which is tomorrow.
15:34:32 <pwhalen> #info Dropping aarch64 from EPEL-7
15:34:38 <pwhalen> #link https://pagure.io/epel/issue/74
15:34:41 <pbrobinson> I'll attempt to get to it before then, feel free to tag me in the meeting
15:34:53 <tdawson> pbrobinson: Will do
15:35:15 <pwhalen> #topic 6)  == Open Floor ==
15:35:29 <pwhalen> Anything else for today?
15:36:07 <tdawson> I had someone ask me if we had thought of doing a RealTime arm spin.
15:36:16 <tdawson> Has that ever come up before?
15:36:56 <pbrobinson> tdawson: well the kernel team has a well defined policy on non upstream kernel patches
15:37:13 <pbrobinson> so RT is never an option until that happens no matter what the architecture
15:37:36 <pbrobinson> I would be interested to know the context though
15:38:23 <tdawson> They are currently using yocto but would rather be using Red Hat stuff.
15:38:44 <tdawson> They only have about 250 units though, so they know they aren't anything major.
15:39:38 <pbrobinson> ultimately there is upstream movement to finally get the RT patches up, I think an enabler for that will land in 5.4
15:42:09 <tdawson> Cool.  OK.  I honestly thought it had already landed, but we didn't talk too much about kernel, more about tools and minimizing things.
15:43:46 <pwhalen> Thanks all!
15:43:51 <pwhalen> #endmeeting