This bug was fixed in the package glib2.0 - 2.56.3-0ubuntu0.18.04.1
---
glib2.0 (2.56.3-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1794544)
+ The documentation for G_GNUC_MALLOC has changed to be more restrictive
to avoid miscompilations; you sho
Version 2.56.3 installed here from proposed, works properly.
marco@tricky:/tmp:✓ $ apt-cache policy libglib2.0-0
libglib2.0-0:
Installato: 2.56.3-0ubuntu0.18.04.1
Candidato: 2.56.3-0ubuntu0.18.04.1
Tabella versione:
*** 2.56.3-0ubuntu0.18.04.1 100
500 http://archive.ubuntu.com/ubunt
Hello Iain, or anyone else affected,
Accepted glib2.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.56.3-0ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
This upload should *fix* misbuilds for future builds. It itself
shouldn't cause things to break and/or unbreak (unless there was
breakage inside glib2.0 itself, in which cause I would have expected one
or more of the rdeps' tests to have picked the problem up already).
On the upstream issue that r
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)
** Description changed:
[ 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
- [ Regresison potential ]
+ [ Regression potential ]
Various fixes
