Bug#950001: marked as done (Upgrade libxkbcommon to upstream 0.10.0)
Your message dated Thu, 06 Feb 2020 12:04:57 +0000
with message-id <E1izftx-000EKa-OK@fasolo.debian.org>
and subject line Bug#950001: fixed in libxkbcommon 0.10.0-1
has caused the Debian Bug report #950001,
regarding Upgrade libxkbcommon to upstream 0.10.0
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 owner@bugs.debian.org
immediately.)
--
950001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950001
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:libxkbcommon
Version: 0.9.1-1
Dear Maintainer,
The libxkbcommon has a new upstream release 0.10.0. It has several improvements and fixes, like the capability of utilizing per-user configuration, and the use of includes in the rule files.
Full changelog:
> libxkbcommon 0.10.0 - 2020-01-18
> ===================
>
> - (security) Fix quadratic complexity in the XKB file parser. See commit
> message 7c42945e04a2107827a057245298dedc0475cc88 for details.
>
> - Add $XDG_CONFIG_HOME/xkb to the default search path. If $XDG_CONFIG_HOME
> is not set, $HOME/.config/xkb is used. If $HOME is not set, the path is not
> added.
>
> The XDG path is looked up before the existing default search path $HOME/.xkb.
>
> Contributed by Peter Hutterer <@who-t.net>.
>
> - Add support for include statements in XKB rules files.
>
> This is a step towards making local XKB customizations more tenable and
> convenient, without modifying system files.
>
> You can now include other rules files like this:
>
> ! include %S/evdev
>
> Two directives are supported, %H to $HOME and %S for the system-installed
> rules directory (usually /usr/share/X11/xkb/rules).
>
> See commit message ca033a29d2ca910fd17b1ae287cb420205bdddc8 and
> doc/rules-format.txt in the xkbcommon source code for more information.
>
> Contributed by Peter Hutterer <@who-t.net>.
>
> - Downgrade "Symbol added to modifier map for multiple modifiers" log to a
> warning.
>
> This error message was too annoying to be shown by default. When working on
> keymaps, set `XKB_LOG_LEVEL=debug XKB_LOG_VERBOSITY=10` to see all possible
> messages.
>
> - Support building on Windows using the meson MSVC backend.
>
> Contributed by Adrian Perez de Castro <@igalia.com>.
>
> - Fix bug where the merge mode only applied to the first vmod in a
> `virtual_modifiers` statement. Given
>
> augment virtual_modifiers NumLock,Alt,LevelThree
>
> Previously it was incorrectly treated as
>
> augment virtual_modifiers NumLock;
> virtual_modifiers Alt;
> virtual_modifiers LevelThree;
>
> Now it is treated as
>
> augment virtual_modifiers NumLock;
> augment virtual_modifiers Alt;
> augment virtual_modifiers LevelThree;
>
> - Reject interpret modifier predicate with more than one value. Given
>
> interpret ISO_Level3_Shift+AnyOf(all,extraneous) { ... };
>
> Previously, extraneous (and further) was ignored. Now it's rejected.
>
> - Correctly handle capitalization of the ssharp keysym.
>
> - Speed up and improve the internal `xkeyboard-config` tool. This tool
> compiles all layout/variant combinations in the xkeyboard-config dataset
> and reports any issues it finds.
>
> Contributed by Peter Hutterer <@who-t.net>.
>
> - Speed up "atoms" (string interning). This code goes back at least to X11R1
> (released 1987).
-- Iiro Laiho
--- End Message ---
--- Begin Message ---
Source: libxkbcommon
Source-Version: 0.10.0-1
We believe that the bug you reported is fixed in the latest version of
libxkbcommon, 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 950001@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Timo Aaltonen <tjaalton@debian.org> (supplier of updated libxkbcommon 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 13:49:36 +0200
Source: libxkbcommon
Architecture: source
Version: 0.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaalton@debian.org>
Closes: 950001
Changes:
libxkbcommon (0.10.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #950001)
* control: Support nocheck profile for xvfb build-dep.
* Migrate to debhelper-compat 12, use dh_missing.
Checksums-Sha1:
cfe254c4779c86fdcabb27ecaa4ee6988cc98c2e 2451 libxkbcommon_0.10.0-1.dsc
1db2eb67afaccd664df28260a6c6cf9a727eb300 600904 libxkbcommon_0.10.0.orig.tar.gz
ce47e3c0a657127b56f07c63af419ce961efea77 29199 libxkbcommon_0.10.0-1.diff.gz
e6c2a5c2ddd8ea488622ce39a5173486f2230f33 8105 libxkbcommon_0.10.0-1_source.buildinfo
Checksums-Sha256:
5f60bd2c91196acba229e2d5a932798c64a18efd83577512b4fd8cd4bcdf4afa 2451 libxkbcommon_0.10.0-1.dsc
54b6f38a4ce77052d343e881aafece8e993f9bfc3db35a107e9bdca9b5b1a055 600904 libxkbcommon_0.10.0.orig.tar.gz
8fd8e43b53ff47c240505bb0b44dbb11456a0234f69a4ae28975ed6fec6bdfd3 29199 libxkbcommon_0.10.0-1.diff.gz
430f8d4cbb8b6fff733ddf9765b8adf4c6fc0890519b2f9a12b8ca4ec7a330a9 8105 libxkbcommon_0.10.0-1_source.buildinfo
Files:
64a9f1e297e96ea589de4be234f3783b 2451 x11 optional libxkbcommon_0.10.0-1.dsc
53b651a20528a1642a957d20bacf41d8 600904 x11 optional libxkbcommon_0.10.0.orig.tar.gz
f4d8e499c0718e036b0cf40b66c3e54d 29199 x11 optional libxkbcommon_0.10.0-1.diff.gz
b9bba033b4616bb2e157cbc064b808e2 8105 x11 optional libxkbcommon_0.10.0-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl47/ZYACgkQy3AxZaiJ
hNx8CA/8DpBiBqk+N9E6JfFnoB6kVIJfyYfvQgkkw9AqS7CnsEXym9CXtaLL9wmo
b7iBl5MnofII6f4ggQ5lkUTl+ibwkkrbhoSdyO4iRCvGX0LdVBtcvW955fKwgPs6
LSFk26v9mkEusrChTPN6dUfg/dtPEIDV12/3UpzRcAnDaxclq5QTd6OyyLOt+RSV
yPPURwy40mg2fUzQUVVuX3PemOpu11BkpkbUbgQ3w9J+GTJFv8mKZ/EtfsdKvM2q
lt5t1tddxL1oKWvYDbDVfFbX/rBSCDn7tHnnTuNNFN9gU+5X7uyfcMf1u8dK6K0X
ddikx8lRabJ8SeYIupCo2BwyBJgbwj5TyBuq5a3Y6TN0FEhLY+44U2IDUPSvLkzU
q5rwDFncQsfBZxhEIBGFOSrn8R4zzHD9JEnLMrqdT3+ZgwYvajccNzpD+xJVMHEk
TA+2TxbI03fEyXTpmoLLeEIHssJ/F9XKCz1RKfxJZOD70YE4p02SWbwhx5D9j9yw
XQldySKXvQ23ZC2AMzjX9Mg2pTh/Z4p9gDiQeUDuSsF0L2qEs/tf5y02lRSRf51i
hK4tzktz9trV1juLYvDMmJJxrZpuQh3L71et47azoNReceIdb2tTwpf3xqVmQMK6
4uZTM84ECuNuqZvVjmk8DaouTkBsjftRJRTYkwvCLIntxDkd7wE=
=QH17
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: