Packages changed:
  drbd
  eyeD3 (0.9.6 -> 0.9.7)
  libX11 (1.8.2 -> 1.8.1)
  pam
  pam-full-src
  pcfclock
  perl-Bootloader (0.939 -> 0.940)
  purple-mattermost (2.0 -> 2.1)
  systemd
  urlscan (0.9.9 -> 0.9.10)

=== Details ===

==== drbd ====
Subpackages: drbd-kmp-64kb drbd-kmp-default

- BuildRequire %kernel_module_package_buildreqs (boo#1205149)

==== eyeD3 ====
Version update (0.9.6 -> 0.9.7)

- update to 0.9.7:
  - [fixup-plugin] Added --no-dir-rename.
  - Add remove-all-unknown to classic plugin. <gobater@users.noreply.github.com>
  - Track/disc number support for JSON/YAML plugins (and tests)
  - CountAndTotalTuple named tuple for count/total values.
  - EyeD3 __all__ includes core.AudioFile.
  - AudioFile.__str__ returns path.
  - Strict render Frame flag to continue on render errors. Applied to RelVolAdjFrameV24, etc
  - Track unsupported frames and add `--remove-all-unknown` classic plugin
    option (#586) <gobater@users.noreply.github.com>
  - Removed display-plugin due to Grako EOL (#585)
  - [stats] Print bytes as text and filter private members.
  - Remove Python 3.6 support, EOL. (#560)
  - Doc grammar fixed (#537) <74979584+piatrashkakanstantinass@users.noreply.github.com>
  - Fix problem when frame file format invalid, and input.read() returns
    no more data at all - this had the potential to loop endlessly. (#539)
    <gerson.kurz@ng-branch-technology.com, gerson.kurz@gmail.com>

==== libX11 ====
Version update (1.8.2 -> 1.8.1)
Subpackages: libX11-6 libX11-data libX11-devel libX11-xcb1

- Update to version 1.8.1
  This release fixes the --enable-thread-safety-constructor option to the
  configure script to work as intended.  In the previous release, the changes
  for this option may not have been enabled when the option was not specified
  or when the --enable option was specified.
  While we have enabled it by default, believing that doing so will reduce
  the number of bugs users encounter running libX11 clients, in some cases
  it may expose bugs in which clients had previously gotten away with calling
  libX11 functions while a libX11 lock is already held, and thus now deadlock,
  as discussed in https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157
- let's hope this version doesn't suffer yet from the regressions
  reported in boo#1205778, boo#1205818 (reported against 1.8.2);
  we need libX11 thread safe for totem (GNOME 43) :-(
- going back to version 1.7.5 for now to get rid of regressions,
  which were introduced by trying to get thread-safe in libX11
  itself
- re-introduced U_fix-a-memory-leak-in-XRegisterIMInstantiateCallback.patch
  which was not yet in 1.7.5
- supersedes the following patches
  * U_0001-Add-XFreeThreads-function.patch
  * U_0002-Don-t-use-pragma-inside-a-function-it-breaks-compili.patch
  * U_0003-Fix-797755-Allow-X-IfEvent-to-reenter-libX11.patch
  * U_0004-Indentation-fixes-around-recent-dpy-in_ifevent-chang.patch
  * U_0005-ChkIfEv.c-fix-wrong-handling-of-dpy-in_ifevent.patch

==== pam ====
Subpackages: pam_unix

- Move pam_env config files below /usr/etc

==== pam-full-src ====

- Move pam_env config files below /usr/etc

==== pcfclock ====

- BuildRequire %kernel_module_package_buildreqs (boo#1205149)

==== perl-Bootloader ====
Version update (0.939 -> 0.940)

- merge gh#openSUSE/perl-bootloader#140
- add basic support for systemd-boot
- 0.940

==== purple-mattermost ====
Version update (2.0 -> 2.1)
Subpackages: libpurple-plugin-mattermost pidgin-plugin-mattermost

- update to 2.1:
  * Fetch last 60 messages when a channel is joined for the first time from
    Pidgin.

==== systemd ====
Subpackages: libsystemd0 libudev1 systemd-container systemd-devel udev

- Don't ship symlink /usr/lib/environment.d/99-environment.conf
  anymore. /etc/environment is owned and parsed (among other config files) by
  pam_env(8), which is included by 'systemd-user' PAM service anyway.

==== urlscan ====
Version update (0.9.9 -> 0.9.10)

- update to 0.9.10:
  * Add "*" to allowed URL characters. Fix #125
  * Strip whitespace from URLs. Fixes #124
  * Redo redirection of sterr/stdout. Fix #122