Bug 1198998 - dnf does not allow to recover from broken history database
Summary: dnf does not allow to recover from broken history database
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On: 1167239
TreeView+ depends on / blocked
Reported: 2015-03-05 09:59 UTC by Till Maas
Modified: 2018-05-29 14:36 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-02 09:46:09 UTC
Type: Bug

Attachments (Terms of Use)

Description Till Maas 2015-03-05 09:59:19 UTC
Description of problem:
the dnf history database got corrupted on a system, but there is no way to recove from this with dnf, e.g. dnf could just move the old one away and create a new one or at least allow to create a new one for example like dnf history new.

Version-Release number of selected component (if applicable):

Comment 1 Honza Silhan 2015-03-17 09:22:50 UTC
Thanks for the report. We're not able to recover everything but it should at least create the new one. Let's do this functionality into Swdb. In the meantime try `sqlite3 history-<date>.sqlite ".dump" | sqlite3 history-2015-03-17.db && rm history-<date>.sqlite`

Comment 2 Honza Silhan 2015-10-21 12:48:33 UTC
*** Bug 1266103 has been marked as a duplicate of this bug. ***

Comment 3 Fedora End Of Life 2015-11-04 10:04:50 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Christian Stadelmann 2015-11-04 10:31:46 UTC
This issue is still present on F23, see bug #1266103.

Comment 5 Fedora End Of Life 2015-12-02 09:46:14 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 udo 2018-05-25 10:03:06 UTC
And it was still present in Fedora 28.

Comment 7 udo 2018-05-29 14:36:54 UTC
You did not read my comment?
What process is this that is peformed at the end of each new fedora release?

Note You need to log in before you can comment on or make changes to this bug.