Does not support filenames with whitespace

[Nikolaus Rath]

Binary package hint: latexmk

[0] nokile:~/Work/MPQ/paper$ latexmk Internship\ Report_Rath_Max\ Planck\ Institute.tex
This is latexmk, John Collins, 2 June 2004, version: 3.07a.
**** Report bugs etc to John Collins <collins at phys.psu.edu>. ****
------------
Run number 1 of latex [Internship Report_Rath_Max Planck Institute.tex]
------------
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
entering extended mode
! I can't find file `Internship'.
<*> Internship
               Report_Rath_Max Planck Institute.tex
Please type another input file name: ! I can't find file `Internship'.
<*> Internship
               Report_Rath_Max Planck Institute.tex
Please type another input file name:

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 RC or later?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[Nikolaus Rath (nikratio)]

There is no information missing here. Whether the bug is still present can trivially be checked by everybody, there is no need to ask the original reporter for it. All it takes is to execute the two lines

$ touch "long file name.tex"
$ latexmk "long file name.tex"

and one can immediately see that the bug is still present. At least in hardy.

I am sorry if I am a bit grunty, but I am really getting disappointed about this. It seems more and more common that the only answer that bug reporters get as a response to their efforts is a periodic "please confirm that the bug still exists". If at least someone would do something about the bug after such a question I would not complain, but usually there is nothing happening at all. This is just a waste of the bug reporter's time, especially if the bug can be extremely trivially reproduced with a minimum of effort.

[Mark Harrison (mark-z-harrison)]

This error is still present in jaunty and can be confirmed by using the same procedure described by Nikolaus. The error was fixed by the maintainer in September 2007 with version 3.21. The current version of latexmk is 4.08 which was released on June 23 of this year. For some reason, the version in the ubuntu repositories is 3.07, which is over 5 years old. The simplest solution seems to be upgrading the version in the repositories.

Until then, the easiest fix for users is to install the latest version from CTAN or the maintainer's website. I've tested this version and filenames with whitespace no longer present a problem.

Maintainer's version history:
http://www.phys.psu.edu/~collins/software/latexmk-jcc/versions.html

Maintainer's website:
http://www.phys.psu.edu/~collins/software/latexmk-jcc/

CTAN source:
http://ctan.tug.org/tex-archive/support/latexmk/

[Mark Harrison (mark-z-harrison)]

In case anyone is still interested in this, here is what happens when latexmk is run with a .tex file whose file name has whitespace.

~ > touch "multiple word tex file.tex"
~ > latexmk multiple\ word\ tex\ file.tex
This is latexmk, John Collins, 2 June 2004, version: 3.07a.
**** Report bugs etc to John Collins <collins at phys.psu.edu>. ****
------------
Run number 1 of latex [multiple word tex file.tex]
------------
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
 %&-line parsing enabled.
entering extended mode
! I can't find file `multiple'.
<*> multiple
             word tex file.tex
Please type another input file name:

As can be seen, latexmk parses files with whitespace in their name as separate files. This version of latexmk interprets "multiple word tex file.tex" as four separate files "multiple", "word", "tex", "file.tex".

As I said in my previous comment, this version of latexmk is badly out of date as this bug was fixed more than two years ago. I'll forward this but to the debian buglist to see if this issue can be resolved there.

[Erik Auerswald (auerswal)]

This is fixed in Ubuntu 18.04 LTS, at least for me, probably because a newer latexmk version is included. :-)

"Latexmk: This is Latexmk, John Collins, 1 January 2015, version: 4.41."

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
$ latexmk --version

Latexmk, John Collins, 1 January 2015. Version 4.41
$ apt-cache policy latexmk
latexmk:
  Installed: 1:4.41-1
  Candidate: 1:4.41-1
  Version table:
 *** 1:4.41-1 500
        500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
        100 /var/lib/dpkg/status

Thanks,
Erik