On 22/10/14 10:14, intrigeri wrote:
Control: reopen -1
Control: notfixed -1 1.42.0-2.1
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=738989
Hi,
I'm very sorry, I had improperly tested that the upstream commit I've
cherry-picked in my NMU was enough to fix the problem for
libglib-object-introspection-perl... and it isn't: that commit only
fixes the problem in tests/scanner/regress.c, which makes the
libglib-object-introspection-perl test suite build process go a bit
further, but more tests/*.c are affected, including
tests/gimarshallingtests.c, and the build breaks a bit further.
The attached patch changes tests/gimarshallingtests.c in the same way
as the aforementioned upstream commit did for tests/regress.c.
This time, I've more carefully verified that it indeed allows running
libglib-object-introspection-perl's test suite.
I've reported this more general problem upstream, and submitted my new
patch there.
Should I NMU again with this new patch applied?
Yes.
Thanks,
Emilio
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
