Package: pootle
Version: 2.0.0-2
Severity: important
This is a subsidiary bug only currently seen if hitting earlier install
problems. But will appear as a fatal bug when upgrading from one 2.0.0
install to another.
Following any initial upgrade the pootle database may partially exist. The
upgrader scripts used on dpkg upgrade, and reconfigure currently fails with
the following trace:
Setting up pootle (2.0.0-2) ...
Traceback (most recent call last):
File "/usr/bin/django-admin", line 5, in <module>
management.execute_from_command_line()
File "/usr/lib/pymodules/python2.5/django/core/management/__init__.py",
line 353, in execute_from_command_line
utility.execute()
File "/usr/lib/pymodules/python2.5/django/core/management/__init__.py",
line 303, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/pymodules/python2.5/django/core/management/base.py", line
195, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/lib/pymodules/python2.5/django/core/management/base.py", line
222, in execute
output = self.handle(*args, **options)
File "/usr/lib/pymodules/python2.5/django/core/management/base.py", line
351, in handle
return self.handle_noargs(**options)
File
"/usr/lib/python2.5/site-packages/pootle_app/management/commands/initdb.py",
line 31, in handle_noargs
create_default_db()
File
"/usr/lib/python2.5/site-packages/pootle_app/management/commands/initdb.py",
line 43, in create_default_db
create_default_projects()
File
"/usr/lib/python2.5/site-packages/pootle_app/management/commands/initdb.py",
line 69, in create_default_projects
pootle.save()
File "/usr/lib/pymodules/python2.5/django/db/models/base.py", line 410,
in save
self.save_base(force_insert=force_insert, force_update=force_update)
File "/usr/lib/pymodules/python2.5/django/db/models/base.py", line 495,
in save_base
result = manager._insert(values, return_id=update_pk)
File "/usr/lib/pymodules/python2.5/django/db/models/manager.py", line
177, in _insert
return insert_query(self.model, values, **kwargs)
File "/usr/lib/pymodules/python2.5/django/db/models/query.py", line
1087, in insert_query
return query.execute_sql(return_id)
File "/usr/lib/pymodules/python2.5/django/db/models/sql/subqueries.py",
line 320, in execute_sql
cursor = super(InsertQuery, self).execute_sql(None)
File "/usr/lib/pymodules/python2.5/django/db/models/sql/query.py", line
2369, in execute_sql
cursor.execute(sql, params)
File "/usr/lib/pymodules/python2.5/django/db/backends/sqlite3/base.py",
line 193, in execute
return Database.Cursor.execute(self, query, params)
sqlite3.IntegrityError: column code is not unique
dpkg: error processing pootle (--configure):
subprocess installed post-installation script returned error exit status
1
Errors were encountered while processing:
pootle
E: Sub-process /usr/bin/dpkg returned an error code (1)
Workaround for now is to erase the new /var/lib/pootle/dbs directory
created by pootle 2.0 before the reconfigure/upgrade.
NP: once new users sign up through 2.0 this will cease to be an option as
their details will only exist in that db.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
