On 13/12/2019 05:41, Brian May wrote:
> Brian May <firstname.lastname@example.org> writes:
>> Apparently the fix for ibus creates a regression in glibc that must get
>> fixed also:
>> However this patch patches GIO in glibc, and it looks like glibc in
>> Jessie (2.19-18+deb8u10) doesn't have this directory. Or anything
>> related to GIO that I can see.
>> Hence, I am inclined to think maybe glibc doesn't need to be fixed in
> i have back-ported the patches to the Jessie version. Hopefully this is
> correct :-)
> If I incorporate the test patch into the Debian package, expecting a
> test failure, instead I get the following results:
> SKIP: gdbus-server-auth 1 /gdbus/server-auth # SKIP Testing interop with libdbus not supported
> SKIP: gdbus-server-auth 2 /gdbus/server-auth/tcp # SKIP Testing interop with libdbus not supported
> SKIP: gdbus-server-auth 3 /gdbus/server-auth/anonymous # SKIP Testing interop with libdbus not supported
> SKIP: gdbus-server-auth 4 /gdbus/server-auth/external # SKIP EXTERNAL authentication not implemented on this platform
> SKIP: gdbus-server-auth 5 /gdbus/server-auth/sha1 # SKIP Testing interop with libdbus not supported
> SKIP: gdbus-server-auth 6 /gdbus/server-auth/anonymous/tcp # SKIP Testing interop with libdbus not supported
> SKIP: gdbus-server-auth 7 /gdbus/server-auth/sha1/tcp # SKIP Testing interop with libdbus not supported
> This is something I would like to be able to test before uploading. At
> least it does look like I enabled the test correctly.
> Not sure when I will get to look at this again, I haven't claimed it, if
> somebody else wants to take over then go ahead.
I have been looking at this, but building glib with only the two fix commits
(not the tests one) makes the build hang on the network-monitor tests. I haven't
investigated much yet, but I wonder if it may be an issue with my local
configuration. Did you glib build succeed? If so can you publish the source and
debs? I'd like to test that with some qt5 apps to verify the regression fix.