On 11/1/20 1:49 PM, Ed Greshko wrote:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log The following boots appear to contain upgrade logs: 1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28 2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29 3 / af5f137e166b43f29a0b569932d59c5b: 2019-04-30 19:33:19 29→30 4 / b906a0cf864c4d2ab51fac91b984a43b: 2019-11-01 21:52:50 30→31 5 / 996e59b22f50425d99b7392c3a1ba11c: 2020-04-18 11:05:18 31→32 6 / 0e48343cf87540db8aa7d984b9c804fd: 2020-10-30 20:08:59 31→32 7 / a8a091e4bb0345108199e0db1619f306: 2020-10-30 20:13:51 31→32 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
Well #8 is what you want to look at. "man dnf" will help you choose it.
But, something odd. You say you want to go to F33. But your entry shows
8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32 <------------
While one would expect
2 / b1f88aab19d4444c9deb9aef2c8a2045: 2020-10-31 14:33:47 32→33 <-----------
I thought that was weird too. -1 did work and showed the error.
You are mixing 2 things?
journalctl isn't upgrade-log
He used the "system-upgrade log" command to get the list, so I assume he used the same one to see the log. "-1" is the correct option to see the most recent upgrade log. That doesn't explain why there's no 32->33 in the list, but it worked anyway.