glib2.0 (2.42.1-1+deb8u3) jessie-security; urgency=medium

  * CVE-2019-13012: Update CVE-2019-13012-1.patch. Fix memleak regression
    spotted by Simon McVittie. (Closes: #933877).

glib2.0 (2.42.1-1+deb8u2) jessie-security; urgency=medium

  * Non-maintainer upload by the LTS team.
  * CVE-2018-16428: gmarkup: Fix crash in error handling path for closing
    elements.
  * CVE-2018-16429: gmarkup: Fix unvalidated UTF-8 read in markup parsing
    error paths.
  * CVE-2019-13012: keyfile settings: Use tighter permissions. (Closes:
    #931234).

glib2.0 (2.42.1-1+deb8u1) jessie-security; urgency=high

  [Michael Biebl]
  * debian/patches/tests-gdatetime-Use-a-real-rather-than-invented-time.patch:
    Cherry-pick a patch from upstream to fix GDateTime tests when tzdata ≥
    2017a is in use. (#858214)

  [Simon McVittie]
  * debian/patches/gfile-Limit-access-to-files-when-copying.patch:
    Backport patch from upstream to ensure files don't temporarily have
    less restrictive permissions during copying
    (#929753, CVE-2019-12450).
  
  [Sylvain Beucler ]
  * Non-maintainer upload by the Debian LTS team.
  * Apply FTBFS fix for jessie.
  * Apply CVE-2019-12450 fix for jessie.

Update to upstream version '2.42.1'
with Debian dir a4b52a8133cb6cf7457551d01c247246ef7ae470

I assume this was some issue with the svn-to-git migration.

Gbp-Dch: ignore

  + Removed, merged upstream.

expects.

g_get_monotonic_time() and g_get_real_time() now always use different
clocks, so we cannot avoid correcting for their offset.  Fixes failure
to time out on Mac OS X.

https://bugzilla.gnome.org/show_bug.cgi?id=738197

Internal allocation size (array->alloc) was being kept to 0 when a new
GByteArray was created from an already existing heap-allocated buffer.

Among other things, this was making g_byte_array_set_size() fully clear all
the buffer contents (not just the newly allocated memory) when
G_DEBUG=gc-friendly was being used...

  if (G_UNLIKELY (g_mem_gc_friendly))
    memset (array->data + array->alloc, 0, want_alloc - array->alloc);

https://bugzilla.gnome.org/show_bug.cgi?id=738170

Don't use it at home.

upstream stable branch - silences warnings that are shown to users on
stderr, and which also cause some testsuite failures and consequent FTBFS.

https://bugzilla.gnome.org/show_bug.cgi?id=728256

Disable the deprecation warnings on GObject properties by default.  This
change is only being made on the stable branch, and maybe only for this
one stable series -- the warnings will remain enabled by default on the
unstable releases.

This ensures the uintptr_t type is defined on mingw-w64.

Fixes compile error:

make[4]: Entering directory
`/home/abuild/rpmbuild/BUILD/glib-2.42.0/gobject'
  CC       libgobject_2_0_la-gtype.lo
In file included from gtype.c:24:0:
../glib/valgrind.h: In function 'VALGRIND_PRINTF':
../glib/valgrind.h:5601:4: error: unknown type name 'uintptr_t'
    uintptr_t _qzz_res;
    ^

https://bugzilla.gnome.org/show_bug.cgi?id=737143

g_thread_pool_push() only returns an error if it fails to spawn a new
thread. However, it unconditionally adds the task to its worker queue,
so:
 • if _any_ threads exist in the pool, the task will eventually be
   handled; and
 • if _no_ threads exist in the pool, the task will be handled if one
   is eventually successfully spawned.
If no more threads are ever spawned, the process probably has bigger
problems than a single GTask which is taking forever to complete.

https://bugzilla.gnome.org/show_bug.cgi?id=736806

Explain why the signal handler holds a reference to the GTask, even
though that causes a reference loop at first glance.

https://bugzilla.gnome.org/show_bug.cgi?id=736806

The GSource times assigned to creation_time are always signed.

https://bugzilla.gnome.org/show_bug.cgi?id=736806

Add wrong po file
This reverts commit ee3d5557.