# (I hope all this messing around doesn't reopen the damn bug) reassign 665692 pygobject-2 2.28.6-10 affects 665692 reportbug severity 665692 normal # Other copies were filed against different packages reassign 664276 pygobject-2 reassign 665759 pygobject-2 forcemerge 665692 664276 665759 thanks
(Spent some time wrapping my head around this, so I thought I'd share the explanation with the bug submitters. Sorry if I'm boring anyone.) On Sun, Mar 25, 2012 at 03:23:36PM +0800, jida...@jidanni.org wrote: > ** (process:7373): WARNING **: Trying to register gtype 'GMountMountFlags' as > flags when in fact it is of type 'GEnum' As Sandro pointed out, this is not a bug with reportbug, but rather with pygobject-2. (Incidentally, it will only affect reportbug if you have installed python-gtk2.) The issue is that these types had to be modified concurrently in glib2.0 (2.31+) and pygobject-2 (2.28.6-10). However, glib2.0 stayed in experimental for a little bit, while pygobject-2 was uploaded to unstable right away, hence the type mismatch. (This is somewhat the mirror image of LP #918607 in Ubuntu.) Version 2.32.0-2 of glib2.0 was just uploaded to unstable today, bringing both in sync. If you're running testing, you can simply downgrade pygobject-2 to 2.28.6-9 in the meantime. -- A radioactive cat has eighteen half-lives. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
