Commit cf7d610
committed
debian/control: add libgnutls30t64 to Conflicts/Replaces/Provides
Debian Trixie and Ubuntu Noble underwent the t64 transition (time_t
becomes 64-bit on 32-bit archs), which renamed libgnutls30 to
libgnutls30t64. The upstream libgnutls30t64 binary package declares
'Provides: libgnutls30' as a transition stub so most consumers
continue to work transparently.
But this gnutls-wolfssl source package's drop-in-replacement clauses
list only libgnutls30. On a fresh Trixie host (which has
libgnutls30t64 installed providing virtual libgnutls30), apt refuses
to install gnutls-wolfssl:
gnutls-wolfssl conflicts with libgnutls30; libgnutls30t64 provides
libgnutls30 and is present and installed.
Standard Debian t64 transition pattern is to extend the lists to
include both names. This is what Debian's own openssl source package
did (libssl3 -> libssl3t64).
The change is unconditional and safe across suites:
- On Bookworm and pre-t64 systems, there's no libgnutls30t64 to match
against, so the t64-specific clauses are inert. No behavior change.
- On Trixie and post-t64 systems, the t64 clauses let apt resolve
the drop-in replacement correctly and install gnutls-wolfssl
cleanly over the system's libgnutls30t64.
Discovered while building gnutls-wolfssl for Debian Trixie/amd64 on
2026-05-24 in the wolfSSL FIPS-eval channel pipeline. The
FIPS-eval build harness has been sed-patching debian/control at
build time as a workaround; this commit lands the fix upstream so
the workaround can be removed from downstream pipelines.
Refs: https://wiki.debian.org/ArmHfPort/64bit_time_t (t64 transition
background)1 parent 81679dd commit cf7d610
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
34 | | - | |
35 | | - | |
36 | | - | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
| |||
0 commit comments