Bug#1093946: espeak-ng: de-key-ify ruby-kramdown etc
Samuel Thibault
sthibault at debian.org
Sat Jan 25 01:09:57 GMT 2025
Sebastian Humenda, le ven. 24 janv. 2025 21:40:12 +0100, a ecrit:
> Samuel Thibault schrieb am 24.01.2025, 20:40 +0100:
> >Chris Hofstaedtler, le ven. 24 janv. 2025 20:28:18 +0100, a ecrit:
> >> 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
> […]
> >> 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.
> […]
> >I'll be happy to see somebody submit a patch to upstream that fallsback
> >to another md-to-html processor that would be less trouble (I have no
> >idea what could be used here, at best it'd be pandoc, which is most
> >probably really not a good idea :)
>
> What is the issue with Pandoc?
Is ghc already a key package?
Samuel
More information about the Pkg-a11y-devel
mailing list