Bug#737380: glib2.0: FTBFS on mipsel: gapplication test failed: ECHILD was received by waitpid()

Source: glib2.0 Version: 2.38.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=glib2.0arch=mipselver=2.38.2-1stamp=1387885448: # random seed: R02S852f3ece8c5f76fcefb61e81eb83e7a7 # Start of

Bug#737380: glib2.0: FTBFS on mipsel: gapplication test failed: ECHILD was received by waitpid()

Doing a test build on eder to see whether this is reproducible. mips* porters are more than welcome to take over - I know virtually nothing about the mips* architectures. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#737380: glib2.0: FTBFS on mipsel: gapplication test failed: ECHILD was received by waitpid()

tags 737380 + confirmed thanks On 02/02/14 10:20, Simon McVittie wrote: # random seed: R02S852f3ece8c5f76fcefb61e81eb83e7a7 # Start of gapplication tests ok 1 /gapplication/no-dbus ok 2 /gapplication/basic # GLib-FATAL-WARNING: In call to g_spawn_sync(), exit status of a child process was

Bug#737380: glib2.0: FTBFS on mipsel: gapplication test failed: ECHILD was received by waitpid()

This appears to be something to do with the gapplication test accidentally trying to use `dbus-launch --autolaunch`, because of the following sequence of events: * one test-case (/gapplication/basic in my testing) calls g_test_dbus_up() * that test-case (/gapplication/basic in my testing) calls