Your message dated Sat, 7 Sep 2024 10:47:45 +0100 with message-id <ztwhqrv5ce8ty...@remnant.pseudorandom.co.uk> and subject line Re: Bug#1081016: mutter: keybindings autopkgtest fails because it needs compiled org.gnome.mutter.test gsettings schema has caused the Debian Bug report #1081016, regarding mutter: keybindings autopkgtest fails because it needs compiled org.gnome.mutter.test gsettings schema 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 ow...@bugs.debian.org immediately.) -- 1081016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mutter Version: 47~rc-1 Severity: serious mutter added new installed tests in 47~rc that we then run as autopkgtests. They asked me before and I said it was ok. One of the new tests is a keybindings test that depends on a gsettings schema org.gnome.mutter.test . That schema is installed by upstream to /usr/share/mutter-15/tests/org.gnome.mutter.test.gschema.xml If mutter is built first, that gsettings schema is compiled by meson and works. But that doesn't happen when it's run as an autopkgtest. Off the top of my head, I'm not sure how to compile this gsettings schema where we need it. There are other installed tests that need access to regular gsettings schemas. The test is mutter-15/keybindings.test and the source code is src/tests/keybindings.c Thank you, Jeremy Bícha
--- End Message ---
--- Begin Message ---Version: 47~rc-2 On Fri, 06 Sep 2024 at 16:50:44 -0400, Jeremy Bícha wrote: > If mutter is built first, that gsettings schema is compiled by meson > and works. But that doesn't happen when it's run as an autopkgtest. This seems to have been a missing dependency on libglib2.0-bin, fixed in 47~rc-2 (but with a typo in the bug number closed by the changelog). smcv
--- End Message ---
