Hide Forgot
The following was filed automatically by anaconda: anaconda 14.22 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/yum/sqlutils.py", line 168, in executeSQLQmark return cursor.execute(query, params) File "/usr/lib/python2.7/site-packages/yum/history.py", line 405, in trans_data_pid_beg VALUES (?, ?, ?)""", (self._tid, pid, state)) File "/usr/lib/python2.7/site-packages/yum/history.py", line 496, in beg self.trans_data_pid_beg(pid, state) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1343, in runTransaction self.skipped_packages, rpmdb_problems, cmdline) File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 992, in _run self.runTransaction(cb=cb) File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 974, in run if self._run(instLog, cb, intf) == DISPATCH_BACK: File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 1730, in doInstall rc = self.ayum.run(self.instLog, cb, anaconda.intf) File "/usr/lib/python2.7/site-packages/pyanaconda/backend.py", line 286, in doInstall return anaconda.backend.doInstall(anaconda) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext self.moveStep() File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1190, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1211, in handleRenderCallback self.currentWindow.renderCallback() IntegrityError: trans_data_pkgs.tid may not be NULL
Created attachment 485969 [details] Attached traceback automatically from anaconda.
This is bizarre ... what version of Fedora/anaconda/yum is this? Is this reproducible ... what did you do to get it?
Created attachment 495932 [details] Attached traceback automatically from anaconda.
Created attachment 674238 [details] Attached traceback automatically from anaconda.
Created attachment 674239 [details] Attached traceback automatically from anaconda.
Installation error of fedora 14 on mac os x
Created attachment 674241 [details] Attached traceback automatically from anaconda.
Created attachment 674244 [details] Attached traceback automatically from anaconda.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.