All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package:
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64) sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386) cairo/unknown (armhf) netplan.io/0.98-0ubuntu1 (ppc64el) apport/2.20.11-0ubuntu8.2 (amd64) snapd-glib/unknown (armhf) firefox/70.0.1+build1-0ubuntu0.19.10.1 (armhf) bumblebee/unknown (armhf) glib2.0/2.62.2-2~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850932 Title: [SRU] Backport 2.62.2-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.2-2 from focal. The main purpose of this backport (as opposed to -1) is to fix bug #1844853. But there are several other changes. There are many cherry-picks to improve the testsuite's reliability. At the time of upload they weren't in the stable branch, but now they almost all are. These commits can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The two that are not are: commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3 Author: Simon McVittie <s...@collabora.com> Date: Tue Oct 29 16:27:53 2019 +0000 gdbus-server-auth test: Create temporary directory for Unix socket This avoids failure to listen on the given address on non-Linux Unix kernels, where abstract sockets do not exist and so unix:tmpdir is equivalent to unix:dir. To avoid bugs like this one recurring, run most of these tests using the unix:dir address type, where Linux is equivalent to other Unix kernels; just do one unix:tmpdir test, to check that we still interoperate with libdbus when using abstract sockets on Linux. Resolves: GNOME/glib#1920 Fixes: 9f962ebe "Add a test for GDBusServer authentication" Signed-off-by: Simon McVittie <s...@collabora.com> commit 9f962ebeac1d67223579ad0d261c4c8215f7c427 Author: Simon McVittie <s...@collabora.com> Date: Fri Oct 11 19:02:55 2019 +0100 Add a test for GDBusServer authentication In particular, if libbdus is available, we test interoperability with a libdbus client: see GNOME/glib#1831. Because that issue describes a race condition, we do each test repeatedly to try to hit the failing case. Signed-off-by: Simon McVittie <s...@collabora.com> which are both testsuite fixes. There are some additional non-upstream changes: * d/p/debian/mimeapps-test-Mark-as-flaky.patch: Drop patch, hopefully no longer needed with #941550 fixed * d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch: Make taptestrunner non-executable to avoid a Lintian warning the former is again a testsuite fix. The latter is a fix to the test runner, which is relevant for the installed tests (run via autopkgtest) but not otherwise. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. [ Regression potential ] all test fixes> Build failures or autopkgtest failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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
