glib2.0 2.64.6-1 (TEST)

[Corinna Vinschen]

On Jul  3 15:49, Jon Turney wrote:
> On 02/07/2023 15:30, Jon Turney wrote:
> > 
> > The following packages have been uploaded to the Cygwin distribution:
> > 
> > * libglib2.0_0-2.64.6-1
> > * libglib2.0-devel-2.64.6-1
> > * libglib2.0-doc-2.64.6-1
> > 
> [...]
> > 
> > There are many test-suite failures, however, as far as I can tell, they
> > are not regressions, so this should work as well as it ever did.
> 
> At least some of these test failures are due to bugs or shortcomings in the
> Cygwin DLL. In an ideal world, I'd have the time and motivation to
> investigate them all, but here's a brief summary of the few I looked into
> ...
> 
> gdatetime: The _NL_CTYPE_OUTDIGITx_MB constants for nl_langinfo aren't
> defined (possibly because we don't have the required information, e.g. to
> produce Persian (as opposed to Arabic) digit characters in the fa_IR.utf-8
> locale)

Uhm... we actually have this information.  Only, unfortunately I screwed
up the names:

  _NL_CTYPE_OUTDIGITSx_MB

instead of

  _NL_CTYPE_OUTDIGITx_MB

D'oh.

Do you think we need the wrong names for backward compat?  Theoretically
they should never have been used...

> stream_rw-all: writes to a pipe until it's full, then ends up blocking when
> poll() still indicates it's writeable?

Pipes never worked 100% POSIX-like, unfortunately, but the hang
was supposed to be fixed by introducingh the semaphore select_sem.

Do you have an STC?  Takashi, can you take a look?

> socket, unix-fd: try to send a fd over a socket, not currently implemented.
> 
> all the GDbus tests: these seem to get stuck during the handshake for an
> emulated unix-domain socket, somehow (It seems like all the dbus pacakge
> tests fail also, probably in the same way)

Does an extra call to setsockopt(fd, SOL_SOCKET, SO_PEERCRED, NULL, 0)
fix this, perhaps?


Corinna