Hello Iain, or anyone else affected,

Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: glib2.0 (Ubuntu Eoan)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.

  [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

  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

  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
      Signed-off-by: Simon McVittie <s...@collabora.com>

  which are both testsuite fixes. There are some additional non-upstream

     * 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

  [ Regression potential ]

  all test fixes> Build failures or autopkgtest failures.

To manage notifications about this bug go to:

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

Reply via email to