Build generating files with pdf.md extension about comply

[binil]

I ran into this same issue. I suspect this is because Pandoc recently changed the way they calculate table column widths (jgm/pandoc@bd7c9eb and jgm/pandoc@7c4d7db).

I got past this issue by changing default.latex as:

\usepackage{longtable,booktabs,array}
\usepackage{calc} % for calculating minipage widths

The current default.latex file after f4f46ba contains these changes. Fetching the file and using it also seem to work.

[kavashgar2]

Hi , we use
docker run --rm -v "$PWD":/source strongdm/comply -c 'comply build'

How can I change default.latex value

[kavashgar2]

I ran into this same issue. I suspect this is because Pandoc recently changed the way they calculate table column widths (jgm/pandoc@bd7c9eb and jgm/pandoc@7c4d7db).

I got past this issue by changing default.latex as:

\usepackage{longtable,booktabs,array}
\usepackage{calc} % for calculating minipage widths

The current default.latex file after f4f46ba contains these changes. Fetching the file and using it also seem to work.

hi we use
docker run --rm -v "$PWD":/source strongdm/comply -c 'comply build'

How can I change default.latex value

[wallrony]

Hello @dineshreddy, sorry for the delay. In the commit c78f900 we solved some pandoc build problems referencing some issues about infinite build in some environments and syntax errors, what we discovered that the cause was basically the version of pandoc which was outdated. So, I think that your problem will be solved if you use the most recent version of Comply, since that your issue was created before the commit merge. Please try this and give some feedback.

[wallrony]

@kavashgar2 you don't need to change the default.latex file, if you update the project (or the strongdm/comply image) you should not have any problems. Otherwise, please give more information about your environment (e.g.: OS, OS Version, Comply Version, etc.) so we can try to replicate the scenario.