Debian Patches
Status for localsearch/3.8.2-12
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Drop-file-notifier-and-miner-fs-tests.patch | Drop 'file-notifier' and 'miner-fs' tests There are flakiness problems here. |
Iain Lane <laney@debian.org> | no | 2021-06-10 | ||
| psx-game-image-1.expected.json-Mark-as-XFAIL.patch | psx-game-image-1.expected.json: Mark as XFAIL The test is newly run in 3.0, and seems to be buggy, see the upstream bug. |
Iain Lane <laney@debian.org> | no | 2021-06-09 | ||
| tiff-photo-1.expected.json-Mark-as-XFAIL.patch | tiff-photo-1.expected.json: Mark as XFAIL The test is newly run in 3.7.3, and seems to be buggy, see the upstream bug. |
Jeremy Bícha <jeremy.bicha@canonical.com> | no | 2024-05-02 | ||
| tracker-miners-Fix-bmp-basic-1-test-failures-on-big-endia.patch | tracker-miners: Fix bmp-basic-1 test failures on big-endian. Make sure w,h values in get_img_resolution() respects endianness. |
Gayathri Berli <Gayathri.Berli@ibm.com> | no | https://gitlab.gnome.org/GNOME/localsearch/-/merge_requests/574 | 2024-12-11 | |
| tests-decrease-deadline.patch | tests: decrease stall deadline to try to help build tests succeed on slower Debian build architectures like riscv64, hppa, sparc64 |
Jeremy Bícha <jeremy.bicha@canonical.com> | no | 2025-02-20 | ||
| extract-html-Don-t-assume-a-NUL-terminated-string-for-the.patch | extract/html: Don't assume a NUL-terminated string for the SAX callback The HTML parser or libxml2 used to always pass NUL-terminated string to the callback, but it's not documented and it no longer happens with libxml2-2.14.0. Fixes #391. (cherry picked from commit f3245004ecebf1a9829875bc6232fc94dddb2858) |
Xi Ruoyao <xry111@xry111.site> | no | 2025-03-31 | ||
| tests-Use-full-signature-in-function-definition.patch | tests: Use full signature in function definition Somehow, gcc >=15 decides that we no longer can use unspecified arguments. (cherry picked from commit 9a19e8326bb018aca0d30055909a8bcc4bb20d57) |
Carlos Garnacho <carlosg@gnome.org> | no | 3.9.0 | 2025-01-17 | |
| common-Cast-function-argument-to-expected-type.patch | common: Cast function argument to expected type Somehow, gcc >=15 now expects the exact signature for a GThreadFunc in g_once(). (cherry picked from commit c9d3679d9060b9afd8ab54d3c3cda462e5b0d49b) |
Carlos Garnacho <carlosg@gnome.org> | no | 3.9.0 | 2025-01-17 | |
| CVE-2026-1764.patch | extractor: Check for valid offsets extracting MP3 performer tags This could be tricked to run out of bounds, add some check to ensure it does not happen. |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.alpha | 2026-01-15 | |
| bug426.patch | extractor: Bail out on 0-size frame for ID3v2.0 tags The code handling ID3v2.3 and v2.4 tags already bailed out correctly, do this too for 2.0 tags, avoids a possible NULL pointer dereference. |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.alpha | 2026-01-15 | |
| CVE-2026-1765.patch | extractor: Check for buffer boundaries extracting MP3 TXXX tags This code could be tricked into reading out of bounds, add a check to ensure this does not happen. |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.alpha | 2026-01-15 | |
| CVE-2026-1766-pre1.patch | extractor: Minor code refactor The APIC tag is the same for ID3v2.3 and 2.4 frames, refactor its handling to a separate function, so the code is not repeated. |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.alpha | 2026-01-15 | |
| CVE-2026-1766.patch | extractor: Refactor/fix handling of COMM tags Refactor the code handling COMM tags for ID3v2.3 and v2.4, so they share a common implementation. In doing that, this also fixes a missing check for boundaries for ID3v2.3, which existed for v2.4. |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.alpha | 2026-01-15 | |
| CVE-2026-1767.patch | extractor: Fix accounting of offsets within MP3 performer tags We were moving two needles when parsing multiple performers, on one hand the base position within the MP3 frame, and on the other the offset accounted for locally within performers, this made us inadvertently pass maximum allowed lengths that actually were past the data frame. To avoid this confusion, keep the base position fixed as it happens during parsing of other tags, and only move the local offset variable. This fixes the invalid maximum lenghts being passed. |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.alpha | 2026-01-15 |
All known versions for source package 'localsearch'
- 3.8.2-12 (sid, forky)