Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 551690 - dev-tex/xmltex-1.9-r2 : fails ebuild :fmtutil: format directory `/var/tmp/portage/dev-tex/xmltex-1.9-r2/work/xmltex/base/texmf-var/web2c' does not exist.
Summary: dev-tex/xmltex-1.9-r2 : fails ebuild :fmtutil: format directory `/var/tmp/por...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: TeX project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-10 16:31 UTC by Jason Mours
Modified: 2018-01-21 15:10 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (xmltex-1.9-r2-build.log,1.95 KB, text/plain)
2015-06-10 16:31 UTC, Jason Mours
Details
emerge-info (xmltex-1.9-r2-emerge.info,17.73 KB, text/plain)
2015-06-10 16:32 UTC, Jason Mours
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Mours 2015-06-10 16:31:18 UTC
Having issues emerging dev-tex/xmltex-1.9-r2 :

fmtutil: format directory `/var/tmp/portage/dev-tex/xmltex-1.9-r2/work/xmltex/base/texmf-var/web2c' does not exist.

: This is the only snippet, I am still attaching build.log

Reproducible: Always
Comment 1 Jason Mours 2015-06-10 16:31:44 UTC
Created attachment 404904 [details]
build.log
Comment 2 Jason Mours 2015-06-10 16:32:05 UTC
Created attachment 404906 [details]
emerge-info
Comment 3 Karl-Johan Karlsson 2015-06-11 19:47:27 UTC
fmtutil is supposed to create that directory by itself, by calling mktexdir, and give that error message if it wasn't created (/usr/share/texmf-dist/scripts/texlive/fmtutil.sh line 590):

  test -d "$destdir" || mktexdir "$destdir" >/dev/null 2>&1
  test -d "$destdir" || abort "format directory \`$destdir' does not exist"

Where do you get these utilities from?

   # equery belongs `which fmtutil`
    * Searching for /usr/bin/fmtutil ... 
   app-text/texlive-core-2014-r4 (/usr/share/texmf-dist/scripts/texlive/fmtutil.sh)
   app-text/texlive-core-2014-r4 (/usr/bin/fmtutil -> ../share/texmf-dist/scripts/texlive/fmtutil.sh)

   # locate mktexdir
   /usr/share/texmf-dist/web2c/mktexdir
   /usr/share/texmf-dist/web2c/mktexdir.opt

   # equery belongs /usr/share/texmf-dist/web2c/mktexdir
    * Searching for /usr/share/texmf-dist/web2c/mktexdir ... 
   dev-libs/kpathsea-6.2.0_p20140525 (/usr/share/texmf-dist/web2c/mktexdir)

Do you get any error messages if you delete the ">/dev/null 2>&1" from the call to mktexdir at /usr/share/texmf-dist/scripts/texlive/fmtutil.sh:590?
Comment 4 Jason Mours 2015-06-11 21:36:07 UTC
(In reply to Karl-Johan Karlsson from comment #3)
> fmtutil is supposed to create that directory by itself, by calling mktexdir,
> and give that error message if it wasn't created
> (/usr/share/texmf-dist/scripts/texlive/fmtutil.sh line 590):
> 
>   test -d "$destdir" || mktexdir "$destdir" >/dev/null 2>&1
>   test -d "$destdir" || abort "format directory \`$destdir' does not exist"
> 
> Where do you get these utilities from?
> 
>    # equery belongs `which fmtutil`
>     * Searching for /usr/bin/fmtutil ... 
>    app-text/texlive-core-2014-r4
> (/usr/share/texmf-dist/scripts/texlive/fmtutil.sh)
>    app-text/texlive-core-2014-r4 (/usr/bin/fmtutil ->
> ../share/texmf-dist/scripts/texlive/fmtutil.sh)
> 
>    # locate mktexdir
>    /usr/share/texmf-dist/web2c/mktexdir
>    /usr/share/texmf-dist/web2c/mktexdir.opt
> 
>    # equery belongs /usr/share/texmf-dist/web2c/mktexdir
>     * Searching for /usr/share/texmf-dist/web2c/mktexdir ... 
>    dev-libs/kpathsea-6.2.0_p20140525 (/usr/share/texmf-dist/web2c/mktexdir)
> 


# equery belongs `which fmtutil`
 * Searching for /usr/bin/fmtutil ...
app-text/texlive-core-2014-r4 (/usr/share/texmf-dist/scripts/texlive/fmtutil.sh)
app-text/texlive-core-2014-r4 (/usr/bin/fmtutil -> ../share/texmfm-dist/scripts/texlive/fmtutil.sh)

# find /| grep mktexdir
/usr/share/texmf-dist/web2c/mktexdir.opt
/usr/share/texmf-dist/web2c/mktexdir
/var/tmp/portage/app-text/texlive-core-2014-r4/work/texlive-20140525-source/texk/kpathsea/mktexdir.opt
/var/tmp/portage/app-text/texlive-core-2014-r4/work/texlive-20140525-source/texk/kpathsea/mktexdir

# equery belongs /usr/share/texmf-dist/web2c/mktexdir
 * Searching for /usr/share/texmf-dist/web2c/mktexdir ...
dev-libs/kpathsea-6.2.0_p20140525 (/usr/share/texmf-dist/web2c/mktexdir)

> Do you get any error messages if you delete the ">/dev/null 2>&1" from the
> call to mktexdir at /usr/share/texmf-dist/scripts/texlive/fmtutil.sh:590?

And yes, stripping ">/dev/null 2>&1" from /usr/share/texmf-dist/scripts/texlive/fmtutil.sh:590 allows dev-tex/xmltex-1.9-r2.ebuild to emerge. This seems to correct my issue... But it doesn't seem like a fix, It looks like this is underlining another issue in dev-libs/kpathsea-6.2.0_p20140525 or app-text/texlive-core-2014-r4? Let me know if you would like a finished build.log of the dev-tex/xmltex-1.9-r2.
Comment 5 Karl-Johan Karlsson 2015-06-11 22:41:53 UTC
(In reply to Jason Mours from comment #4)
> And yes, stripping ">/dev/null 2>&1" from
> /usr/share/texmf-dist/scripts/texlive/fmtutil.sh:590 allows
> dev-tex/xmltex-1.9-r2.ebuild to emerge. This seems to correct my issue...

That's weird. That shouldn't make any difference to the result, just let you see any error messages.

Looking at my own system, it seems that mktexdir writes a bunch of stuff to /tmp first. Did that filesystem happen to be full or otherwise unavailable when it failed?

> Let me know if you would like a finished build.log of the dev-tex/xmltex-1.9-r2.

Did mktexdir write anything interesting? It would be any lines between:

   >>> Compiling source in /var/tmp/portage/dev-tex/xmltex-1.9-r2/work/xmltex/base ...

and

   fmtutil: running `pdftex -ini   -jobname=xmltex -progname=xmltex &latex xmltex.ini' ...
   This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (INITEX)
Comment 6 Karl-Johan Karlsson 2015-06-12 00:57:23 UTC
(In reply to Karl-Johan Karlsson from comment #5)
> Looking at my own system, it seems that mktexdir writes a bunch of stuff to
> /tmp first. Did that filesystem happen to be full or otherwise unavailable
> when it failed?

Sorry, that's of course not true when it is run by Portage under Sandbox. Temporary files get put in /var/tmp/portage/dev-tex/xmltex-1.9-r2/temp/.
Comment 7 Wilke Schwiedop 2015-07-13 11:50:46 UTC
dupe: https://bugs.gentoo.org/show_bug.cgi?id=500934