Debian Patches
Status for entangle/3.0-7
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Fix_meson_build.patch | meson: fix build for meson >=0.60.0 Replaced the positional arguments in i18n.merge_files with the data_dirs-keyword Fixes #67 (cherry picked from commit 54795d275a93e94331a614c8712740fcedbdd4f0) |
EorlBruder <eorl@bruder.space> | no | upstream, after v3.0 | 2022-01-12 | |
| Adapt-to-changing-gexiv2-APIs.patch | Adapt to changing gexiv2 APIs This is the minimal effort change to adapt to the APIs, error reporting is lacking / ignored, as the calling scenarios should gracefully degrade their behaviour. (cherry picked from commit 63059e0424d2acc80a4491b71a86a3dcafdc45c8) |
"Daniel P. Berrangé" <berrange@redhat.com> | no | upstream, after v3.0 | 2026-02-09 | |
| Use-either-libgirepository-2.0-or-libgirepository-1.0-as-.patch | build: Use either libgirepository-2.0 or libgirepository-1.0, as appropriate pygobject 3.52 and libpeas 1.38 have switched from libgirepository-1.0 to libgirepository-2.0, and the whole process (pygobject, libpeas and the application) must agree on a single version to use. Automatically detect the right one at compile-time. This checks both the pygobject version and the libpeas version. Conversely, pygobject is not necessarily guaranteed to be installed at the time that entangle is compiled, so we can't completely rely on being able to check its version. (cherry picked from commit efe1ce41d2f8e2f6eacc37450f517e142e2c6490) |
Simon McVittie <smcv@debian.org> | no | upstream, after v3.0 | 2025-10-22 | |
| meson-fix-GExiv2-GIR-name.patch | meson: fix GExiv2 GIR name The API bump means GExiv2-0.16 is needed instead of 0.10 (cherry picked from commit 7ac409bd9fe2528205547cad52c0072f00311f17) |
"Daniel P. Berrangé" <berrange@redhat.com> | no | upstream, after v3.0 | 2026-02-09 |