glib2.0 (2.75.2-1)
[PTS] [DDPO]
OK: VCS matches the version in the archive
- Git: https://salsa.debian.org/gnome-team/glib.git -b debian/experimental
-
- Branch: debian/experimental
- Path: debian/changelog
- Repo size: 144994304
- Browser: https://salsa.debian.org/gnome-team/glib
- Last scan: 2023-02-03 18:39:12+00
- Next scan: 2023-02-10 22:40:00+00
- Merge requests: 2
- CI pipeline status: success
- Debian changelog in Git:
glib2.0 (2.75.2-1) experimental; urgency=medium
* New upstream release
* d/copyright: Update
* Refresh patch series
* d/libglib2.0-0.symbols: Sort lines
* d/libglib2.0-0.symbols: Update for new ABI
* d/libglib2.0-0.symbols: Use stable-branch versions for older symbols.
We don't need to keep track of precisely which development release
included each symbol: it's enough to generate dependencies on the first
stable release that had it. Debian stable releases shouldn't include
GLib development releases anyway.
* d/p/Include-GObject-s-visibility-header.patch,
d/p/build-Don-t-overwrite-build-variables.patch,
d/p/glib-compile-schemas-Fix-typo-in-comparison-function.patch:
Add some post-release bug fixes from upstream
* d/p/tests-Improve-error-message-if-setting-max-processes-to-1.patch,
d/p/debian/06_thread_test_ignore_prctl_fail.patch:
Split up patch that skipped a test if unable to set RLIMIT_NPROC.
The part that improves the error message could be upstreamable, even if
skipping the test as a result isn't.
* d/p/debian/06_thread_test_ignore_prctl_fail.patch:
Try dropping this patch, to reassess whether we still need it.
* d/p/garray-Update-NULL-termination-after-copying-array-conten.patch,
d/p/garray-Avoid-calling-memcpy-with-no-items.patch:
Add proposed patches to fix a test failure
-- Simon McVittie <smcv@debian.org> Tue, 10 Jan 2023 13:54:58 +0000
- This branch is even with tag debian/2.75.2-1