Bug 327061 (Joe) - TB815ccf7d sqlutils.py:148:executeSQLQmark:OperationalError: no such column: filelist
Summary: TB815ccf7d sqlutils.py:148:executeSQLQmark:OperationalError: no such column: ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: Joe
Product: Fedora
Classification: Fedora
Component: yum
Version: 7
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-10 23:13 UTC by Joe Earl
Modified: 2014-01-21 22:59 UTC (History)
5 users (show)

Fixed In Version: 3.2.8
Clone Of:
Environment:
Last Closed: 2007-12-07 03:31:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Saved bug file from error message. (1.40 KB, application/octet-stream)
2007-10-10 23:13 UTC, Joe Earl
no flags Details
error bug report (1.40 KB, text/plain)
2007-10-13 02:31 UTC, Joe Earl
no flags Details

Description Joe Earl 2007-10-10 23:13:01 UTC
Description of problem:
Received error while attempting to update Fedora after initial install from HTTP

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


How reproducible: 


Steps to Reproduce:
1.Started Software Updater
2.during initial stage of checking for dependencies
3.have shutdown and rebooted and still have the error
  
Actual results:


Expected results:


Additional info:

Comment 1 Joe Earl 2007-10-10 23:13:01 UTC
Created attachment 223551 [details]
Saved bug file from error message.

Comment 2 Jeremy Katz 2007-10-10 23:38:05 UTC
What's the output of 'rpm -q yum yum-metadata-parser'?

Comment 3 Joe Earl 2007-10-11 01:03:17 UTC
yum-3.2.0.1.fc7
yum-metadata-parser-1.1.0-2.fc7


Comment 4 Joe Earl 2007-10-13 02:21:38 UTC
Any additional help available on this error? I have wiped my harddrive clean and
reinstalled Fedora 7 with the Internet install and when I try to run the initial
updates which shows 209 package updates available I still get this same error.

Comment 5 Joe Earl 2007-10-13 02:31:39 UTC
Created attachment 226291 [details]
error bug report

Comment 6 Seth Vidal 2007-12-07 03:31:41 UTC
Is this still happening anywhere? The later versions of yum and
yum-metadata-parser have not shown this problem.


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