#855: extend dbus api to get all bugzillas created by abrt from local machine ----------------------+--------------------- Reporter: jmoskovc | Type: defect Status: new | Priority: major Milestone: | Component: Version: 2.0 | Resolution: Keywords: | ----------------------+---------------------
#855: extend dbus api to get all bugzillas created by abrt from local machine --------------------------+----------------------------- Reporter: jmoskovc | Owner: crash-catcher@… Type: enhancement | Status: new Priority: major | Milestone: Component: abrt | Version: 2.0 Resolution: | Keywords: Blocked By: | Blocking: --------------------------+----------------------------- Changes (by jmoskovc):
* owner: => crash-catcher@… * component: => abrt * cc: lmacken (added) * type: defect => enhancement
Comment:
{{{ <lmacken> hey all. how can get at a list of bugs #'s that were filed from a users local abrt? * mtoman has quit (Quit: Leaving.) <jmoskovc> lmacken: hm, you want a list of bugzillas that were reported from some machine? <lmacken> jmoskovc: yes, I want to write code that runs on a local system and figures out what bug #'s it filed <lmacken> I wrote fedmsg-notify, which provides a dbus bridge to realtime fedmsg notifications. Now we'll be able to watch bodhi updates and see if it contains a bug # that the users system filed or hit, and say "Hey, this update fixes this problem that you had" <lmacken> https://github.com/lmacken/fedmsg-notify <jmoskovc> lmacken: oh, that's nice we were thinking about a similar thing :) <jmoskovc> lmacken: it's a bit tricky, because for reporting abrt moves the report to $HOME <lmacken> I'm demoing some of this new fedmsg stuff tomorrow to my team, so I wanted to see what it would take to get this done <jmoskovc> lmacken: but if you have only one user it should be easy <lmacken> that should be fine, my fedmsg-notify-daemon is dbus-activated and runs as the local user <jmoskovc> lmacken: just walk thru .cache/abrt/spool/* <lmacken> perfect... reported_to has it <jmoskovc> lmacken: and look for file reported_to <lmacken> thanks! <jmoskovc> lmacken: and you'll have to parse it :-/ <lmacken> yeah, that's fine for this initial prototype :) <jmoskovc> lmacken: I think we can implement some DB for this <jmoskovc> lmacken: it would make much better sense <lmacken> or a dbus api to get it <jmoskovc> lmacken: sure no problem, now we have a customer for it :) }}}
crash-catcher@lists.fedorahosted.org