Adam Williamson composed on 2019-10-24 11:10 (UTC-0700):
On Thu, 2019-10-24 at 11:07 -0700, Samuel Sieb wrote:
> Felix Miata wrote:
> > $SUBJECT is the output.
> No, it's not. dnf prints out a lot more than that and to
find out
> what's happening, we need to see it.
How to find what you want I don't know. $SUBJECT is all that was on the screen
after the confirmation to proceed line.
http://fm.no-ip.com/Tmp/Linux/F/gx62b-f31jrnl.tgz has /var/log/journal.
http://fm.no-ip.com/Tmp/Linux/F/gx62b-f31dnflogs.tgz has /var/log/dnf.log*.
http://fm.no-ip.com/Tmp/Linux/F/gx62b-f31dnfdnf.tgz has /var/lib/dnf*.
I mean, excluding the kernel from the transaction is already kinda
out
of bounds. Just don't do that. :P
The new kernel gets used during the upgrade? If not, why should it be out of
bounds? It used to work. The "old" kernel 5.3.7-200.fc30 installed minutes
earlier
remains installed, and boots. I wouldn't expect 5.3.7-301.fc31 to be materially
different.
I'm in the habit of deciding precisely if and when to install a new kernel. They
consume a lot of disk space, precious at time when dnf is filling up the
filesystem with rpms. That time is usually after there are no other
updates/upgrades left to do, as a separate transaction, very often done without
the help of dnf, having been downloaded in advance elsewhere via upgrade from a
different host, saving precious bandwidth.
--
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata ***
http://fm.no-ip.com/