On Mon, 29 Jul 2019 23:46:57 +0900 Osamu Aoki <os...@debian.org> wrote: > Package: src:sphinx > Version: 1.8.4-1 > Severity: normal > > -M option doesn't work well except for a very simple case. I faced this > problem while building multi-language source. […] > I wanted to move the cache directory to a particular FOO, so I did: > $ sphinx-build -M gettext -d FOO source build > > This creates: > new file: FOO/gettext/environment.pickle > new file: FOO/gettext/index.doctree > new file: FOO/gettext/scope.doctree > new file: build/index.pot > new file: build/scope.pot
I experience a similar problem with -M latexpdf in combination with the -D option. If I do: sphinx-build -M latexpdf -D release=v1.0 source build Then a directory “release=v1.0” is created (populated by doctrees) and the build breaks when trying to compile the LaTeX source to PDF. Experienced with sphinx-build 5.3.0-7. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
