Debian Patches
Status for transgui/5.18.0+dfsg-5
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| patch_connect_transmission_3.0 | Patch transmission remote gui to correctly connect to transmission 3.0 | Diesel1017 <diesel1017@gmail.com> | yes | upstream | other, https://github.com/Diesel1017/transgui/commit/7efff8d5476fc44465d765a1a59d1143147c7c74 | 2022-05-06 |
| build-with-qt5-widgetset.patch | Build with qt5 widgetset | Bastian Germann <bage@debian.org> | no | 2023-09-20 | ||
| 0003-windows-INVALID_HANDLE_VALUE.patch | windows INVALID_HANDLE_VALUE The const INVALID_HANDLE_VALUE is not defined on Linux, just MS Windows. |
"Barak A. Pearlmutter" <barak+git@pearlmutter.net> | no | 2025-06-22 | ||
| load-openssl3.patch | Load modern OpenSSL for HTTPS (e.g. GeoIP download) Two related problems prevent HTTPS from working on current Debian: . 1) rpc.pas's hardcoded libssl SONAME list stops at 1.1.0, which is absent from current Debian. The only dlopen target present is the legacy stub libssl.so.1.0.0 that cannot negotiate TLS 1.2+. . 2) CheckOpenSSL (the routine that probes the versioned SONAMEs and registers a real SSLImplementation) only runs when the Transmission RPC connection itself uses HTTPS. A plain-HTTP RPC user never triggers it, so when the GeoIP download (or flag image download, or adding a torrent from an HTTPS URL) tries HTTPS, synapse still has SSLImplementation := TSSLNone and fails with "SSL/TLS support is not compiled!". . Extend the SONAME list to include '3' and '1.1' (preferred first), and call RpcObj.InitSSL from TMainForm.FormCreate so the probe runs regardless of the RPC transport. FormCreate runs before the RPC worker thread exists and before any Http configuration has been applied, so there is no race on the shared THTTPSend. |
Andreas Noteng <andreas@noteng.no> | yes | 2026-04-18 |
All known versions for source package 'transgui'
- 5.18.0+dfsg-5 (forky, sid)
- 5.18.0+dfsg-3 (bookworm)
