Removed rpms
============

 - phonon4qt5-backend-gstreamer
 - phonon4qt5-backend-gstreamer-lang

Added rpms
==========

 - virtualbox-guest-tools
 - virtualbox-kmp-default

Package Source Changes
======================

gdm
+- Update gdm-xvnc-start-session-failed.patch: Following the upstream
+  final solution(bsc#1219205 glgo#GNOME/gdm#909).
+
+- Add gdm-xvnc-start-session-failed.patch: None seat0 session runs
+  without running launcher(bsc#1219205 glgo#GNOME/gdm#909).
+
giflib
+- Update to version 5.2.2
+  * Fixes for CVE-2023-48161 (bsc#1217390), CVE-2022-28506
+    (bsc#1198880)
+  * Address SF issue #138 Documentation for obsolete utilities still
+    installed
+  * Address SF issue #139: Typo in "LZW image data" page
+    ("110_2 = 4_10")
+  * Address SF issue #140: Typo in "LZW image data" page ("LWZ")
+  * Address SF issue #141: Typo in "Bits and bytes" page ("filed")
+  * Note as already fixed SF issue #143: cannot compile under mingw
+  * Address SF issue #144: giflib-5.2.1 cannot be build on windows
+    and other platforms using c89
+  * Address SF issue #145: Remove manual pages installation for
+    binaries that are not installed too
+  * Address SF issue #146: [PATCH] Limit installed man pages to
+    binaries, move giflib to section 7
+  * Address SF issue #147 [PATCH] Fixes to doc/whatsinagif/ content
+  * Address SF issue #148: heap Out of Bound Read in gif2rgb.c:298
+    DumpScreen2RGB
+  * Declared no-info on SF issue #150: There is a denial of service
+    vulnerability in GIFLIB 5.2.1
+  * Declared Won't-fix on SF issue 149: Out of source builds no
+    longer possible
+  * Address SF issue #151: A heap-buffer-overflow in gif2rgb.c:294:45
+  * Address SF issue #152: Fix some typos on the html documentation
+    and man pages
+  * Address SF issue #153: Fix segmentation faults due to non
+    correct checking for args
+  * Address SF issue #154: Recover the giffilter manual page
+  * Address SF issue #155: Add gifsponge docs
+  * Address SF issue #157: An OutofMemory-Exception or Memory Leak
+    in gif2rgb
+  * Address SF issue #158: There is a null pointer problem in
+    gif2rgb
+  * Address SF issue #159 A heap-buffer-overflow in GIFLIB5.2.1
+    DumpScreen2RGB() in gif2rgb.c:298:45
+  * Address SF issue #163: detected memory leaks in
+    openbsd_reallocarray giflib/openbsd-reallocarray.c
+  * Address SF issue #164: detected memory leaks in GifMakeMapObject
+    giflib/gifalloc.c
+  * Address SF issue #166: a read zero page leads segment fault in
+    getarg.c and memory leaks in gif2rgb.c and gifmalloc.c
+  * Address SF issue #167: Heap-Buffer Overflow during Image Saving
+    in DumpScreen2RGB Function at Line 321 of gif2rgb.c
+- Added patch:
+  * giflib-5.2.2-no-imagemagick.patch
+    + do not use ImageMagick to resize one gif file. It creates a
+    build cycle.
+  * 0001-Clean-up-memory-better-at-end-of-run-CVE-2021-40633.patch
+    + upstream fix for CVE-2021-40633 (bsc#1200551)
+- Modified patches:
+  * PIE.patch
+  * reproducible.patch
+    + rediff to changed context
+
+- Define make_build for distributions which do not define them in
+  system macros
+
+- add reproducible.patch to avoid timestamp patching in the build
+  section and allowing it to build with -Werror=date-time
+
marble
+- Fix build fail with gcc7 on Leap 15
+  * Use gcc13 on compilation
+
+- Update to 23.08.4
+  * New bugfix release
+  * For more details please see:
+  * https://kde.org/announcements/gear/23.08.4/
+- No code change since 23.08.3
+
+- Update to 23.08.3
+  * New bugfix release
+  * For more details please see:
+  * https://kde.org/announcements/gear/23.08.3/
+- Changes since 23.08.2:
+  * snapcraft: initial import snapcraft files.
+
qemu
+- Fix bsc#1220799. Amended commit:
+  * [openSUSE]: Increase default phys bits to 42, if host supports that
+    (bsc#1205978, bsc#1219977, bsc#1220799)
+
sudo
+- Security fix: [bsc#1219026, bsc#1220389, CVE-2023-42465]
+  * Try to make sudo less vulnerable to ROWHAMMER attacks.
+  * Add sudo-CVE-2023-42465-1of2.patch sudo-CVE-2023-42465-2of2.patch
+
timezone
+- update to 2024a:
+  * Kazakhstan unifies on UTC+5.  This affects Asia/Almaty and
+    Asia/Qostanay which together represent the eastern portion of the
+    country that will transition from UTC+6 on 2024-03-01 at 00:00 to
+    join the western portion.  (Thanks to Zhanbolat Raimbekov.)
+  * Palestine springs forward a week later than previously predicted
+    in 2024 and 2025.  (Thanks to Heba Hamad.)  Change spring-forward
+    predictions to the second Saturday after Ramadan, not the first;
+    this also affects other predictions starting in 2039.
+  * Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00
+    not 00:00.  (Thanks to Đoàn Trần Công Danh.)
+  * From 1947 through 1949, Toronto's transitions occurred at 02:00
+    not 00:00.  (Thanks to Chris Walton.)
+  * In 1911 Miquelon adopted standard time on June 15, not May 15.
+  * The FROM and TO columns of Rule lines can no longer be "minimum"
+    or an abbreviation of "minimum", because TZif files do not support
+    DST rules that extend into the indefinite past - although these
+    rules were supported when TZif files had only 32-bit data, this
+    stopped working when 64-bit TZif files were introduced in 1995.
+    This should not be a problem for realistic data, since DST was
+    first used in the 20th century.  As a transition aid, FROM columns
+    like "minimum" are now diagnosed and then treated as if they were
+    the year 1900; this should suffice for TZif files on old systems
+    with only 32-bit time_t, and it is more compatible with bugs in
+    2023c-and-earlier localtime.c.  (Problem reported by Yoshito
+    Umaoka.)
+  * localtime and related functions no longer mishandle some
+    timestamps that occur about 400 years after a switch to a time
+    zone with a DST schedule.  In 2023d data this problem was visible
+    for some timestamps in November 2422, November 2822, etc. in
+    America/Ciudad_Juarez.  (Problem reported by Gilmore Davidson.)
+  * strftime %s now uses tm_gmtoff if available.  (Problem and draft
+    patch reported by Dag-Erling Smørgrav.)
+  * The strftime man page documents which struct tm members affect
+    which conversion specs, and that tzset is called.  (Problems
+    reported by Robert Elz and Steve Summit.)
+
+- update to 2023d:
+  * Ittoqqortoormiit, Greenland changes time zones on
+    2024-03-31.
+  * Vostok, Antarctica changed time zones on 2023-12-18.
+  * Casey, Antarctica changed time zones five times since
+    2020.
+  * Code and data fixes for Palestine timestamps starting in
+    2072.
+  * A new data file zonenow.tab for timestamps starting now.
+  * Fix predictions for DST transitions in Palestine in
+    2072-2075, correcting a typo introduced in 2023a.
+  * Vostok, Antarctica changed to +05 on 2023-12-18.  It had
+    been at +07 (not +06) for years.
+  * Change data for Casey, Antarctica to agree with
+    timeanddate.com, by adding five time zone changes since 2020.
+    Casey is now at +08 instead of +11.
+  * Much of Greenland, represented by America/Nuuk, changed
+    its standard time from -03 to -02 on 2023-03-25, not on
+    2023-10-28.
+  * localtime.c no longer mishandles TZif files that contain
+    a single transition into a DST regime.  Previously,
+    it incorrectly assumed DST was in effect before the transition
+    too.
+  * tzselect no longer creates temporary files.
+  * tzselect no longer mishandles the following:
+  * Spaces and most other special characters in BUGEMAIL,
+    PACKAGE, TZDIR, and VERSION.
+  * TZ strings when using mawk 1.4.3, which mishandles
+    regular expressions of the form /X{2,}/.
+  * ISO 6709 coordinates when using an awk that lacks the
+    GNU extension of newlines in -v option-arguments.
+  * Non UTF-8 locales when using an iconv command that
+    lacks the GNU //TRANSLIT extension.
+  * zic no longer mishandles data for Palestine after the
+    year 2075.
+- Refresh tzdata-china.diff
+
timezone-java
+- update to 2024a:
+  * Kazakhstan unifies on UTC+5.  This affects Asia/Almaty and
+    Asia/Qostanay which together represent the eastern portion of the
+    country that will transition from UTC+6 on 2024-03-01 at 00:00 to
+    join the western portion.  (Thanks to Zhanbolat Raimbekov.)
+  * Palestine springs forward a week later than previously predicted
+    in 2024 and 2025.  (Thanks to Heba Hamad.)  Change spring-forward
+    predictions to the second Saturday after Ramadan, not the first;
+    this also affects other predictions starting in 2039.
+  * Asia/Ho_Chi_Minh's 1955-07-01 transition occurred at 01:00
+    not 00:00.  (Thanks to Đoàn Trần Công Danh.)
+  * From 1947 through 1949, Toronto's transitions occurred at 02:00
+    not 00:00.  (Thanks to Chris Walton.)
+  * In 1911 Miquelon adopted standard time on June 15, not May 15.
+  * The FROM and TO columns of Rule lines can no longer be "minimum"
+    or an abbreviation of "minimum", because TZif files do not support
+    DST rules that extend into the indefinite past - although these
+    rules were supported when TZif files had only 32-bit data, this
+    stopped working when 64-bit TZif files were introduced in 1995.
+    This should not be a problem for realistic data, since DST was
+    first used in the 20th century.  As a transition aid, FROM columns
+    like "minimum" are now diagnosed and then treated as if they were
+    the year 1900; this should suffice for TZif files on old systems
+    with only 32-bit time_t, and it is more compatible with bugs in
+    2023c-and-earlier localtime.c.  (Problem reported by Yoshito
+    Umaoka.)
+  * localtime and related functions no longer mishandle some
+    timestamps that occur about 400 years after a switch to a time
+    zone with a DST schedule.  In 2023d data this problem was visible
+    for some timestamps in November 2422, November 2822, etc. in
+    America/Ciudad_Juarez.  (Problem reported by Gilmore Davidson.)
+  * strftime %s now uses tm_gmtoff if available.  (Problem and draft
+    patch reported by Dag-Erling Smørgrav.)
+  * The strftime man page documents which struct tm members affect
+    which conversion specs, and that tzset is called.  (Problems
+    reported by Robert Elz and Steve Summit.)
+
+- update to 2023d:
+  * Ittoqqortoormiit, Greenland changes time zones on
+    2024-03-31.
+  * Vostok, Antarctica changed time zones on 2023-12-18.
+  * Casey, Antarctica changed time zones five times since
+    2020.
+  * Code and data fixes for Palestine timestamps starting in
+    2072.
+  * A new data file zonenow.tab for timestamps starting now.
+  * Fix predictions for DST transitions in Palestine in
+    2072-2075, correcting a typo introduced in 2023a.
+  * Vostok, Antarctica changed to +05 on 2023-12-18.  It had
+    been at +07 (not +06) for years.
+  * Change data for Casey, Antarctica to agree with
+    timeanddate.com, by adding five time zone changes since 2020.
+    Casey is now at +08 instead of +11.
+  * Much of Greenland, represented by America/Nuuk, changed
+    its standard time from -03 to -02 on 2023-03-25, not on
+    2023-10-28.
+  * localtime.c no longer mishandles TZif files that contain
+    a single transition into a DST regime.  Previously,
+    it incorrectly assumed DST was in effect before the transition
+    too.
+  * tzselect no longer creates temporary files.
+  * tzselect no longer mishandles the following:
+  * Spaces and most other special characters in BUGEMAIL,
+    PACKAGE, TZDIR, and VERSION.
+  * TZ strings when using mawk 1.4.3, which mishandles
+    regular expressions of the form /X{2,}/.
+  * ISO 6709 coordinates when using an awk that lacks the
+    GNU extension of newlines in -v option-arguments.
+  * Non UTF-8 locales when using an iconv command that
+    lacks the GNU //TRANSLIT extension.
+  * zic no longer mishandles data for Palestine after the
+    year 2075.
+- Refresh tzdata-china.diff
+