From: sebastian@breakpoint.cc   
      
   On 2026-02-09 08:53:14 [+0900], Dominique Martinet wrote:   
   > But that breaks all packages with an explicit `Depends: libssl3` in   
   > control rule -- and given it only breaks on armhf I'm not convinced it's   
   > intended, nor that many people would notice, which is why I reported it.   
      
   No package within the Debian pool does have such a Dpends:.   
      
   > (Although now that I think about it, they shouldn't need it at all   
   > because dynamic library dependencies are automatically picked up...   
   > So I'll just tell my coworker to "just don't do that" and leave it   
   > there; but I still think there's something weird with the lack of   
   > provides on armhf now the t64 transition is finished...)   
      
   Once there is a so bump and everything migrates to libssl4 then again   
   the manual installation of libssl3t64 will break. If you leave it as-is   
   then it will be pulled once required. During an upgrade (such as   
   Bookworm to Trixie) the automatic installed libssl3 will be automatically   
   removed once libssl3t64 is there and the former has no dependencies.   
      
   Sebastian   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)