On Wed, 2020-02-19 at 15:09 -0500, Michael H. Warfield wrote: : - <Snip> > > The armhfp images use extlinux and require grubby-deprecated. The > > aarch64 > > images shouldn't have it installed. > > Looking at your bz, I see you mention the aarch64 image has > > extlinux- > > bootloader > > and grubby-deprecated which I dont see. Did you install anything > > else > > on the > > image that could have pulled it in? Well now I'm really baffled. Based on the dnf logs on one of the affected systems, grubby-deprecated seems to have been pulled in about two weeks ago. That would account for the timing. But it was on a system that was upgraded to aarch64 and the 5.3.7 kernel months ago and been in operation and updated frequently since then. > I don't think so. I'll do a fresh raw image cut and see if there is > something in there without doing any updates. Since I have a mix of > systems, there may have been a cross contamination and most of the 64 > bit systems were built to upgrade and replace their 32 bit previous > Fedora versions on earlier systems built before the aarch64 was > stable > enough (Fedora 30? 29?). And I built one system from scratch and > updated it from there. Since these are in sort of a cooperative > cluster, it might be possible that cross over between what rpm > packages > were installed, but it hit all of the V3 systems and I only have a > couple of V2 systems left on-line (for testing) at this time that > require it and all of them have been updating successfully for > months. > > Just checked a fresh raw un-updated image and you're right, it's not > there. > > Now I gotta figure out how it got on all 6 of my V3 systems and > WHEN. > It's even on my reference card. So it got introduced into my build > process very early on. Maybe from an old backup. > > What's bad is that it's a required package for the armfp systems but > is > in the aarch64 repositories and yet can cause this problem if it's > accidentally installed. Maybe that should be should be removed from > the aarch64 repositories unless there's an actual documented need for > it with the caveats of what could happen? I think I've got them cleaned up with the various armfp systems "with" and the various aarch64 systems "without". I'm going to go back and flush my system config backup systems and reinitialize in case the culprit is lurking in there (which I highly suspect at this time). : - <Big snip> Mike -- Michael H. Warfield (AI4NB) | (o) +1 706 850-8773 | mhw@xxxxxxxxxxxx /\/\|=mhw=|\/\/ | (c) +1 678 463-0932 | http://www.wittsend.com/mhw/ ARIN whois: MHW9-ARIN | An optimist believes we live in the best of all PGP Key: 0xC0EB9675674627FF | possible worlds. A pessimist is sure of it!
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
