What testing will be done of the resulting binary packages to guard
against misbuilds not caught by the upstream testing? Please call this
out explicitly in the bug description. (If the autopkgtests are
sufficient, that's fine, please just call it out.)
** Changed in: glib2.0 (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1794544
Title:
[SRU] 2.56.3
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Bionic:
Incomplete
Bug description:
[ Description ]
The third stable release in the 2.56 series.
[ QA ]
Upstream release, so QA already performed by maintainers
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
[ Regression potential ]
Various fixes in multiple places so multiple apps could be affected.
* New upstream release (LP: #xxx)
+ The documentation for G_GNUC_MALLOC has changed to be more restrictive
to avoid miscompilations; you should check whether any uses of it in
your code are appropriate
+ Fix cancellation of g_subprocess_communicate_async() calls
+ Bug fixes:
+ /network-monitor/create-in-thread fails in (LXC) containers on
glib-2-56
+ GBookmarkFile: nullptr access in current_element
+ GBookmarkFile: heap-buffer-overflow in g_utf8_get_char
+ Backport g_subprocess_communicate() cancellation fixes from !266 to
glib-2-56 (LP: #1789476)
+ Many uses of G_GNUC_MALLOC are incorrect
+ Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw
+ Fix persistent CI failure on glib-2-56
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
