Changelog for xkbcomp-1.4.6-2.1.x86_64.rpm :

* Sun Dec 18 2022 Dirk Müller - update to 1.4.6:
* configure: Use AC_SYS_LARGEFILE to enable large file support
* suppress four more warnings when \'warningLevel\' is zero
* suppress the \"Could not resolve\" warning when \'warningLevel\' is zero
* man page: remove out-of-date COPYRIGHT section
* Build xz tarballs instead of bzip2
* Fix \"upercase\" typo
* Sat May 01 2021 Dirk Müller - modernize spec file (move license to licensedir)
* Wed Mar 17 2021 Stefan Dirsch - Update to version 1.4.5
* Remove trailing whitespaces
* gitlab CI: add basic build test
* Replace WARN[1-9], ERROR[1-9], etc. with their unnumbered version
* Downgrade the warning for missing symbols to info
* keycodes: downgrade the >255 keycode warning to an info
* keycodes: compress the high keycode warning
* Thu Nov 05 2020 Stefan Dirsch - Update to version 1.4.4
* Fix spelling/wording issues
* Fix lockdevbtn to be XkbSA_LockDeviceBtn action
* For -R and after chdir, add the current directory to the path
* Don\'t pretend unresolved symbols are an error
* Fri Feb 21 2020 Stefan Dirsch - Update to version 1.4.3
* Update configure.ac bug URL for gitlab migration
* configure: Remove unused AC_SUBST([REQUIRED_MODULES])
* pkgconfig: Remove unneeded Requires.private
* Suppress high-keycode warnings at the default warning level
* xkbcomp Fix missing support for \"affect\" and incorrect modifier handling for ISOLock
* Don\'t compare with string literals
* Fix invalid error report on F_Accel field
* Error out if we have no default path
* Fri Jun 08 2018 sndirschAATTsuse.com- Update to version 1.4.2
* Only one patch, fixing keymap compilation errors when the keycodes maximum is set to a value above the permitted X11 maximum of 255. While we already ignored keys with codes above 255, we still failed on the maximum=374; line that xkeyboard-config 2.24 produces now.
* Mon Mar 05 2018 sndirschAATTsuse.com- Update to version 1.4.1
* This release adds the path of the xkbcomp executable to the pkgconfig data, allowing the X server to find the right binary regardless of where its (the X servers) $prefix is pointed. Without this the X server will guess that xkbcomp is configured for the same prefix; since the default prefix is /usr/local, and your distribution certainly did not install xkbcomp there, \'make check\' and \'ninja dist\' for the X server build would fail because Xvfb would not start.- supersedes U_xkbcomp_pkgconfig-add-bindir.patch- refreshed xkbcomp.keyring; seems signing key changed, since this time the package has been released by Adam Jackson (before: Daniel Stone)? Hope I got this right ...
* Mon Nov 20 2017 zaitorAATTopensuse.org- Add U_xkbcomp_pkgconfig-add-bindir.patch: pkgconfig: Add our bindir to xkbcomp.pc.
* Tue May 02 2017 sndirschAATTsuse.com- Update to version 1.4.0
* This xkbcomp release mostly contains a couple of bugfixes and parser improvements. Notably, ignoring keycodes that X11 can never support means that we can start using those keycodes, which xkbcommon supports.- refreshed xkbcomp.keyring; seems signing key changed, since this time the package has been released by Daniel Stone (before: Peter Hutterer)? Hope I got this right ...
* Fri Nov 13 2015 mpluskalAATTsuse.com- Use url for source- Add gpg signature- Make building more verbose