Pandoc template directory changed after update

Hello everyone,

I’ve just updated the ghc-pandoc package with zypper dup. Now, when I try to call pandoc (from the pandoc to convert from markdown to PDF, I get the following error message:

> pandoc example_file.md -o example_file.pdf
Could not find data file /usr/share/pandoc-3.1.9/data/templates/default.latex

There is no folder /usr/share/pandoc-3.1.9/. There is, however, a folder /usr/share/pandoc-3.1.11/ which has the required file templates/default.latex.

Zypper shows me that the ghc-pandoc package version is 3.1.11:

> zypper se -si pandoc
Loading repository data...
Reading installed packages...

S  | Name                    | Type    | Version     | Arch   | Repository
---+-------------------------+---------+-------------+--------+----------------------
i  | ghc-commonmark-pandoc   | package | 0.2.2-1.1   | x86_64 | Main Repository (OSS)
i  | ghc-pandoc              | package | 3.1.11-1.1  | x86_64 | Main Repository (OSS)
i  | ghc-pandoc-types        | package | 1.23.1-2.1  | x86_64 | Main Repository (OSS)
i+ | pandoc-cli              | package | 0.1.1.1-1.6 | x86_64 | Main Repository (OSS)
i  | python311-pandocfilters | package | 1.5.0-2.2   | noarch | Main Repository (OSS)

But when I check the version of the pandoc command, I get 3.1.9:

> pandoc -v
pandoc 3.1.9
...

What can I do to fix the issue?

Thank you very much for your help!

The current version is 0.1.1.1-1.7. Wait until it is available in Tumbleweed.

Thank you very much for your help :+1:

Is there a simple check which would have helped me avoid my mistake of updating ghc-pandoc without the corresponding version of pandoc-cli being available?

If one package fails to run without the exact version of another package it should be recorded in package dependencies. So it sounds like a packaging issue. You may consider opening bug report on https://bugzilla.opensue.org/ (same user/password as here).

Currently pandoc-cli just requires ghc-pandoc >= 3.0. Anyway, version 0.1.1.1-1.7 is available in 20240104 Tumbleweed snapshot.

1 Like

@arvidjaar, as you said, the 20240104 Tumbleweed snapshot fixed the issue.