sam...@sieb.net wrote on 22-MAY-2020 19:53:22.14
>On 5/22/20 2:29 AM, Jouk Jansen wrote:
>> dnf system-upgrade log --number=-1
>> .
>> May 21 15:57:09 vlinder dnf[1839]: texlive-a5comb
>> noarch 9:svn17020.4-19.fc32
On 5/22/20 10:29 AM, Neal Becker wrote:
Interesting, let me try that:
dnf system-upgrade log
The following boots appear to contain upgrade logs:
-- no logs were found --
Is that maybe because the upgrade was too long ago?
I would expect that it's part of the regular journal storage, so it
On 5/22/20 2:29 AM, Jouk Jansen wrote:
dnf system-upgrade log --number=-1
.
May 21 15:57:09 vlinder dnf[1839]: texlive-a5comb
noarch 9:svn17020.4-19.fc32 >
May 21 15:57:09 vlinder dnf[1839]: texlive-abbr
Interesting, let me try that:
dnf system-upgrade log
The following boots appear to contain upgrade logs:
-- no logs were found --
Is that maybe because the upgrade was too long ago?
On Fri, May 22, 2020 at 5:33 AM Ed Greshko wrote:
> On 2020-05-22 17:21, Jouk Jansen wrote:
> > [root@vleegert
Hi,
Oops I gave the command on the wrong machine. Now I get
dnf system-upgrade log --number=-1
.
May 21 15:57:09 vlinder dnf[1839]: texlive-a5comb
noarch 9:svn17020.4-19.fc32 >
May 21 15:57:09 vlinder dnf[1839]:
On 2020-05-22 17:21, Jouk Jansen wrote:
> [root@vleegert ~]# dnf system-upgrade log --number=-1
> Error: Cannot find logs with this index.
try just
dnf system-upgrade log
to get a list of available logs
--
The key to getting good answers is to ask good questions.
Samuel Sieb wrote on 22-MAY-2020 10:32:36.96
>On 5/22/20 12:23 AM, Jouk Jansen wrote:
>> I tried an upgrade form F31 to F32 using dnf command line. All went well and
>> I rebooted into the upgrade process. Here I got a freeze: After 20 hours
>> looking at "Starting system upgrade. This may take a
