View Single Post
Old 11-11-2008, 02:35 AM   #3
alexxxm
Addict
alexxxm has a complete set of Star Wars action figures.alexxxm has a complete set of Star Wars action figures.alexxxm has a complete set of Star Wars action figures.alexxxm has a complete set of Star Wars action figures.
 
Posts: 223
Karma: 356
Join Date: Aug 2007
Device: Rocket; Hiebook; N700; Sony 505; Kindle DX ...
Quote:
Originally Posted by kovidgoyal View Post
what message does it crash with?
in today's update (ver. 0.4.104):

Code:
Upgrading database from version: 1
Upgrading database from version: 2
Upgrading database from version: 3
Upgrading database from version: 4
Upgrading database from version: 5
Upgrading database from version: 6
Upgrading database from version: 7
Upgrading database from version: 8
Upgrading database from version: 9
Upgrading database from version: 10
Upgrading database from version: 11
Traceback (most recent call last):
  File "/usr/bin/calibre", line 8, in <module>
    load_entry_point('calibre==0.4.104', 'gui_scripts', 'calibre')()
  File "build/bdist.linux-i686/egg/calibre/gui2/main.py", line 1290, in main
  File "build/bdist.linux-i686/egg/calibre/gui2/main.py", line 237, in __init__
  File "build/bdist.linux-i686/egg/calibre/library/database2.py", line 1163, in migrate_old
  File "build/bdist.linux-i686/egg/calibre/library/sqlite.py", line 106, in run
sqlite3.IntegrityError: PRIMARY KEY must be unique

after nuking the database directory content instead, I get this (strangely enough):
Code:
Upgrading database to version 2...
Upgrading database to version 3...
Upgrading database to version 4...
and calibre runs OK


alessandro
alexxxm is offline   Reply With Quote