Maximum runs of pdflatex reached without getting stable files about svg HOT 7 CLOSED

What I did for this is to configure latexmk to ignore changes for pdf files by adding this into .latexmkrc

$hash_calc_ignore_pattern{'pdf'}='^';

(https://tex.stackexchange.com/questions/347980/how-to-make-latexmk-ignore-certain-input-files-as-dependencies/348361#348361)

from svg.

XeTeX now provides \filemoddate which will be supported with svg version v2.03

from svg.

Thanks, that did the trick!

However, I still think this is an issue worth solving in this package as well. If I understand it correctly, latexmk will look at the hash of each file to see if any of them have been modified and if that is the case it will rerun the build process. This means (i think) that the svg package rebuilds the pdf every run, even if the svg has not changed and the pdf was already generated. In my opinion, this should be prevented.

from svg.

Yeah, I agree it was kinda hack-y.

The idea of checking the hash is also mentioned in #11 though. My bad, misread the reply.

from svg.

Yes, I do.

OK this explains it. Too bad there's no built-in workaround... anyway, the workaround above seems to work fine, so I'll stick with that for now.

from svg.

Yes, I do.

OK this explains it. Too bad there's no built-in workaround... anyway, the workaround above seems to work fine, so I'll stick with that for now.

(I fat-fingered and deleted the reply... Original reply is here for future reference)

Do you happen to use xelatex?
From the package documentation:

Unfortunately a primitive like \pdffilemoddate is missing for XeTeX, so with this engine, the behaviour will be the same as inkscape=forced

Is this possibly the cause?

from svg.

Seems like the new version is still regenerating pdfs...
I updated to texlive 2019 (on Ubuntu 19.10), the svg package is up-to-date right?

It's not. My bad!

from svg.