Debian Patches
Status for tinysparql/3.11.1-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| disable-some-failing-tests.patch | Disable some failing tests In the autopkgtest setup some tests fail that pass during build. Ideally we figure out how to set it up correctly, but until then, let's skip these tests. |
Paul Gevers <elbrus@debian.org> | no | debian | 2023-02-15 | |
| exclude-web-ide.patch | exclude web-ide to match debian/copyright Files-Excluded |
Jeremy Bícha <jeremy.bicha@canonical.com> | no | 2024-08-15 | ||
| skip-manpage-test.patch | Skip manpage test I don't know why this test is failing in the autopkgtest environment man-db is Priority: standard The manpage tinysparql-import is installed in the tinysparql package |
Jeremy Bícha <jbicha@debian.org> | no | 2025-11-05 | ||
| tests-Handle-double-values-precision-changes-in-SQLite-3..patch | tests: Handle double values precision changes in SQLite 3.53.1 The release news of this SQLite version (https://sqlite.org/releaselog/3_53_1.html) has the following item: 9. Improvements to floating-point ↔ text conversions. a. Reimplemented to improve performance. b. Rounding is now done by default to 17 significant digits, instead of 15, as was the case for all prior versions. The sqlite3_db_config(SQLITE_DBCONFIG_FP_DIGITS) API (item 6g above) can change this, if desired. This is generally great, but these precision changes seep in our test suite. Adapt the SPARQL query tests that are returning double values so that these are converted to a string up to a precision defined in the query itself, and less dependent on implementation details. Ideally, these tests should use cursor getters for double values and compare with an epsilon, instead of these rough string comparisons we do. This is left as something for the future. (cherry picked from commit 47d5bf9313d0ccb1feb7169eed9047d0e1597a39) |
Carlos Garnacho <carlosg@gnome.org> | no | upstream, after 3.11.1 | 2026-05-12 |