** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not complete
To
This bug was fixed in the package zeitgeist - 0.8.1-1ubuntu1
---
zeitgeist (0.8.1-1ubuntu1) oneiric; urgency=low
* Merge with debian, remaining change:
- Build-dep on raptor2-utils instead of raptor-utils
zeitgeist (0.8.1-1) unstable; urgency=low
* New upstream release. Some
** Changed in: zeitgeist
Milestone: None => 0.8.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not complete
--
ubuntu-bugs ma
** Changed in: zeitgeist
Status: Triaged => Fix Committed
** Changed in: zeitgeist (Ubuntu)
Importance: Undecided => Low
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif) => J.P. Lacerda (jplacerda)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:zeitgeist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not complete
--
ubuntu-bugs mailing list
ubuntu-bugs@
Things have changed slightly:
I implemented Mikkel's suggestion of setting the version to -1 just
before an upgrade, and back to it's correct value afterwards. This is
only useful if an upgrade is killed: the upgrade can also fail due to a
raised OperationalError. If that is the case (regardless o
This has been (mostly) fixed.
I think that there are some possible improvements regarding schema upgrading /
database creation.
As Seif said in #9, to replicate this:
1) Backup activity.sqlite
2) Restart the daemon
3) While "Updating sql schema" kill the daemon
The problem, however, is that this
** Branch linked: lp:~jplacerda/zeitgeist/660307
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not complete
--
ubuntu-bugs mailing
** Changed in: zeitgeist
Milestone: 0.8.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not complete
--
ubuntu-bugs ma
** Changed in: zeitgeist
Milestone: 0.7.0 => 0.8.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not complete
--
ubuntu-bugs m
OK I think we can start by always backing up while doing an upgrade from n ->
n+1.
I don't know what a gzipped ttl file is so why not just copy the
activity.sqlite to another back_activity.sqlite?
After upgrade is done we need to check the DB if its properly built. If not we
try to recover from
Oh, and one point in I forgot to add in my previous comment - I don't
want to validate the DB on startup. That's just way too expensive -
and whas in fact one of the primary points when I implemented DB
versioning.
One thing we could do to easily, and almost freely, detect when we are
killed durin
However noble it may be I don't think we stand a realistic chance of
implementing a stable "repair" function if the DB corrupts at an
undefined point in the upgrade process. There are just *way* too many
variables if we have fx. 4 different DB schemes that can all intermix
and corrupt in different
So my take on this would be to check every table upon startup for validity.
This requires however that we know what current scheme the db is on how how the
structure would look like.
This means we need to store the table structures and compare them on startup.
We will be confronted with two scenar
http://paste.ubuntu.com/530852/ is a start of the fix
On Fri, Nov 12, 2010 at 8:42 PM, Seif Lotfy wrote:
> To replicate this
> 1) Backup the activity.sqlite DB
> 2) restart the daemon
> 3) while its saying "DEBUG:zeitgeist.sql:Updating sql schema" kill the
> daemon
>
> On Fri, Nov 12, 2010 at 8:
To replicate this
1) Backup the activity.sqlite DB
2) restart the daemon
3) while its saying "DEBUG:zeitgeist.sql:Updating sql schema" kill the
daemon
On Fri, Nov 12, 2010 at 8:13 PM, Seif Lotfy
<660...@bugs.launchpad.net>wrote:
> I manged to replicate this manually creating an invalid structure.
I manged to replicate this manually creating an invalid structure. Thank
you for the bug. We are on it.
** Changed in: zeitgeist
Status: Incomplete => Confirmed
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
** Changed in: zeitgeist
Milestone: None => 0.7.0
Sorry, the file doesn't exist any more, it was on another user's PC.
Does creating a file with the SQL above help in recreating it?
--
zeitgeist fails to run if its database structure is not complete
https://bugs.launchpad.net/bugs/660307
You received this bug notification because you are a membe
Do you mind attaching the broken activity.sql file for us to test with?
--
zeitgeist fails to run if its database structure is not complete
https://bugs.launchpad.net/bugs/660307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
I guess so... but in the particular case I found, it wouldn't create the
tables at all. The activity.sqlite file that wouldn't work at all had
only two tables, uri and schema_version:
sqlite> .schema uri
CREATE TABLE uri
(id INTEGER PRIMARY KEY, value VARCHAR UNIQUE);
CREAT
I found an issue...
The tables are generated if not existent on each startup
However if the table exists but is damaged or incomplete it wont overwrite
it
We can fix that by getting the columns for each table and replacing if
incomplete
Does that sound sane?
On Fri, Nov 5, 2010 at 4:49 AM, Rocko
No, I do not believe that is correct. The table is *not* created with
the next starting of zeitgeist - see note 2 in the original description:
2) Better yet, zeitgeist could create the necessary tables if its
database is invalid or perhaps backup the old database and create a new
one so it can ru
The problem is more difficult than that. If a table is not there it gets
created with the next starting of zeitgeist. So there should be another
explanation why the update failed... We need more info about the
issue... I will mark it as incomplete until we can actually reproduce
this bug.
** Chang
** Also affects: zeitgeist
Importance: Undecided
Status: New
--
zeitgeist fails to run if its database structure is not complete
https://bugs.launchpad.net/bugs/660307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
--
zeitgeist fails to run if its database structure is not complete
https://bugs.launchpad.net/bugs/660307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
25 matches
Mail list logo
