On Wed, Jul 15, 2009 at 1:27 AM, wrote:
> Hey,
>
> I'm attaching a tarball with what's supposed to become Zeitgeist 0.2. Please
> test it (and thekorn, I'd be great if you could review the last commits I've
> done) and this afternoon I'll publish it if there's nothing wrong.
Hi Siegfried,
sorry f
and after fixing the typo I mentioned in my last mail the tarball is
working ok for me too.
So rebuild the tarball with my fix, and we should be good to go.
Well done everybody!
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@
Hi,
I've asked this question on #zeitgeist today, but somehow the answer
was not satisfying and I'm feeling we need to discuss this further.
Since a couple of days events are not represented as tuples with >10
elements, but are dicts now. This is how we define such dicts in
zeitgeist/dbusutils.py:
On Thu, Jul 16, 2009 at 12:10 AM, markus korn wrote:
> 1a.) although it is stated here otherwise, mimetype is not an optional
> entry, the engine itself will discard events without a mimetype
> 1b.) is mimetype really required for an event? Seif: as you are
> working on this applica
Public bug reported:
It looks like zeitgeist-daemon needs some love:
* remove engine object, it is not used in the daemon
* remove --no-tryicon. this option does not make any sense since the split of
the engine and the GUI (actually it should be the GUI which starts the daemon
if not already
Yes, writing tutorials, howtos and documentation in general is a good
idea. But instead of writing them in multiple places all over the
internet suggest creating this documentation in doc/ of lp:zeitgeist
using the restructured text format. We should then publish them on
http://docs.zeitgeist-proje
Public bug reported:
It would be nice to have a method in the DBus API to change the
annotations (tags/bookmarked) of an item. The item should be identified
by its URI. Something like this
ChangeAnnotation("file:///boo/bar/test.dat", {"tags": ["one", "two"],
"bookmarked": False})
The 2nd argumen
Added task for zeitgeist-filesystem as this project is waiting for this
bug to be fixed.
** Also affects: zeitgeist-filesystem
Importance: Undecided
Status: New
--
Add API method to change annotations of an item
https://bugs.launchpad.net/bugs/404915
You received this bug notification
cts: zeitgeist
Importance: Medium
Assignee: Markus Korn (thekorn)
Status: New
** Changed in: zeitgeist
Importance: Undecided => Medium
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
Define content and source types in one central pl
Public bug reported:
the dataprovider in _zeitgesit/loggers/dataprovider use strings like "File",
"Web" or "Note" as content types. Which does not match our database design
spec, which claims URIs for this values.
We need to change it and provide a script to convert entries in an existing DB
to
Public bug reported:
We should understand the 'bookmarked' attribute of an entry as an user
action, an action which can exclusively be set by any zeitgeist client.
As a conclusion of this dataprovider should not be able to set the
'bookmarked' flag for an new item.
** Affects: zeitgeist
Impo
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
Recently Used parsing error
https://bugs.launchpad.net/bugs/419867
You received this bug notification because you are a member of
Zeitgeist-Engine, which is a direct subscriber.
Status in Zeitgeist Engine: New
Can you please attach '~/.recently-used.xbel' to this bugreport. NOTE: this
file contains private data, so don't forget to switch on the privat flag for
this report.
If you feel uncomfortable to upload the whole file, please show me some lines
around line 1072 of this file.
Markus
--
Recently
Public bug reported:
I get this Traceback if firefox is not installed (a history db is not
found):
DEBUG:root:Updating database with new Firefox History items
Traceback (most recent call last):
File "/home/markus/zeitgeist/trunk/zeitgeist/../zeitgeist-datahub", line 111,
in _update_db_async
** Attachment added: "reproducer.py"
http://launchpadlibrarian.net/31773016/reproducer.py
** Branch linked: lp:~zeitgeist/zeitgeist/event-item-separation
--
sqlite error if 'application' attribute of an event is not given
https://bugs.launchpad.net/bugs/429255
You received this bug notificat
Public bug reported:
(This is a bug in the event-item-separation branch)
According to the definition of an event in zeitgeist/datamodel.py the
"application" attribute is optional.
The attached reproducer trys to add an event with 'application' not set, it
fails with the following error:
Traceb
Public bug reported:
(This is a bug in the event-item-separation branch)
The attached script adds a bookmarked event and a bookmarked item to the
database. But FindEvents for bookmarked events returns an empty list.
When you look at the database, it is also obvious that bookmarking of events is
** Attachment added: "reproducer.py"
http://launchpadlibrarian.net/31778338/reproducer.py
** Branch linked: lp:~zeitgeist/zeitgeist/event-item-separation
--
searching for bookmarked events is broken
https://bugs.launchpad.net/bugs/429314
You received this bug notification because you are a m
Public bug reported:
Right now zeitgeist is using pure python unittest plus a self written script to
run all tests. I think there are cases where we need a more powerful testing
framework, I suggest using nose [1].
Some examples:
* we are using temporary databases for our tests, it would be nic
** Description changed:
Right now zeitgeist is using pure python unittest plus a self written script
to run all tests. I think there are cases where we need a more powerful testing
framework, I suggest using nose [1].
Some examples:
* we are using temporary databases for our tests, it wou
To address this issue I've started an extension for firefox [0] which creates
zeitgeist events for every page-visit.
This is not stable yet, is not publicly announced, but if you would like to
give it a try I'm happy to get your comments.
Once we consider this extension stable, we should add it
Public bug reported:
The latest changes to the API demonstrate that we need an API version ID
and we also should make this ID accessible over DBus, something like:
>>> iface = DBusInterface()
>>> iface.getVersion()
'0.3'
Sample usecases:
* some (external) dataprovider might only work with some A
Public bug reported:
It should be possible to
* enable/disable some dataprovider (esp. useful for testing while developing
and debugging)
* define which dataprovider sends events for which application (right now it
is possible to have multiple DP per application, eg. are shipping a firefox
lo
I implemented a Properties interface in lp:~thekorn/zeitgeist/dbus.properties
The 'version' property is a read-only property which returns a version tuple.
Example usage:
>>> from zeitgeist.dbusutils import DBusInterface
>>> iface = DBusInterface()
>>> iface.version()
dbus.Struct((dbus.Int32(0),
Targeted to 0.3, because of the to be expected API change.
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Milestone: None => 0.3
--
Add engine version identifier a
Merge proposal is at
https://code.edge.launchpad.net/~thekorn/zeitgeist/dbus.properties/+merge/14188
Mikkel, did I implement the DBus Properties correctly, is it following
your proposal in comment #1?
--
Add engine version identifier and expose this ID over the DBus API
https://bugs.launchpad.ne
Public bug reported:
"test/resonance-engine-test.py" has some code to check if two Event
objects are the same. This code should not stay in the testcase, but
should be in the Event/Subject class, as this code is useful in other
places
** Affects: zeitgeist
Importance: Undecided
Sta
Public bug reported:
I know mikkel had a hard time at the hackfest trying to make this dbus API
tests unittests, but I think I found a solution for it.
Having this test in unittests too would allow us to create one big testsuite
for zeitgeist easily.
I will add a branch with unittests for the re
Public bug reported:
right now the relevancy-provider is loaded by default. Unfortunately this
extension is kind of buggy and not well tested, so in case of errors while
loading this extension the whole engine would fail to run.
We need a configurable plugin-system for our extensions, and for no
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist
Milestone: None => 0.3
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configurable
https://bugs.launchpad.net/bugs/483556
You received this bug notification beca
@mikkel, what do you think. Would this work for you?
** Branch linked: lp:~thekorn/zeitgeist/zeitgeist-
resonance_remote_unittest
** Changed in: zeitgeist
Milestone: None => 0.3
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zei
I added a branch with the general workflow I foresee, any opinions
(test/resonance-engine-extension-test.py
has an example)
Code still needs some work.
** Branch linked: lp:~thekorn/zeitgeist/zeitgeist-resonance_extensions
** Changed in: zeitgeist
Assignee: (unassigned) => Markus K
ok, sorry, pushed again, sth. went wrong the first time...
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper
unittests
https://bugs.launchpad.net/bugs/483550
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant fo
Sorry, just fixed the whitespace issue to keeps the diff as small as possible;
$SOMEONE told my editor to use tabs for indention in all zeitgeist branches,
the fact that we are using spaces in some parts of the source code is maybe
another bug.
I also renamed __public_methods__ to PUBLIC_METHODS
sorry, I wanted to link the demo/doctest directly here
http://bazaar.launchpad.net/~thekorn/zeitgeist/zeitgeist-resonance_extensions/annotate/head%3A/test/test-engine-extension.rst
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configurable
https://
merged
revno: 1299 [merge]
committer: Markus Korn
branch nick: zeitgeist-resonance
timestamp: Tue 2009-11-17 09:11:04 +0100
message:
* turned test/remote-test.py over to a proper unittest (LP: #483550
If we really need a millisecond accuracy in timestamps we should go with
INTEGER an use int(time.time()*1000) in python code.
But on the other hand I don't get why we need this at all. Events which happen
at the same time for the user will have a different timestamp, one example is:
A user opens
For me there is only one question left to fix this bug: How should
methods of extensions be accessible?
Right now they behave like direct members of the engine:
engine.some_extension_method()
There are also some possible alternative solutions:
engine.extensions.some_extension_method()
en
after thinking about it I think we should drop raising the KeyError.
Instead this we should return the id of the already existing event in the DB.
This way inserting 50 Events will always return a list of 50 ids.
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchp
Public bug reported:
I'm using this bug to track progress for an evolution eplugin sending
events to zeitgeist until I have a running version which is worth its
own project.
** Affects: zeitgeist
Importance: Wishlist
Assignee: Markus Korn (thekorn)
Status: In Pro
Public bug reported:
Running
python test/resonance-engine-test.py
I get one failed testcase
==
FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest)
** Changed in: zeitgeist
Status: New => Triaged
--
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist Engine:
** Changed in: zeitgeist
Status: In Progress => Fix Released
--
Add engine version identifier and expose this ID over the DBus API
https://bugs.launchpad.net/bugs/462890
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist F
I don't get why we need magic like ${PYTHON} at all. Isn't
/usr/bin/python always linked to the python version preferred by the
user? - so wn't fix for me too, unless there is a good reason I'm
missing.
** Changed in: zeitgeist
Status: Triaged => Incomplete
--
zeitgeist-0.2.0: using "env
No, this is not related to a blacklist mechanism discussed in bug 447417.
A blacklist system is on a per event basis whereas this bugreport asks for a
more global solution to manage dataprovider in general. This is esp. needed
when we have a gio dataprovider.
--
add a registry for Dataprovider
Only the "Tim" usecase in the description of this bugreport can be solved by a
blacklist system.
For the "Tina" usecase we need to find a way to apply filter on already
existing entries in the database to delete them
--
Zeitgeist should have any kind of system to protect users privacy
https://b
Public bug reported:
The old version of the engine is more verbose, has more logging
statements. For example it prints out if and how many objects are
inserted into the database. This information is useful when developing a
dataprovider to see if everything is working. We should re-add this
statem
@Mikkel, right. So maybe it is just about putting this into an usable
UI. But this is unrelated to this bugreport.
--
Zeitgeist should have any kind of system to protect users privacy
https://bugs.launchpad.net/bugs/447417
You received this bug notification because you are a member of
Zeitgeist-E
** Project changed: zeitgeist => zeitgeist-dataproviders
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification because you are a member of
Zeitgeist-Engine, which is subscribed to Zeitgeist Data Providers.
Status in Zeitgeist D
The attached branch has all my experiments, please see evolution/README
for a detailed report.
** Branch linked: lp:~thekorn/zeitgeist-dataproviders/evolution-
dataprovider
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification
Public bug reported:
Due to a missing pyxpcom package in ubuntu karmic the firefox extension
was hacked by files in the dbus communication process. this is VERY
inefficient. We should use XPCOM instead.
** Affects: zeitgeist-dataproviders
Importance: Undecided
Status: New
--
firef
Right, this was my initial idea.
But maybe using mozjs-dbus is much easier, I will try it later today.
Thanks for the link.
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
You received this bug notification because you are a member of
Zeit
sr/lib/pymodules/python2.6/dbus/service.py", line 252, in
_method_reply_return
reply.append(signature=signature, *retval)
OverflowError: Value 889653821 out of range for UInt32
** Affects: zeitgeist
Importance: High
Assignee: Markus Korn (thekorn)
Status: In Progress
**
** Changed in: zeitgeist
Status: In Progress => Fix Released
--
OverflowError in GetHighestTimestampForActor()
https://bugs.launchpad.net/bugs/489127
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in
Yeah, I'm ok with removing this method from the dbus API.
I would be cool if we could add a more flexible method to ZeitgeistClient, like
ZeitgeistClient.get_max_timestamp(self, actor=None,
manifestation=None, interpretation=None)
so you can not only search for the last timestamp for an actor,
** Branch linked: lp:~thekorn/+junk/test_dbus_direct_signal
--
Add event notification and subscription system
https://bugs.launchpad.net/bugs/488967
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgei
In the attached branch I tried to put together a sample dbus service
which *should* send directed signals, but somehow it is not working as I
expect it to work.
There are two scripts, service.py which starts the service, and
client.py (0|1), the client. starting the client with argument '1' means
maybe this screencasts help to understand whyt I mean ;)
** Attachment added: "out.ogv"
http://launchpadlibrarian.net/36195528/out.ogv
--
Add event notification and subscription system
https://bugs.launchpad.net/bugs/488967
You received this bug notification because you are a member of
Zeitge
Public bug reported:
For the time_range argument, there are two ways to query for all events ever
inserted in Zeitgeist,
1.) using TimeRange.until_now(), which translates to (0,
int(time.time()*1000))
2.) (0,0)
Strictly speaking both intervals means sth. completely different, and we should
IMHO setting the bug to invalid is the right decision. Just in case
anyone looks for a solution for it in the future, use sth. like this
class Test(object):
def __init__(self):
self.__value = 5
def get_value(self):
return self.__value
def set_value(s
Public bug reported:
Most of he metaclass magic in datamodel.py to register and define
Manifestation and Interpretation is not used anymore, we should remove
it and use much simpler (and more readable) code.
** Affects: zeitgeist
Importance: Undecided
Assignee: Markus Korn (thekorn
I'm working on fixing this bug in the attached branch
** Branch linked: lp:~thekorn/zeitgeist/simple.categories
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Milestone: None => 0.3.1
--
Make def
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
Make defenition of Manifestation and Interpretation in datamodel.py simpler
https://bugs.launchpad.net/bugs/492261
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant fo
Public bug reported:
When I request all events in my database (there are about 3000 of them)
I get an operational error:
In [1]: from zeitgeist.client import ZeitgeistDBusInterface
In [2]: iface = ZeitgeistDBusInterface()
In [3]: events = iface.FindEventIds((0,0), [], 2, 5, 0)
In [4]: len(
** Branch linked: lp:~zeitgeist/zeitgeist/apriori
--
"apriori": get most used (websites/notes/documents/etc...)
https://bugs.launchpad.net/bugs/494288
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status in Ze
I think I have an Idea of how to fix this bug, I will try to get some
code later today
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
External dataproviders playing along the recentlyused manager
https://bugs.launchpad.net/bugs/487297
You received this
Public bug reported:
At revision 1219 of lp:zeitgeist I added a unittest to test the
insert_hook feature (by using an extension which is blocking all events)
which fails with this error:
mar...@thekorn ~/devel/zeitgeist/trunk % python
test/resonance-engine-extension-test.py
DEBUG:zeitgeist.engin
This bug is very easy to fix, but it leads ton an important question: how do we
handle events which are not inserted (because of an error, or because of being
blocked).
Keep in mind, in our current design the clients depend on the order of items
InsertEvents returns, this allows them to map even
** Changed in: zeitgeist
Milestone: None => 0.3.1
--
AttributeError: 'NoneType' object has no attribute 'payload'
https://bugs.launchpad.net/bugs/495017
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status
I like this solution more than my proposal in my comment on the other
bugreport. But I still think it is not optimal because there is no reason to
distinguish between different reason of failure. The client will always get the
same result back no matter if this event was blocked by an extension,
I'm preparing a branch with the solution proposed by Mikkel, as this
solution has the best (making sense)/(breaking API) ratio.
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
What to do on failed or blocked event insertions?
https://bugs.launchpad.
** Branch linked: lp:~thekorn/zeitgeist/zero_as_error
--
What to do on failed or blocked event insertions?
https://bugs.launchpad.net/bugs/495179
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status in Zeitgei
thanks for your super fast code review.
I've changed the method name and fixed some engine-testcases (Exceptions are
not raised anymore, 0 is returned instead)
If nobody complains until lunchtime I will merge this branch into lp:zeitgeist.
This branch fixes only half of the issue, we also need a
Public bug reported:
Right now GetEvents raises a KeyError whenever any event is either not
found or blocked by an extension. As good as this solution was in case
of not found events it turns out to be bad for blocked events.
I think there are two possible solutions:
* adding a NULLEvent, a some
** Changed in: zeitgeist
Status: Confirmed => Fix Committed
--
What to do on failed or blocked event insertions?
https://bugs.launchpad.net/bugs/495179
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Stat
This is fixed by fixing bug 495179
** Changed in: zeitgeist
Status: New => Fix Committed
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
AttributeError: 'NoneType' object has no attribute 'payload'
https://bugs.launchpad.net/bug
/zeitgeist/null_event
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => In Progress
--
What to do if an event is not found or blocked when calling GetEvents (or its
engine equivalent)
https://bugs.launchpad.ne
I addressed both your comments in revision 1225, thanks for the review.
--
What to do if an event is not found or blocked when calling GetEvents (or its
engine equivalent)
https://bugs.launchpad.net/bugs/495392
You received this bug notification because you are a member of Zeitgeist
Developers,
Public bug reported:
sorry, for spamming you. but seif is unable to use our beloved launchpad
;)
** Affects: zeitgeist
Importance: Critical
Assignee: Markus Korn (thekorn)
Status: Won't Fix
--
small test
https://bugs.launchpad.net/bugs/496107
You received thi
** Changed in: zeitgeist
Status: New => Invalid
--
small test
https://bugs.launchpad.net/bugs/496107
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: Won't Fix
Bug descript
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a member of Zeitgeist
Developers, which is a direct subscriber.
St
** Changed in: zeitgeist
Status: New => Confirmed
** Changed in: zeitgeist
Importance: Undecided => High
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a member of Zeitgeist
Developers, which is a d
revno 1222 has a remote testcase for this bug, which fails.
A testcase which does the same on engine level works just fine.
** Branch linked: lp:zeitgeist
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a memb
** Changed in: zeitgeist
Assignee: Markus Korn (thekorn) => (unassigned)
--
small test
https://bugs.launchpad.net/bugs/496107
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framew
My last comment is kind of wrong, I adjusted the engine testcase in my
last commit to fail too
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a member of Zeitgeist
Developers, which is a direct subscriber.
St
I think this is a case where "where.may_have_results()" in resonance_engine.py
line 569 should return True (which results in find_eventids returning an empty
list), but it does not work this way.
I think someone with a full understanding of the logic going on there should be
able to provide a qu
I just added documentation for both NULL_EVENT and 0 in GetEvents
results.
--
What to do if an event is not found or blocked when calling GetEvents (or its
engine equivalent)
https://bugs.launchpad.net/bugs/495392
You received this bug notification because you are a member of Zeitgeist
Developer
Based on the feedback and the fact I added docs I decided to merge the changes
into lp:zeitgeist as I need this for another fix I'm working on right now (bug
462894)
revno: 1226 [merge]
committer: Markus Korn
branch nick:
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
add a registry for Dataprovider
https://bugs.launchpad.net/bugs/462894
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status
** Changed in: zeitgeist
Status: Confirmed => In Progress
** Branch linked: lp:~thekorn/zeitgeist/exclusive_clients
--
add a registry for Dataprovider
https://bugs.launchpad.net/bugs/462894
You received this bug notification because you are a member of Zeitgeist
Developers, which is the r
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
What to do if an event is not found or blocked when calling GetEvents (or its
engine equivalent)
https://bugs.launchpad.net/bugs/495392
You received this bug notification because you are a member of Zeitgeist
Developers, whi
After discussing this with Mikkel yesterday on IRC I came to the
conclusion that this bug is not an urgent one to fix, so I removed
myself as assignee.
** Changed in: zeitgeist
Assignee: Markus Korn (thekorn) => (unassigned)
--
add a registry for Dataprovider
https://bugs.launchpad.
I added a negation switch, using "!" as operator to some fields in the attached
branch.
There is also *one* testcase, I would like to add some more before merging
this, but I'm running out of time now.
Any comments?
** Changed in: zeitgeist
Assignee: (unassigned) => Ma
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
zeitgeist-daemon errors on startup
https://bugs.launchpad.net/bugs/497139
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Sta
** Changed in: zeitgeist
Status: New => Fix Committed
--
zeitgeist-daemon errors on startup
https://bugs.launchpad.net/bugs/497139
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Fram
Siegfried, do yo happen to know what's going on here. In my
understanding everything should work just fine, as notify.py is in
_zeitgeist/engine/Makefile.am
--
zeitgeist-daemon errors with "No module named notify"
https://bugs.launchpad.net/bugs/497140
You received this bug notification because y
Public bug reported:
To define some principles for existing and hopefully at some point new
contributors it would be cool to have a HACKING document.
Let's use this bugreport to collect a few things which should be mentioned
there:
* python version: zeitgeist is developed to be usable with pyt
Public bug reported:
I just added a new testcase to tests/remote-test.py, which is
unfortunatly failing:
mar...@thekorn ~/devel/zeitgeist/trunk % python test/remote-test.py
ZeitgeistRemoteAPITest.testGetMostUsedWithSubjects
:(
DEBUG:zeitgeist.engine:Creating eng
This bug is 'Won't fixed' until bug 497316 is fixed.
--
add get_most_used_with_subjects to client.py
https://bugs.launchpad.net/bugs/497188
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Fr
Public bug reported:
This is a kind of meta-bug to improve the documentation of zeitgeist, there are
several tasks we should try to adress:
* rename doc/dbus, it is not a pure DBus API doc anymore, we already have the
Datamodel documented etc.
* split the huge index.html in multiple smaller pa
1 - 100 of 424 matches
Mail list logo
