Your message dated Wed, 18 Dec 2019 16:04:23 +0000
with message-id <[email protected]>
and subject line Bug#946355: fixed in glib2.0 2.63.3-1
has caused the Debian Bug report #946355,
regarding glib2.0: Please make autopkgtests cross-test-friendly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
946355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946355
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: glib2.0
Version: 2.63.1-2
Severity: minor
Tags: patch
User: [email protected]
Usertags: origin-ubuntu focal ubuntu-patch
Dear maintainers,
In Ubuntu, we are in the process of moving the i386 architecture to a
compatibility-only layer on amd64, and therefore we are also moving our
autopkgtest infrastructure to test i386 binaries in a cross-environment.
This requires changes to some tests so that they are cross-aware and can do
the right thing.
The glib2.0 tests currently fail in this environment, because there are
build tests that do not invoke the toolchain in a cross-aware manner. I've
verified that the attached patch lets the tests successfully build (and run)
i386 tests on an amd64 host.
Note that upstream autopkgtest doesn't currently set DEB_HOST_ARCH so this
is a complete no-op in Debian for the moment. Support for cross-testing in
autopkgtest is currently awaiting review at
https://salsa.debian.org/ci-team/autopkgtest/merge_requests/69 and once
landed, will still have no effect unless autopkgtest is invoked with a '-a'
option. So this change should be safe to land in your package despite this
not being upstream in autopkgtest.
Unfortunately in the case of glib2.0, this is an incomplete solution for
cross-testing compatibility, because in addition to the build tests, glib2.0
has two other tests that depend on libglib2.0-tests and this package is not
cross-installable because dh-python causes it to have a dependency on
python3:any but on python3.7, and it's impossible to install the
foreign-arch (i386) version of python3.7. There is discussion on the
autopkgtest MP about how to filter out some tests when cross-testing, which
may wind up being a solution, but I think this is also a bug in dh-python
that it generates a dependency on same-arch python3.7, so I think this patch
is worth inclusion in glib2.0 as-is.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
[email protected] [email protected]
diff -Nru glib2.0-2.63.1/debian/tests/build glib2.0-2.63.1/debian/tests/build
--- glib2.0-2.63.1/debian/tests/build 2019-11-18 05:59:35.000000000 -0800
+++ glib2.0-2.63.1/debian/tests/build 2019-12-06 21:31:37.000000000 -0800
@@ -34,6 +34,13 @@
WORKDIR=$(mktemp -d)
trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
cd $WORKDIR
+
+if [ -n "${DEB_HOST_GNU_TYPE:-}" ]; then
+ CROSS_COMPILE="$DEB_HOST_GNU_TYPE-"
+else
+ CROSS_COMPILE=
+fi
+
cat <<EOF > glib.c
#include <glib.h>
@@ -119,7 +126,7 @@
;;
esac
- gcc $cflags -o ${lib}-$mode ${lib}.c `pkg-config $pcflags --cflags --libs
${packages}`
+ ${CROSS_COMPILE}gcc $cflags -o ${lib}-$mode ${lib}.c
`${CROSS_COMPILE}pkg-config $pcflags --cflags --libs ${packages}`
echo "build ($lib, $mode): OK"
[ -x ${lib}-$mode ]
foo=bar ./${lib}-$mode
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.63.3-1
We believe that the bug you reported is fixed in the latest version of
glib2.0, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Iain Lane <[email protected]> (supplier of updated glib2.0 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 18 Dec 2019 14:02:00 +0000
Source: glib2.0
Architecture: source
Version: 2.63.3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Iain Lane <[email protected]>
Closes: 946355
Changes:
glib2.0 (2.63.3-1) experimental; urgency=medium
.
[ Iain Lane ]
* New upstream release
+ Add a `--glib-min-version` argument to `gdbus-codegen` which controls
breaks in the API of generated code
+ Add `g_clear_list()` API to clear `GList`s to `NULL`
+ Add a `GMemoryMonitor` API to be notified of memory pressure situations
using the low-memory-monitor project
+ Add support for dispose functions for `GSource` implementations
+ Tighten up validation of GObject signal and property names, allowing
performance improvements
* debian/tests/build: Style fixes, thanks to shellcheck.
* d/p/d/Disable-some-tests-on-slow-architectures-which-keep-faili.patch:
Rebase. Upstream have disabled these tests by default too (unless slow
mode is enabled), so we don't need to add a patch to do a similar thing.
* debian/libglib2.0-0.symbols: New symbols for 2.63.3
* d/p/tests-Skip-GMemoryMonitor-tests-if-the-dbusmock-template-.patch: Add.
We don't have a new enough dbusmock in Debian at the minute (one is not
released yet). Skip the test if the required template isn't available.
* control: Add Depends for the new memory-monitor tests.
There are new tests, written in python, for GMemoryMonitor. They require
dbus-python, pygobject, and the GI bindings for GLib and GIO.
.
[ Steve Langasek ]
* debian/tests/build: Make cross-test friendly
autopkgtest is soon to get a `-a ARCHITECTURE` switch, which will
cross-test autopkgtests. This is to be detected by the presence of the
`dpkg-architecture`-style family of variables being set in the
environment.
For build tests like `glib2.0`'s `build` test, this means that we should
test "${DEB_HOST_ARCH}" and invoke the cross toolchain as necessary.
(Closes: #946355)
Checksums-Sha1:
ea5a862686bb09871223abaeb4b028bf27f72f43 3279 glib2.0_2.63.3-1.dsc
cea319d2e303f5c8486147d843daeaff90a2fa85 4719532 glib2.0_2.63.3.orig.tar.xz
2ccc98b999c0cffb0981d09aa9e168ad8348a8c7 88084 glib2.0_2.63.3-1.debian.tar.xz
f174a62558a24742dd250e1d32e0dd23f7af4565 13634
glib2.0_2.63.3-1_source.buildinfo
Checksums-Sha256:
95b8b6250d8f886fcc5c87d7a33cf01eb621587b0361b036c5a96113c973bdb8 3279
glib2.0_2.63.3-1.dsc
8a09a2a059eb617d52b6fcd6f25e0243f0849c598612c9aa5074ce3a6ee1c11c 4719532
glib2.0_2.63.3.orig.tar.xz
c09cede8df97de995daa6c7baf30b4ac294ff260cde670f708e369979264d774 88084
glib2.0_2.63.3-1.debian.tar.xz
6cb57ed1f5b6bcdadc2bd0426461d17da7bd049735d5347eafb657bac91eb4e4 13634
glib2.0_2.63.3-1_source.buildinfo
Files:
9abb66048b6639d645fd7a8e8f72e285 3279 libs optional glib2.0_2.63.3-1.dsc
da7afdb02af6057baf9e104d97db5b22 4719532 libs optional
glib2.0_2.63.3.orig.tar.xz
154110b6ae0e4aa25b9866b8c2180425 88084 libs optional
glib2.0_2.63.3-1.debian.tar.xz
671697c7e2f71d61dee2c5f0213f17b1 13634 libs optional
glib2.0_2.63.3-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEPQ77lee1I38W6CJY41LVxRxQQdQFAl36SL8ACgkQ41LVxRxQ
QdTNURAAn5K/WYxjXV6HZ3GOtVnP+RG431k1h8Ub4rTg1ppnucwBKvbZcpsngOpm
+30uizFXu3f8uDflmZLdi17PM5CdrbXPnt0kNtH6AZZ/eNW0CMBDLwKfbetKE1PA
Ee6B1Qg6ymI3mtPUNvUqLwRBoxs1gfDjteu8gYTuCrwrPV+3KCj24FrZ7krhJbqV
zyA0Dc8rG4WK7BBE1v+oXSQuI2JlSP9zUMbieIad41sir89gdVl1MAMYLBxamWCb
cbzSWlHKJZy4VqpK979DjAXEYSXwqb9GW2inFJmUxMJc2fVt7UKQ8qCgGOfwpgfm
ChVLmHBq+1/xrqoHqVPQoHY6Abg60eryPo6gYyu7VtwKO2oNqL5fv6LhOQqDuTmA
XywcaXEM/PHhdQUhhTcXlKKAnfvX7mdDzz2ucvWcO8itqjxgMor8U+0xxDX1dGFl
5/p8E2XXo5ns5dZBdS0xNdIRFwGGJr07WP5zLFXkB2Vb3W6yM3PD45RajMO6X8vG
1YgYRYfhRYAVsPNrW5yGhukPt5IL3RRNELIQDNB2OKANIrVZ229sd0vUZiPWRore
DgsCLrdnZIplgBodBh/20UNaiS68mwBbjy9st/Of1Bg0C47DS3hTOsjJShzTSW0C
G9NUJlPeGAst3zz8xnQqunV+e+yiwSwfrpwLCpsazzQ4EN5K++8=
=cdBK
-----END PGP SIGNATURE-----
--- End Message ---
