Re: Broken dnf from 06-30-2018

2018-07-06 Thread Adam Williamson
On Fri, 2018-07-06 at 12:33 +0100, Russel Winder wrote: > By pure fluke I ran "dnf check-update --refresh" not as root and got: > > RuntimeError: C++ std::exception: Failed to open backup database: > /var/lib/dnf/history/history-2015-04-01.sqlite > > Surprising in that I have run this command no

Re: Broken dnf from 06-30-2018

2018-07-06 Thread Adam Williamson
On Fri, 2018-07-06 at 11:57 +0100, Russel Winder wrote: > On Thu, 2018-07-05 at 12:49 -0700, Adam Williamson wrote: > […] > > > > But the new dnf doesn't break everywhere; I updated to it and didn't > > hit any of the reported issues. I'm sure the DNF developers *do* test > > it on their local mac

Re: Broken dnf from 06-30-2018

2018-07-06 Thread Russel Winder
By pure fluke I ran "dnf check-update --refresh" not as root and got: RuntimeError: C++ std::exception: Failed to open backup database: /var/lib/dnf/history/history-2015-04-01.sqlite Surprising in that I have run this command not as root before and it didn't fail, but the file was owned root:roo

Re: Broken dnf from 06-30-2018

2018-07-06 Thread Russel Winder
On Thu, 2018-07-05 at 12:49 -0700, Adam Williamson wrote: […] > > But the new dnf doesn't break everywhere; I updated to it and didn't > hit any of the reported issues. I'm sure the DNF developers *do* test > it on their local machines, but this is not some sort of cast-iron > guarantee that it wi