On Fri, 2018-07-13 at 09:06 -0700, Samuel Sieb wrote:
> On 07/13/2018 07:23 AM, Russel Winder wrote:
> > PS Is it correct that dnf works fine without the history database, and
> > seems not to recreate it?
>
> You will have lost your past history of dnf transactions. The next time
> you
On 07/13/2018 07:23 AM, Russel Winder wrote:
PS Is it correct that dnf works fine without the history database, and
seems not to recreate it?
You will have lost your past history of dnf transactions. The next time
you install, update, or remove something, it should create it again.
On Thu, 2018-07-12 at 20:42 +, Andre Robatino wrote:
> > accessing it). I don't suppose you kept a backup of the file? That
> > would be very helpful for investigating the problem...
>
> See https://bugzilla.redhat.com/show_bug.cgi?id=1598590#c4 .
It would seem that this is a possible reason
> accessing it). I don't suppose you kept a backup of the file? That
> would be very helpful for investigating the problem...
See https://bugzilla.redhat.com/show_bug.cgi?id=1598590#c4 .
___
test mailing list -- test@lists.fedoraproject.org
To
On Fri, 2018-07-06 at 07:43 -0700, Adam Williamson wrote:
>
[…]
> That's interesting, but rather odd, as it suggests that run as root dnf
> just *happens* to have a *different* issue involving the same file
> (since obviously, when run as root, it wouldn't have had any problem
> accessing it). I
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
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
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
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
On Thu, 2018-07-05 at 10:38 +0100, Russel Winder wrote:
> On Tue, 2018-07-03 at 20:14 -0700, Adam Williamson wrote:
> > On Sun, 2018-07-01 at 09:19 +0100, Russel Winder wrote:
> > > I wonder if this
> > > episode indicates that there should be work done to make sure that a
> > > broken
> > > dnf
On Thu, 2018-07-05 at 10:48 +0100, Peter Robinson wrote:
> On Thu, Jul 5, 2018 at 10:40 AM, Russel Winder wrote:
> >
> > Has anyone discovered a way forward for updating Fedora Rawhide given dnf
> > just
> > seg faults currently?
>
> Can you use rpm to just update it lmanually?
>
So far no.
On Thu, Jul 5, 2018 at 10:40 AM, Russel Winder wrote:
>
> Has anyone discovered a way forward for updating Fedora Rawhide given dnf just
> seg faults currently?
Can you use rpm to just update it lmanually?
> --
> Russel.
> ===
> Dr Russel Winder t:
Has anyone discovered a way forward for updating Fedora Rawhide given dnf just
seg faults currently?
--
Russel.
===
Dr Russel Winder t: +44 20 7585 2200
41 Buckmaster Roadm: +44 7770 465 077
London SW11 1EN, UK w: www.russel.org.uk
On Tue, 2018-07-03 at 20:14 -0700, Adam Williamson wrote:
> On Sun, 2018-07-01 at 09:19 +0100, Russel Winder wrote:
> > I wonder if this
> > episode indicates that there should be work done to make sure that a
> > broken
> > dnf can never be installed?
>
> How do you propose we do that?
Using a
On Wed, Jul 4, 2018 at 4:14 AM, Adam Williamson
wrote:
> On Sun, 2018-07-01 at 09:19 +0100, Russel Winder wrote:
>> I wonder if this
>> episode indicates that there should be work done to make sure that a broken
>> dnf can never be installed?
>
> How do you propose we do that?
Personally I would
On Sun, 2018-07-01 at 09:19 +0100, Russel Winder wrote:
> I wonder if this
> episode indicates that there should be work done to make sure that a broken
> dnf can never be installed?
How do you propose we do that?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora |
On Sun, 1 Jul 2018 10:21:40 -0700
stan wrote:
> 'chroot dnf update' worked for me the last time dnf was compromised
> in rawhide.
This can't be true. I remember using it, but that can't have been why,
because if dnf is borked in rawhide, it won't work.
On Sun, 01 Jul 2018 09:19:15 +0100
Russel Winder wrote:
> Sadly it seems the 3.0.2 and 2.7.5 packages cannot be installed due
> to various different broken dependencies, so simple upgrade or
> downgrade of dnf from the current state of the Fedora install is not
> possible.
>
> I know this is
On Sat, 2018-06-30 at 12:39 -0700, stan wrote:
> On Sat, 30 Jun 2018 16:57:47 + (UTC)
> George R Goffe wrote:
>
> > Is there a specific download site for the fix for this problem? I
> > wrote a bug report yesterday to the RedHat bugzilla "Bug 1596827 –
> > dnf non-functional after upgrade".
On Sat, 30 Jun 2018 16:57:47 + (UTC)
George R Goffe wrote:
> Is there a specific download site for the fix for this problem? I
> wrote a bug report yesterday to the RedHat bugzilla "Bug 1596827 –
> dnf non-functional after upgrade".
>
> Bug 1596827 – dnf non-functional after upgrade
You
Dirk,
Is there a specific download site for the fix for this problem? I wrote a bug
report yesterday to the RedHat bugzilla "Bug 1596827 – dnf non-functional after
upgrade".
Bug 1596827 – dnf non-functional after upgrade
Best regards,
George...
21 matches
Mail list logo
