Issue: make: *** [pdf] Error 83

[Ragamuffin-Asa]

Today I updated the phd_thesis_markdown template (after using a 2016 version for years without issues). However, when I tried to generate a pdf I got the following error: make: *** [pdf] Error 83

This happened after I resolved the error *** [pdf] Error 43 by updating tlmgr.

Anyone has any suggestions? I'm pretty much a tech noob, so any help would be appreciated ^^"

[tompollard]

@Ragamuffin-Asa sorry about this, we'll look into it!

[tompollard]

I see tests are failing (my bad, i think, for not checking an earlier merge properly!), though not sure if this is related:

tlmgr: main database at https://mirrors.concertpass.com/tex-archive/systems/texlive/tlnet is not signed
The command "if [ "$TRAVIS_OS_NAME" = "osx" ]; then
    eval "$(/usr/libexec/path_helper)"
    sudo tlmgr update --self
  elif [ "$TRAVIS_OS_NAME" = "linux" ]; then
    tlmgr init-usertree
    echo MSG FROM JO:
    echo on linux we cannot update apt installed texlive
    echo next steps to fix see commit msg: https://github.com/tompollard/phd_thesis_markdown/pull/100/commits/85fd9e7ac413a34066b79f1e49b3e1d3efdeac00
    echo c.f. https://tex.stackexchange.com/questions/551383/cant-run-tex-lives-tlmgr-in-a-github-action
    echo and https://tex.stackexchange.com/questions/1092/how-to-install-vanilla-texlive-on-debian-or-ubuntu

  fi
  " failed and exited with 1 during .

[Ragamuffin-Asa]

Thanks for looking into it. Since I was facing a deadline and a little rushed, I eventually solved it by exporting to .docx and (after changing the fonts etc) exported it to .pdf It was a way to get around the issue, but of course not as handy. I am going to have another look to see whether I am able to figure something out.

[dendrondal]

FWIW, it appears this issue arose before the merge. Strangely, the Jenkins build succeeded when he submitted the PR, but failed when I merged it. Judging by the error, it's a problem with the mirror that tlmgr update is pulling from. Perhaps their SSL certificate has expired since then, but I'm not 100% sure what we can do to fix this, unless we manually pull from another mirror. @JamesOwers let me know your thoughts since you've run into so many of the sharp edges with Travis.

[JamesOwers]

Hi @dendrondal - apologies for delay!

This issue should be solved. @Ragamuffin-Asa - can you reproduce your issue now when following the new quickstart instructions in the README.md?

@dendrondal - The issue with the Travis build is separate to this issue. For that, I recommend simply rerunning the build: https://stackoverflow.com/a/17624403/2550114

[aathanor]

I encountered the same problem, how it was solved? Thanks