Ask Your Question

`dnf history info` results in python exception

asked 2014-04-05 14:35:42 -0500

updated 2014-09-28 17:10:02 -0500

mether gravatar image

The dnf history info command is almost rendered useless on my system by this problem; I don't know if it's an issue with dnf-0.4.19-1 package or just a misconfiguration on my system. It doesn't matter whether I use the command as noted at the beginning or if I append the transaction ID, the result is the same (for the most part).

Here's the last output, as an example, which starts off all right, but then spews out traceback lines about a missing argument to isinstance function in :

dnf history info
Transaction ID : 73
Begin time     : Sat Apr  5 13:18:59 2014
Begin rpmdb    : 3912:d632bcef55ab96c730f08f9cd14b5c7571c35d87
End time       :                          (0 seconds)
End rpmdb      : 3911:af036115f25fdd96e7c4b88b20262b35997fdc0b
User           : ilmostro <ilmostro>
Return-Code    : Success
Command Line   : remove mcstrans-debuginfo
Traceback (most recent call last):
  File "/bin/dnf", line 35, in <module>
    main.user_main(sys.argv[1:], exit_code=True)
  File "/usr/lib/python2.7/site-packages/dnf/cli/", line 242, in user_main
    errcode = main(args)
  File "/usr/lib/python2.7/site-packages/dnf/cli/", line 75, in main
    return _main(base, args)
  File "/usr/lib/python2.7/site-packages/dnf/cli/", line 124, in _main
  File "/usr/lib/python2.7/site-packages/dnf/cli/", line 1378, in run
  File "/usr/lib/python2.7/site-packages/dnf/cli/commands/", line 2280, in run
    ret = self.output.historyInfoCmd(extcmds)
  File "/usr/lib/python2.7/site-packages/dnf/cli/", line 1810, in historyInfoCmd
    self._historyInfoCmd(tid, pats)
  File "/usr/lib/python2.7/site-packages/dnf/cli/", line 1931, in _historyInfoCmd
    if not isinstance(old.tid):
TypeError: isinstance expected 2 arguments, got 1

However, based on my experience with yum and according to the dnf manpage-entry, I should be able to see transaction details for, e.g. transaction 73, by issuing dnf history info 73.

> dnf history info [<spec>...]
>     Describe  the given transactions. Each <spec> can be either a <transaction-spec>, which
> specifies a transaction directly, or a <package-name-spec>, which specifies a
> trans‐action by a package which it manipulated. When no
> transaction is specified describe what happened during the latest transaction.


looks like this might be a known issue with the dnf-0.4.19-1 package, judging by this bugreport.

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2014-04-05 15:57:53 -0500

The nightly build of dnf can be used until an update is released to the stable F20 repos.

$ cd /tmp/
$ wget

You will have to install it as root:

# rpm -Uvh dnf-0.5.0-99.613.20140405git78661a4.fc20.noarch.rpm

If, for some reason, that specific package is not found on the site at the time you try to download it, go to the top directory for the last successful build of DNF and seek it out in the folders. After that, dnf history info subcommands work as expected:

# dnf history info 74
Transaction ID : 74
Begin time     : Sat Apr  5 15:34:54 2014
Begin rpmdb    : 3911:af036115f25fdd96e7c4b88b20262b35997fdc0b
End time       :            15:34:55 2014 (1 seconds)
End rpmdb      : 3904:e8705a2eec754c1097df06363f8a52c26daf902a **
User           : ilmostro <ilmostro>
Return-Code    : Success
Command Line   : remove python3-dnf python3-dnf-plugins-core
Transaction performed with:
    Upgraded      dnf-0.4.19-1.fc20.noarch @updates
    Installed     rpm-4.11.2-2.fc20.x86_64 (unknown)
Packages Altered:
    Erase python3-dnf-0.4.19-1.fc20.noarch             @updates
    Erase python3-dnf-plugins-core-0.0.6-1.fc20.noarch @updates
    Erase python3-hawkey-0.4.12-1.fc20.x86_64          @updates
    Erase python3-iniparse-0.4-9.fc20.noarch           @fedora
    Erase python3-libcomps-0.1.4-4.fc20.x86_64         @fedora
    Erase python3-librepo-1.6.0-1.fc20.x86_64          @updates
    Erase rpm-python3-4.11.2-2.fc20.x86_64             @updates-testing

Alternatively, one could also try downgrading the dnf package; though, I'm not sure at what point (i.e. version) this issue arose. To downgrade the package:

# yum downgrade dnf
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2014-04-05 14:35:42 -0500

Seen: 322 times

Last updated: Apr 05 '14