Closed drphilmarshall closed 7 years ago
OK @kadrlica , I have hit a wall - travis
is consistently refusing to allow latexmk
to write to a file called .bib
, and I can't figure out how to stop it. The latest travis report is here, and the exact error is as follows:
pdflatex: Not writing to .bib (openout_any = p).
! I can't write on file `.bib'.
I cannot edit the texmf.cnf
file in travis
's texlive
installation because I don't have permission (even with sudo). The issue seems to be security: texmf.cnf
contains the line openout_any = p
, (for "paranoid"), which prevents latex
from writing to unusually-named files, like .bib
or .rhosts
etc.
One possibility could be to fall back to vanilla pdflatex
(which does not write to a .bib
file), perhaps?
In other news, I made some other things better in this branch along the way, so it could be merged any time (although that will also close #29 and #31, because I merged both the updates and lsstdescnote.cls branches into this one :-))
I ran across this while installing aastex6.1.cls
:
http://journals.aas.org/authors/aastex/linux.html
It might solve your .bib
problem.
Excellent, thanks @kadrlica ! That fixed it: PDF is now compiling successfully at travis :-) Now to figure out my GitHub API key...
Success! PDF is now deployed to the pdf
branch at:
However, in future this should only be updated if the master branch is updated, so I've set up the travis file accordingly. (The existing PDF is a relic, from before I fixed this.) I think this PR is OK to be merged - and when we do, we'll see if the PDF gets updated! :-)
I started this branch in response to #27, and to try to help out the CCL group. However, their repo is private, so I can't make travis do the work there. So, I'll use this branch to build our own note's PDF, instead. This will mean setting up travis etc. Note that I pre-merged PR #31 (new cls file) and PR #29 before starting work (here's hoping they pass code review soon!)