Debian Patches

Status for lightning-matrix/0.10.6+dfsg1-2

Patch Description Author Forwarded Bugs Origin Last update
0001-cmake-optional-cargo-locked.patch Let cargo resolve crates against the distribution's packages Upstream builds with --locked against rust/Cargo.lock, which pins versions
the archive does not carry. Add LIGHTNING_CARGO_LOCKED (default ON, so
upstream behaviour is unchanged); debian/rules turns it OFF.

===================================================================
Erich Eickmeyer <eeickmeyer@ubuntu.com> not-needed 2026-10-18
0002-rust-drop-deepfilternet.patch Drop the DeepFilterNet dependency The DeepFilterNet model weights have no explicit licence upstream, and its
tract dependency tree is not in the archive. Remove the optional path
dependency so cargo never has to resolve it; the Rust code already reports
the backend as unavailable when the feature is absent.
Erich Eickmeyer <eeickmeyer@ubuntu.com> not-needed 2026-10-18
0003-update-disable-network-checks.patch Disable the in-app update checker Debian/Ubuntu owns updates for this package through the archive, and this
build must never contact an outside host on its own. UpdateManager::
startCheck() is the single chokepoint every check and download leads back
to: checkForUpdates() (the manual action), maybeCheckAutomatically() (the
startup timer) and downloadUpdate() (gated on reaching the UpdateAvailable
state, itself only reachable from a successful check) all go through it.
Refusing there unconditionally, ahead of its own development-build and
trust-key gates, disables every path at once, including the
LIGHTNING_ALLOW_DEV_UPDATE_CHECK diagnostic override.
.
Also adds UpdateManager::checksDisabledByPolicy (reading the same
kChecksDisabledByPolicy flag startCheck() refuses from) and uses it in
qml/UpdatesSettingsSection.qml to replace the "Automatic checks" toggle
and the "Check for updates" button with a fixed notice, and to hide every
check-result state in the "Status" card (Idle/Checking/UpToDate/
UpdateAvailable/Downloading/Verifying/ReadyToInstall/Installing/
RestartRequired/Failed). Without this, the automatic startup timer still
flips the backend to Failed every launch (harmlessly, with no network
involved) and the pane would show that as an alarming, misleading error
banner. updateLastResultBlock (the previous install's outcome, from the
helper's status file) is unrelated to checking and is left alone.

===================================================================
Erich Eickmeyer <eeickmeyer@ubuntu.com> not-needed 2026-10-23
0004-cmake-skip-deepfilternet-inputs-when-disabled.patch Do not list excluded third_party/deepfilternet paths as a Ninja DEPENDS The +dfsg repack excludes third_party/deepfilternet (its model weights carry
no licence upstream; see debian/README.source), and
LIGHTNING_ENABLE_DEEPFILTERNET is always OFF for this package (see
0002-rust-drop-deepfilternet.patch). LIGHTNING_DEEPFILTERNET_CARGO_INPUTS
still listed those paths unconditionally as a custom command's DEPENDS;
Ninja hard-fails a DEPENDS entry that is neither present on disk nor the
output of another build rule, so this would FTBFS once the paths no longer
exist. Make the list conditional on the feature actually being enabled.
Erich Eickmeyer <eeickmeyer@ubuntu.com> not-needed 2026-10-29
0005-rust-use-system-sqlite.patch Use Debian's system libsqlite3 instead of a bundled copy Do not request matrix-sdk's bundled-sqlite feature, so matrix-sdk-sqlite's
own "bundled" feature (and therefore rusqlite/libsqlite3-sys's "bundled"
feature, which compiles a private copy of SQLite into the binary) is never
enabled anywhere in the dependency graph. Verified against Cargo.lock:
rusqlite has exactly two consumers in the whole ~450-crate tree
(matrix-client-rust's own direct dependency, already default-features =
false with no "bundled"; and matrix-sdk-sqlite, whose "bundled" feature is
reached only through matrix-sdk's own "bundled-sqlite"), so removing it here
is sufficient.
.
Upstream chose bundled-sqlite because FTS5 (needed by the local message
index) is a compile-time SQLite option that is not universally enabled, and
explicitly raises the floor to the bundled amalgamation's version. Debian's
libsqlite3 has carried -DSQLITE_ENABLE_FTS5 since 2017 (confirmed on the
current archive build: `PRAGMA compile_options` on the shared library
reports ENABLE_FTS5, and `nm -D` on it exports sqlite3Fts5Init), so the
system library already meets the requirement this package needs.
Build-Depends gains libsqlite3-dev; pkgconf and librust-pkg-config-dev
(libsqlite3-sys's own pkg-config probe) are already present.
Erich Eickmeyer <eeickmeyer@ubuntu.com> not-needed 2026-10-29
0006-cmake-link-system-sqlite.patch Link libsqlite3 explicitly when the Rust backend is not bundled 0005-rust-use-system-sqlite.patch drops matrix-sdk's bundled-sqlite cargo
feature, so libsqlite3-sys links libsqlite3-sys dynamically against the
system library via a `cargo:rustc-link-lib=sqlite3` directive from its own
build.rs. That directive only reaches a consumer inside the same cargo
build graph; CMake treats the Rust staticlib as a prebuilt IMPORTED archive
(matrix-client-rust) and does not read cargo's native-link metadata at all,
the same reason dl/pthread/m are already named explicitly a few lines above
this change ("Rust static libraries commonly need libdl/libpthread/libm").
Without this, the final lightning-matrix link would fail with undefined
references to sqlite3_* symbols.
.
Adds LIGHTNING_RUST_SYSTEM_SQLITE (default OFF, matching upstream's bundled
default) rather than linking libsqlite3 unconditionally, so this patched
tree still builds correctly for anyone who re-enables bundled-sqlite.
debian/rules passes -DLIGHTNING_RUST_SYSTEM_SQLITE=ON.

===================================================================
Erich Eickmeyer <eeickmeyer@ubuntu.com> not-needed 2026-10-29

All known versions for source package 'lightning-matrix'

Links