On Sat, May 4, 2019 at 1:37 PM <ng0177@xxxxxxxxx> wrote: > > "dnf --releasever=30 --setopt=deltarpm=false distro-sync" does the trick. I wonder, if it could replace "sudo dnf -y system-upgrade download --releasever=30" or just complete it. distro-sync is an alternative to system-upgrade, there's pros and cons to it though so the later tends to be more suitable for most users. The former is useful to ensure you have the latest packages plus and changes like new package additions that may not get pulled in, or just as a cleanup mechanism like this. Peter > [pi@raspi ~]$ lsb_release -d;uname -r > Description: Fedora release 30 (Thirty) > 5.0.10-300.fc30.aarch64 > > On Fri, May 3, 2019 at 10:30 PM Peter Robinson <pbrobinson@xxxxxxxxx> wrote: >> >> On Fri, May 3, 2019 at 9:28 PM Peter Robinson <pbrobinson@xxxxxxxxx> wrote: >> > >> > > See below. Interestingly "sudo grub2-mkconfig" resulted in permission denied but "su" worked. Nevertheless, I am stilled faced w/ >> > >> > Well there's no F-30 kernels installed so it's booted as expected, >> > even if it's not what's desired! >> > >> > I would: >> > "rm -rf /var/cache/dnf/*" >> > "dnf upgrade --refresh" >> >> And if that doesn't give you a new kernel update try: >> >> "dnf --releasever=30 --setopt=deltarpm=false distro-sync" _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
