8 + // Blacklist Ubuntu One events...
9 + const gchar *actor;
10 + actor = zeitgeist_event_get_actor (event);
11 + if (strcmp(actor, dbus://com.ubuntuone.SyncDaemon.service) == 0)
12 + return;
13 + if (strcmp(actor, dbus://org.desktopcouch.CouchDB.service) == 0)
14
Another benefit of a separate function is also that we can unit test the
function directly as well.
--
https://code.launchpad.net/~rainct/zeitgeist/ignore-ubuntuone-actor/+merge/99986
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
** Changed in: activity-log-manager
Status: New = Fix Released
** Changed in: ubuntu
Status: Confirmed = Fix Released
** Changed in: ubuntu
Milestone: ubuntu-11.10 = ubuntu-12.04
--
You received this bug notification because you are a member of Activity
Log Manager, which is
1550+void Indexer::DropIndex ()
Are we not leaking db and enquire in this method?
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fts++/+merge/92022
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
___
Mailing list:
Functionally tested in Unity and working well. Unit tests passing. However -
There seems to be a fairly bad leak somewhere. Try repeatedly searching for
'u' or something like that and you'll see the memory consumption go up
fairly
fast.
Nope, sorry can't reproduce that, the first
Review: Approve
Looking good to me. I'd like someone else to +1 it before we merge though...
Outstanding work Michal!
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fts++/+merge/92022
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
Review: Needs Fixing
Functionally tested in Unity and working well. Unit tests passing. However -
There seems to be a fairly bad leak somewhere. Try repeatedly searching for 'u'
or something like that and you'll see the memory consumption go up fairly fast.
--
Review: Needs Fixing
1583+void Indexer::Flush ()
1584+{
1585+ db-flush ();
1586+}
This need to be Commit() and db-commit(). See
http://xapian.org/docs/apidoc/html/classXapian_1_1WritableDatabase.html#cbea2163142de795024880a7123bc693.
You should probably also surround it with a
I don't have any strong opinion for or against, but I think you need to
state some reasoning behind this? :-)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is the registrant for Zeitgeist Datahub.
https://bugs.launchpad.net/bugs/927938
Title:
Thanks for digging through this Doughy; I am not sure why Zeitgeist
searches were slowing down, they are usually very fast. I'll attach a
Zeitgeist task to check if anyone there have any ideas...
** Also affects: zeitgeist
Importance: Undecided
Status: New
--
You received this bug
On 2 February 2012 12:49, Siegfried Gevatter rai...@ubuntu.com wrote:
This doesn't need any changes in libzeitgeist, does it?
Not that I am aware of. It'll just be callers changing the strings
they pass for event/subject attributes. So no API changes.
--
You received this bug notification
** Changed in: libzeitgeist
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/884192
Title:
Update to shared-desktop-ontologies-0.8
** Branch linked: lp:~rainct/libzeitgeist/update-ontology-feb2012
** Changed in: libzeitgeist
Assignee: (unassigned) = Siegfried Gevatter (rainct)
** Changed in: libzeitgeist
Importance: Undecided = Medium
** Changed in: libzeitgeist
Status: New = In Progress
--
You received
Review: Approve
review approve
Didn't run the test suite, but the code looks clean
--
https://code.launchpad.net/~zeitgeist/zeitgeist/884193/+merge/84412
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
___
Mailing list:
Thanks teddy this looks just fine :-)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/722762
Title:
zeitgeist-daemon using ~100% of CPU
Status in Zeitgeist Framework:
Public bug reported:
The shared-desktop-ontologies that we use has recently released version
0.8. Among a range of other new classes it includes nfo:WebDataObject
which is of particular interest to us as it allows us to properly
describe web pages (since nfo:WebDataObject is not a subclass of
Public bug reported:
The problem is that nfo:FileDataObject (which we use as manifestation
for all files) has subclasses nfo:RemoteDataObject and
nfo:EmbeddedFileDataObject which we may not be interested in querying
for (at least, we're not in Unity). In Unity we qualify our queries by
Thanks ViViD this is most useful! If more people could attach traces
similarly (as described in my comment #48) that would be grand.
(or if you can attach an extra trace, ViVid, that is also good, as the
method I outlined will produce a dump from a random location in the
code)
--
You received
Thanks for confirming this. We need something to go on before we can
proceed with this issue though. Here's what you can do to help:
First install the needed debugging packages:
sudo apt-get install gdb python-dbg libxapian22-dbg
Then when you see the issue drop to a terminal:
pgrep -f
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Importance: Undecided = High
** Changed in: zeitgeist (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Status: New = Confirmed
** Changed in: zeitgeist
Importance: Undecided = High
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is
Can people open up ~/.cache/zeitgeist/daemon.log in a text editor and
see if there are any embarrassing, or confidential info in there, and if
not attach it to this bug please? (and if there are you can also just
delete those sections and attach it anyway)
--
You received this bug notification
Can people open up ~/.cache/zeitgeist/daemon.log in a text editor and
see if there are any embarrassing, or confidential info in there, and if
not attach it to this bug please? (and if there are you can also just
delete those sections and attach it anyway)
--
You received this bug notification
** Changed in: zeitgeist
Status: New = Confirmed
** Changed in: zeitgeist
Importance: Undecided = High
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/832092
Title:
So it looks like we get thrown off (or already is off?) the bus when
calling AddMatch on the session bus. There were some fixes in Zeitgeist
0.8.2 that may have also fixed this issue. Can anyone with
zeitgeist-0.8.2 (it got uploaded to Oneiric last weekI think)
confirm/deny?
** Also affects:
As Manish points out it would be helpful if people could test against
zeitgeist-0.8.2 which just got uploaded to Oneiric, but also with
zeitgeist-extension-fts-0.0.13 which also just got uploaded. There were
some fixes to the setup of the Xapian index that also may have caught
this one.
** Also
** Also affects: zeitgeist-extensions
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/757727
Title:
Zeitgeist-daemon memory
The attached branch, lp:~mhr3/zeitgeist-extensions/scheme-detection
Remove , by Michal stands a good chance of fixing this issue:
* It fixes a potential race, where we might end up trying to put data in a
corrupt index
* It removes the code branch where exception happens with some simpler
Ok. The Desktop team is pushing this to a PPA https://launchpad.net
/~ubuntu-desktop/+archive/ppa (ppa:ubuntu-desktop/ppa). Anyone willing
to test out the proposed fix will be of great help! Thanks in advance.
--
You received this bug notification because you are a member of Zeitgeist
Public bug reported:
The Xapian index for the FTS extension should add version metadata to
more easily and cleanly facilitate re-indexing when needed
** Affects: zeitgeist-extensions
Importance: High
Assignee: Michal Hruby (mhr3)
Status: In Progress
** Branch linked:
** Changed in: zeitgeist-extensions
Assignee: (unassigned) = Michal Hruby (mhr3)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/860362
Title:
FTS doesn't index paths
For reference this is the diff. I am not gonna apply it as is, as it'll
require a reindex in order to take effect:
=== modified file 'fts/fts.py'
--- fts/fts.py 2011-09-07 08:42:40 +
+++ fts/fts.py 2011-09-27 08:15:08 +
@@ -607,7 +607,7 @@
# usually web URIs, are indexed
There has been a range of fixes in the zeitgeist-extension-fts package.
Be sure that you are running the latest version and check if you can
reproduce. Running 'apt-cache policy zeitgeist-extension-fts' should
report 0.0.12.
--
You received this bug notification because you are a member of
I have an idea for a fix. You can help me know if it'll work or not by
running this command in a terminal:
dbus-send --print-reply --session --dest=org.gnome.zeitgeist.Engine
/org/gnome/zeitgeist/index/activity
org.gnome.zeitgeist.Index.ForceReindex
It will rebuild your Zeitgeist index (you will
Wow, that is an interesting stack trace. I assume you have less than
1,462,895,201 items in your index? ;-)
Looking at that monstrous doc id it would seem that this is either
memory corruption in the zg process or that it is a corrupted index,
that xapian somehow doesn't detect.
Can you report
Right @Izo, that's also ok. This means that it is rebuilding your index.
If you log out and back in, or reboot - do you then still see the bug?
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
With the latest fts release we fixed an index corruption bug that was
the most likely cause of this bug. Marking FixReleased
** Changed in: zeitgeist-extensions
Status: New = Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the
Ok. The updated crash reports looks sensible. I am still quite in the
dark about this, it could be a binding issue or something - do you
guys get it consistently or only occasionally?
So my guess work so far goes something like this: Consider the buggy
expression from the fts.py Python code:
** Changed in: zeitgeist-extensions
Milestone: None = fts-0.0.12
** Changed in: zeitgeist-extensions
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
** Changed in: zeitgeist-extensions
Status: Fix Committed = Fix Released
** Changed in: zeitgeist-extensions
Milestone: None = fts-0.0.12
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
** Changed in: zeitgeist-extensions
Status: Fix Committed = Fix Released
** Changed in: zeitgeist-extensions
Milestone: None = fts-0.0.12
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
Importance: Undecided = High
** Changed in: zeitgeist-extensions
Status: New = Triaged
** Changed in: zeitgeist-extensions
Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which
by indexing long URLs (at least 245 bytes long). We
already had a cap at 2000 characters, but that was apparently not good
enough.
** Affects: zeitgeist-extensions
Importance: High
Assignee: Mikkel Kamstrup Erlandsen (kamstrup)
Status: Triaged
** Changed in: zeitgeist-extensions
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist-extensions/fts-cap-term-length into
lp:zeitgeist-extensions.
Requested reviews:
Zeitgeist Extensions (zeitgeist-extensions)
Related bugs:
Bug #843668 in Zeitgeist Extensions: Blowing Xapian max term length corrupts
index
Thanks for the logs everyone.
To anyone else experiencing this problem: You don't have to comment here
to register your problem; simply tick the affects me too in the top.
We can all totally appreciate that you are burning CPU and we're working
to resolve it asap.
--
You received this bug
If someone is seeing this please try running 'top' in a terminal and
check whether the PID of zeitgeist-daemon keeps changing every so
often... I have a hunch that the daemon may be restarting over and over
again...
--
You received this bug notification because you are a member of Zeitgeist
Ok, I actually have it myself here now - and I can attest that it's
_not_ because Zeitgeist is restarting...
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/722762
Title:
: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Status: Triaged = Invalid
** Changed in: zeitgeist (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant
*** This bug is a duplicate of bug 705944 ***
https://bugs.launchpad.net/bugs/705944
** This bug has been marked a duplicate of bug 705944
FTS index corruption
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist
** Changed in: zeitgeist-extensions
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/614282
Title:
fts extension is missing
No it does not, and I know because it doesn't use sql at all ;-)
My guess is that it triggers this inside the zg engine by calling into
some of the public api, like get_events() or something.
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in:
revno: 67
fixes bug(s): https://launchpad.net/bugs/617309
committer: Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com
branch nick: MASTER
timestamp: Mon 2011-09-05 11:51:19 +0200
message:
Fix bug fts can SIGSEGV ZG during reindex. This was caused by searching
while rebuilding the index
** Changed in: zeitgeist-extensions
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/705944
Title:
Can't recover from FTS index
If you have at least r69 of the fts extension you can test this by
killing zeitgeist, then running:
$ head /dev/urandom ~/.local/share/zeitgeist/fts.index/postlist.DB
And restarting Zeitgeist. This should cause a reindex. You can verify
this by looking in ~/.cache/zeitgeist/daemon.log. You
If you want to try and help verify that this bug is indeed fixed you
need at least r67 of the fts extension. Then open d-feet and run the
ForceReindex() method on the index - and quickly open Synapse or the
Unity dash and type a search string.
As this is a race it may or may not be elusive. So
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist/network-manager-state-fix into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
Bug #841764 in Zeitgeist Framework: Storage monitor for networkmanager
broken with NM = 0.9
https
Public bug reported:
The storage device monitoring is broken for NetworkManager = 0.9 since
the latest version of NM broke API. The result is that the 'net' storage
id will always be marked as unavailable.
** Affects: zeitgeist
Importance: Undecided
Status: New
--
You received
revno: 1802 [merge]
committer: Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com
branch nick: MASTER
timestamp: Mon 2011-09-05 14:21:57 +0200
message:
Merge lp:~kamstrup/zeitgeist/network-manager-state-fix. Fixes it so we
support both 0.9 and = 0.9 versions of the NetworkManager API
To anyone with this problem - you don't have to kill/replace the running
zeitgeist-daemon if you see this bug. Simply open
~/.cache/zeitgeist/daemon.log in your favorite editor, check that you
don't have embarrassing or confidential stuff in there[1] and attach it
to this bug.
[1]: If you do,
You can generate a redacted zeitgeist log with something like:
sed -e 's/file:.*$/file:XXX/g' ~/.cache/zeitgeist/daemon.log
~/zeitgeist-redacted.log
Replaces all file: URLs in your log with file:XXX.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team,
: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/839382
Title:
zeitgeist-daemon crashed with SIGSEGV in
FlintTable_base
Phew - after much fiddling about I got raptor build from a git checkout
and indeed the 'rapper' build from raptor trunk fixes this as described
in the upstream bug report.
Caveat distropatcheum: The upstream patch requires a re-autogen as it
changes some of the flex source files that are used to
** Also affects: librdf via
http://bugs.librdf.org/mantis/view.php?id=451
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Some comments:
1) The default ZG integration in Ubuntu 11.04 (and 10.10 netbook
edition) logs nothing that can't already be found in recently-used.xbel
(except zg also logs when you launch apps (but not what you do with
them)). So saying that ZG makes Ubuntu less secure by default is a
The reason that we are not using tools like Tracker and Beagle is that
we didn't find them reasonable performance-wise, nor providing the
quality of results, or fine control of queries we wanted. And working
reasonably well is just not good enough in my book.
That said, there's nothing saying we
A DBus dump reveals that the LeaveEvent gets (correctly) marked as
ScheduledActivity but that the AccessEvent when transitioning to the
next track is still a UserActivity (should also have been a
ScheduledActivity since this was an automatic track change without user
action).
** Attachment added:
** Also affects: sezen
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is the registrant for Sezen.
https://bugs.launchpad.net/bugs/739653
Title:
libzeitgeist vapi needs an update
Status in
I'm adding a libzeitgeist task as well here because it right now
creating either a ZeitgeistLog or ZeitgeistIndex will DBus-activate
zeitgeist-daemon. It's unclear to me what the consequences of not
autostarting zeitgeist from these would be though...
And that said simply twiddling these two
Some reference bedtime reading:
- bug #731019 Certification System 201101-7174 boots 7.93 seconds slower
- http://www.phoronix.com/scan.php?page=articleitem=ubuntu_natty_bootnum=1
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed
@manish: I'm testing out from the ppa:banshee-team/banshee-daily ppa and
have:
banshee-2.0.0+git20110427.r1.7fd9361-0ubuntu1+natty
banshee-extension-zeitgeistdataprovider-2.0.0+git20110426.r1.59395ec-0ubuntu1+natty1
libzeitgeist0.1-cil-0.1.1.0-2~natty1
Is that good enough? I am still seeing
Before we freak about about __slots__ and structs I think we need hard
evidence that we lose all this memory to Events and Subjects. Attaching
some profiler to the Python VM should sort this out quickly. And why
doesn't Ubuntu show the same symptoms?
--
You received this bug notification because
On 28 April 2011 14:28, Seif Lotfy 748...@bugs.launchpad.net wrote:
Are you sure your requesting UserActivities and not WorldActivities
?
Yes :-) http://bazaar.launchpad.net/~unity-team/unity-place-
files/trunk/view/head:/src/daemon.vala#L505
--
You received this bug notification because you
** Bug watch added: GNOME Bug Tracker #627311
https://bugzilla.gnome.org/show_bug.cgi?id=627311
** Also affects: cheese via
https://bugzilla.gnome.org/show_bug.cgi?id=627311
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
If you kill Zeitgeist, delete the fts.index folder and restart
Zeitgeist everything should be rebuild fine and dandy. But as you say,
that's just a workaround.
I'm honestly really puzzled how this can happen as Xapian indexes
should be very robust. I'll try and look into writing some stress
** Also affects: zeitgeist
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
https://bugs.launchpad.net/bugs/748120
Title:
Enabling Zeitgeist data-logger in
that was
directly triggered by some user initiated sequence of actions. For
example a music player automatically changing to the next song in a
playlist.
** Changed in: unity
Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: unity
Status: New = Confirmed
--
You
Markus this doesn't seem to happen when ZG stops, but when it starts up
or something. At least that's what I gather from the dupes
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Instead of doing a complex Popen dance to get this right we might as
well use glib's g_spawn_async()..?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/739780
Title:
Session
Looks like this bug was mistakenly marked as Fix Released when it's
really not. Probably the action of some rogue script ;-) So reopening.
** Changed in: unity
Status: Fix Released = Triaged
** Changed in: unity-place-files
Status: Fix Released = Triaged
--
You received this bug
I looked at Markus' branch and I think it makes sense - provided that
we're still confident that the cache gives us a boost :-) And we're
bumpting the schema version anayway...
A quick pre-review of Markus' branch:
- there seems to be missing a commit() after the DELETE statement?
-
Also!
_fix_cache can be a temp table or something right? sqlite has something
akin to a memory backed table that is lost when the process dies. We
might as well use that?
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
Now that we're changing this code we can simplify it even more. The Python
'dbus' module has methods request_name() and name_has_owner() built directly
into the SessionBus singleton, ie:
bus = dbus.SessionBus()
if bus.name_has_owner(org.Foo) : do_blah()
else: bus.request_name(com.Bleh)
- you
Review: Approve
Awesome Siegfried :-)
Code looks good to me and the tests all run. I think we may want to make a
backup copy in the upgrade script - before we do anything. This is by far the
most complex upgrade we have.
Does that mean 0.7 is compatible with the amendment you made to the
Review: Approve
RainCT kamstrup: well, --quit doesn't need to take the bus
Right :-)
--
https://code.launchpad.net/~zeitgeist/zeitgeist/dbus-paranoia/+merge/53301
Your team Zeitgeist Framework Team is subscribed to branch
lp:~zeitgeist/zeitgeist/dbus-paranoia.
** Changed in: unity-place-files
Status: Triaged = Invalid
** Changed in: unity
Status: Triaged = Invalid
** Changed in: unity-place-files (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which
in Unity
** Affects: unity
Importance: Medium
Assignee: Mikkel Kamstrup Erlandsen (kamstrup)
Status: Triaged
** Affects: zeitgeist-extensions
Importance: High
Assignee: Mikkel Kamstrup Erlandsen (kamstrup)
Status: Triaged
** Changed in: zeitgeist-extensions
Fixed in lp:zeitgeist-extensions revno51: Also index subject URI,
origin, mimetype, and storage. And make sure we respect these fields in
the event template compiler
** Changed in: zeitgeist-extensions
Status: Triaged = Fix Committed
** Changed in: unity
Status: Triaged = Fix
Review: Needs Fixing
I haven't properly reviewed this yet - but this caught my eye:
48 + CONSTRAINT actor_fk FOREIGN KEY(origin)
49 + REFERENCES uri(id) ON DELETE CASCADE,
I think it should be CONSTRAINT origin_fk instead, right?
--
I don't have any clever solution off the top of my head - I just want
to give Siegfried some props for the cool detective work! Nice job!
Now. To thinking.
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
lambda :
The space before the colons looks ugly :P.
Fixed
except:
Please make this except sqlite3.foobar (or, worst-case, except Exception).
Also, why do you need the rollback there?
Since sqlite3 doesn't have a common error super class I am just catching
Exception for now. The
Mikkel Kamstrup Erlandsen has proposed merging
lp:~zeitgeist/zeitgeist/storagemonitor2 into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#489194 Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
For more
Review: Approve
Looks good to me
--
https://code.launchpad.net/~zeitgeist/zeitgeist/bug673008/+merge/48914
Your team Zeitgeist Framework Team is subscribed to branch
lp:~zeitgeist/zeitgeist/bug673008.
___
Mailing list: https://launchpad.net/~zeitgeist
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist/new-event-interpretations into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#714636 Zeitgeist needs AcceptEvent, DenyEvent and ExpireEvent events
https://bugs.launchpad.net/bugs
** Changed in: zeitgeist
Status: New = Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/714636
Title:
Zeitgeist needs AcceptEvent, DenyEvent and
** Branch unlinked: lp:~kamstrup/zeitgeist/storagemonitor
** Branch linked: lp:~zeitgeist/zeitgeist/storagemonitor2
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/489194
I believe that it's a shorthand check for the python-rdflib package.
In Ubuntu, at least, that package ships this tool. We python-rdflib
for parsing the ontologies at build time
--
https://code.launchpad.net/~federico-gnome/zeitgeist/fixes/+merge/46803
Your team Zeitgeist Framework Team is
Maybe we can replace the check for rdfpipe with something ala:
python -c import rdflib
if [ $? != 0 ]; then
echo You need the Python module 'rdflib' in order to compile Zeitgeist
exit 1
fi
--
https://code.launchpad.net/~federico-gnome/zeitgeist/fixes/+merge/46803
Your team Zeitgeist
I agree in principle that this is desirable, but comparing the
relatively small gains to the complexity in the URL provided by Markus
I am not sure I think it's worth it...
___
Mailing list: https://launchpad.net/~zeitgeist
Post to :
Siegfried; what you propose is breaking the DBus API, which will force
me to break ABI and API of libzeitgeist = mikkel becomes unpopular.
That said, I do see the merit in what you are proposing. It just has
some consequences...
___
Mailing list:
On 6 January 2011 10:43, Markus Korn thek...@gmx.de wrote:
After re-reading this bugreport, the discussion it includes and the merge
proposal, I'm still not confident that the API which is proposed here is good
enough. This is why I started working on a blacklist API spec.
It is still work
1 - 100 of 304 matches
Mail list logo
