[Gnome-zeitgeist] jonas-zeta joined gnome-zeitgeist-users
Hello GNOME Zeitgeist Team, Jonas Zetterholm (jonas-zeta) has been added as a member of Friends of GNOME Zeitgeist (gnome-zeitgeist-users) by Jonas Zetterholm (jonas- zeta). Follow the link below for more details. https://launchpad.net/~gnome-zeitgeist-users/+member/jonas-zeta -- You received this email because you are an admin of the Friends of GNOME Zeitgeist team via the GNOME Zeitgeist Team team. ___ Mailing list: https://launchpad.net/~gnome-zeitgeist Post to : gnome-zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~gnome-zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 660415] Re: zeitgeist-daemon.py has a bad code structure
** Changed in: zeitgeist Status: In Progress = Fix Committed -- zeitgeist-daemon.py has a bad code structure https://bugs.launchpad.net/bugs/660415 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: The code of zeitgeist-daemon.py is very hard to read, let's restructure the code! (This is more like a reminder for myself to work on it, but I would like to fix it after bug #655164 has been fixed) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-10-25 09:55z (1 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-10-25 09:55z (2 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Merge] lp:~seif/zeitgeist/fix-643303 into lp:zeitgeist
okidoki, my take on this: I would like to have some kind of tests for the upgrade pathes, but please let's not do it like Seif tried in rev 1625. Therefor I suggest the following, let's merge this branch without rev 1625 into lp:zeitgeist, and then put some work into writing a testing framework for db schemes and upgrades. -- https://code.launchpad.net/~seif/zeitgeist/fix-643303/+merge/39201 Your team Zeitgeist Framework Team is requested to review the proposed merge of lp:~seif/zeitgeist/fix-643303 into lp:zeitgeist. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Gnome-zeitgeist] stascheck-fl joined gnome-zeitgeist-users
Hello GNOME Zeitgeist Team, levu (stascheck-fl) has been added as a member of Friends of GNOME Zeitgeist (gnome-zeitgeist-users) by levu (stascheck-fl). Follow the link below for more details. https://launchpad.net/~gnome-zeitgeist-users/+member/stascheck-fl -- You received this email because you are an admin of the Friends of GNOME Zeitgeist team via the GNOME Zeitgeist Team team. ___ Mailing list: https://launchpad.net/~gnome-zeitgeist Post to : gnome-zeitge...@lists.launchpad.net Unsubscribe : https://launchpad.net/~gnome-zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Merge] lp:~seif/zeitgeist/fix-665607-and-643303 into lp:zeitgeist
Seif Lotfy has proposed merging lp:~seif/zeitgeist/fix-665607-and-643303 into lp:zeitgeist. Requested reviews: Zeitgeist Framework Team (zeitgeist) I tried to fix the bug by simple detecting the current core schema and i and then iterating through all update scripts in form of 'core_i_i+1' its simple and straight forward. No looking for paths and leaving us to actually only worry about upgrade +1 increasing upgrade scripts. If the basic idea is OK I can propose for merging. Bugs fixed: #665607 and #643303 -- https://code.launchpad.net/~seif/zeitgeist/fix-665607-and-643303/+merge/39307 Your team Zeitgeist Framework Team is requested to review the proposed merge of lp:~seif/zeitgeist/fix-665607-and-643303 into lp:zeitgeist. === modified file '_zeitgeist/engine/sql.py' --- _zeitgeist/engine/sql.py 2010-10-19 13:54:12 + +++ _zeitgeist/engine/sql.py 2010-10-25 20:11:11 + @@ -92,20 +92,20 @@ def _do_schema_upgrade (cursor, schema_name, old_version, new_version): Try and upgrade schema `schema_name` from version `old_version` to - `new_version`. This is done by checking for an upgrade module named - '_zeitgeist.engine.upgrades.$schema_name_$old_version_$new_version' - and executing the run(cursor) method of that module + `new_version`. This is done by executing a series of upgrade modules + named '_zeitgeist.engine.upgrades.$schema_name_$(i)_$(i+1)' and executing + the run(cursor) method of those modules until new_version is reached - # Fire of the right upgrade module - log.info(Upgrading database '%s' from version %s to %s. This may take a while % - (schema_name, old_version, new_version)) - upgrader_name = %s_%s_%s % (schema_name, old_version, new_version) - module = __import__ (_zeitgeist.engine.upgrades.%s % upgrader_name) - eval(module.engine.upgrades.%s.run(cursor) % upgrader_name) - - # Update the schema version - _set_schema_version(cursor, schema_name, new_version) - + for i in xrange(old_version, new_version): + # Fire of the right upgrade module + log.info(Upgrading database '%s' from version %s to %s. This may take a while % + (schema_name, i, i+1)) + upgrader_name = %s_%s_%s % (schema_name, i, i+1) + module = __import__ (_zeitgeist.engine.upgrades.%s % upgrader_name) + eval(module.engine.upgrades.%s.run(cursor) % upgrader_name) + + # Update the schema version + _set_schema_version(cursor, schema_name, i+1) log.info(Upgrade succesful) def _check_core_schema_upgrade (cursor): @@ -113,7 +113,7 @@ # See if we have the right schema version, and try an upgrade if needed core_schema_version = _get_schema_version(cursor, constants.CORE_SCHEMA) if core_schema_version is not None: - if core_schema_version == constants.CORE_SCHEMA_VERSION: + if core_schema_version = constants.CORE_SCHEMA_VERSION: return True else: try: ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 643303] Re: Upgrade of the db schema strategy for version jumps
** Branch unlinked: lp:~seif/zeitgeist/fix-643303 -- Upgrade of the db schema strategy for version jumps https://bugs.launchpad.net/bugs/643303 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: We have to discuss how to support versions jump in the upgrade path of our db schema, like from (core, 0) to (core, 2). This becomes even more important when we reach the next version. For me there are two solution: 1.) write 'dummy' upgrade scripts, like core_0_2.py, which do not more than running core_0_1.run() and core_1_2.run() one after another 2.) add some magic to sql._do_schema_upgrade() which automatically tries to find an upgrade path and run the 'shortest' possible one. There is an issue with both solutions: right now the upgrade mechanism is designed in a way that after each data upgrade the schema upgrade is done. In both solutions the schema upgrade will be done *after* the full upgrade path. This can be handled by solution 1.) in the sanest possible way, the downside is that 1.) does not scale well for big numbers of schema versions around. Any Ideas? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 665607] Re: DB upgrades not backwards compatible (even when their are)
** Changed in: zeitgeist Status: Confirmed = Fix Committed -- DB upgrades not backwards compatible (even when their are) https://bugs.launchpad.net/bugs/665607 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: Not sure if we already fixed this, but just in case. INFO:zeitgeist.sql:Upgrading database 'core' from version 2 to 1. This may take a while CRITICAL:zeitgeist.sql:Failed to upgrade database 'core' from version 2 to 1: No module named core_2_1 ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 665607] Re: DB upgrades not backwards compatible (even when their are)
** Branch linked: lp:zeitgeist -- DB upgrades not backwards compatible (even when their are) https://bugs.launchpad.net/bugs/665607 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: Not sure if we already fixed this, but just in case. INFO:zeitgeist.sql:Upgrading database 'core' from version 2 to 1. This may take a while CRITICAL:zeitgeist.sql:Failed to upgrade database 'core' from version 2 to 1: No module named core_2_1 ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 643303] Re: Upgrade of the db schema strategy for version jumps
** Branch linked: lp:zeitgeist -- Upgrade of the db schema strategy for version jumps https://bugs.launchpad.net/bugs/643303 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Fix Committed Bug description: We have to discuss how to support versions jump in the upgrade path of our db schema, like from (core, 0) to (core, 2). This becomes even more important when we reach the next version. For me there are two solution: 1.) write 'dummy' upgrade scripts, like core_0_2.py, which do not more than running core_0_1.run() and core_1_2.run() one after another 2.) add some magic to sql._do_schema_upgrade() which automatically tries to find an upgrade path and run the 'shortest' possible one. There is an issue with both solutions: right now the upgrade mechanism is designed in a way that after each data upgrade the schema upgrade is done. In both solutions the schema upgrade will be done *after* the full upgrade path. This can be handled by solution 1.) in the sanest possible way, the downside is that 1.) does not scale well for big numbers of schema versions around. Any Ideas? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 612344] Re: Blacklist API sucks
with only a week left and no decision on the development method and API I postponed the bug to 0.7 ** Changed in: zeitgeist Milestone: 0.6 = 0.7 -- Blacklist API sucks https://bugs.launchpad.net/bugs/612344 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: Guys, GetBlacklist and SetBlacklist (without any signals) for an asynchrounous-by-nature API? Come on! How about changing it to Get, Add, Remove and a changed signal? That way it'd be actually usable... ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.1
Hello Zeitgeist Framework Team, On 2010-10-25 20:49z (9 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.3
Hello Zeitgeist Framework Team, On 2010-10-25 20:49z (12 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] Translation template import - zeitgeist in Zeitgeist Framework 0.5
Hello Zeitgeist Framework Team, On 2010-10-25 20:49z (14 minutes ago), you uploaded a translation template for zeitgeist in Zeitgeist Framework 0.5 in Launchpad. The template has now been imported successfully. Thank you, The Launchpad team ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
