** Changed in: glib
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1036260
Title:
Running gtester-report on gtester output raises KeyError
** Changed in: glib
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1036260
Title:
Running gtester-report on gtester output raises KeyError
To manag
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/103
** Changed in: glib
Status: Unknown => New
** Changed in: glib
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1036260
Title:
Running gteste
Thanks for the bug report. I found an upstream bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=668035 and I submitted a
simple patch to fix it.
You can workaround the issue by manually adding:
PACKAGENAME
VERSION
REVISION
to the generated xml. It seems that is exactly what glib does, to
c
