* Samuel Thibault <[email protected]> [250124 20:24]: > Chris Hofstaedtler, le ven. 24 janv. 2025 20:19:41 +0100, a ecrit: > > On Fri, Jan 24, 2025 at 02:44:55AM +0100, Samuel Thibault wrote: > > > Chris Hofstaedtler, le ven. 24 janv. 2025 02:33:20 +0100, a ecrit: > > > > espeak-ng build-depends on ruby-kramdown, which transitively > > > > build-depends on ruby-em-socksify. > > > > > > Err, does it? I don't see it appear in apt build-dep ruby-kramdown in a > > > sid chroot. > > espeak-ng 1.52.0+dfsg-4 Build-Depends: kramdown, so yes :) > > I still don't understand: > > apt build-dep espeak-ng > > doesn't bring ruby-em-socksify either.
Yes, this is true. This is a transitive build-dep chain: espeak-ng build-depends ruby-kramdown ruby-kramdown build-depends ruby-stringex ruby-stringex build-depends rails rails build-depends ruby-webmock ruby-webmock build-depends ruby-em-socksify So you'll never see ruby-em-socksify when building espeak-ng. But you can change the choice of markdown implementation to influence the key package set :) With the available data it's hard to tell if changing espeak-ng will indeed stop making rails, ruby-webmock, ruby-em-socksify key. But if you have the cycles, please give it a try. Chris
