On Tue, Nov 04, 2025 at 10:43:42PM -0600, John Goerzen wrote: > Hello, > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118629 pertains to a > bug that can be resolved in trixie by simply rebuilding ckermit from > source.
A rebuild is not really a solution for the root cause. The root cause of the problem is that OpenSSL changed it's version rules for ABI compatibility (1.0 and 1.1 were not ABI-compatible, but ABI is compatible among 3.x version), and C-Kermit still assumes the old one. The proper solution in this case is to patch out the OpenSSL check from C-Kermit and then backport that change in a pu request[1] for trixie. The actual requirement is already handled by the soname and the automatically generated dependency on libssl3t64. In the extremely rare case that a package actually has a stricter requirement than the soversion of the library, it would have to create a matching dependency like "libssl3t64 (>= 3.5), libssl3t64 (<< 3.6)" during the build. > I'd like to know how to accomplish this. Is there someone that I could > contact to do that? Or does it require a new changelog entry, and > source upload, to trixie-proposed-updates or some such? For a binNMU request (which might get rejected due to the above issue) do: reportbug release.debian.org 1 binnmu binNMU requests > Thanks, > > John cu Adrian [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#special-case-uploads-to-the-stable-and-oldstable-distributions
