Hi,
I cannot really grasp at the moment whether there are still problems?
Is everything working for you now?
> severity: wishlist Re the large size of texlive-lang-cjk: It would be
> nice if we can selectively install C-part, K-part and J-part of CJK of
> texlive-lang-cjk.
Is already done in TeX Live 2014 which is in experimental,, and will
be uploaded to unstable as soon as TL2014 is released.
> tex -kpathsea-debug=-1 -recorder foo.tex 2>foo-debug.log
That looks all fine and works, as you have noticed.
> BTW, the strange problem of ".fmt not found" seems to have been cured by
> running latex once under superuser. (So I am skeptical
So that means
THere are no problems anymore!
Is this correct?
Or do you still have a format where the problem occurs?
> Are ".fmt" files created into system installation directory? But, if
At installation time and when run as root with fmtutil-sys, they
are copied into
/var/lib/texmf/web2c/
If user runs it (which *should*not*be*necessary*) the are copied into
~/.texmf-var/
In both cases, if the disk space is exhausted, this will not
succeed.
> so, this is done when a user issues a TeX-related command by running
> setuid binary, correct?
No setuid package here.
> Anyway, if a file space issue happened during installation, it was
> not obvious to me.
I still think that this is the only explanation.
> *BUT*, usually, when file system space issue arises during package
> installation, apt-get or aptitude clearly fails and so I can take
The fmtutil run creates dump files that are several MB, my
/var/lib/texmf/web2c weights 93M. That means, if there are
not 93M free, it will fail in fmtutils-sys, then free the space,
and return to apt.
> If a run-time generated file could not be created due to space issues,
> then it ought to be reported clearly. Maybe an fmt-generation program
> or something did not report the error during (f)write or (f)close
That can be. But it should error out in this case. The fmtutil
script is running with
set -e
so failure to do the copy should be obvious.
Ah, one more idea: What is the output of
dpkg -l tex-common
> Also, I doubt the space issue because of another reason. As I wrote
> this message, I re-ran my XML->TeX->PDF conversion script using the
> latest texlive-lang-cjk (and many other packages, dblatex xetex, etc.)
> and it successfully ran to create a PDF under an ordinary user
> account. So I doubt if the space issue is the cause of strange
> behavior, but who knows :-(
Maybe you have cleaned up space in the meantime?
Think about what happens when you *install* a package:
* download a copy
* unpack
* check overwrites
* move the files to the right place
THat means intermediately 2-3 times the size is necessary.
After that, space is freed up. And if you clean your apt cache
(apt-get clean) then lots of space is freed up.
> I have been trying to see what went wrong myself even before the bug
> post, but could not come up with a possible candidate and explanation of
> self-healing (after running latex under superuser account) myself.
But this is the only explanation I see ...
> I still think that running latex under superuser may have
> changed/fixed permannently something (broken symlink/permission
No.
> bit/??? or as you suggest create a fmt file in a file system where it
> could not be made by an ordinary user due to some reason (possibly a
> temporary space issue?)).
Yes. That is the problem. But that should have happened at
installation time.
Again, what is the status of tex-common? (dpkg -l tex-common)
> I am wits' end. Is it possible that there could have been an issue
> using the package(s) from TESTING repository?
I am not sure, but that should be fine...
> Finally, would you like me to run the seemingly destructive command?
It is not necessary anymore, right? Everything works? Or what does
not work?>
If "ptex" does not work, please run the above command (with debug and
recorder) with ptex, too!
> Hmm., to see that you suggest that I run this as root, then I suppose
> these format ought to have been created during installation under
> super-user for system-wide sharing. That means there is a possibility
> that they failed for some mysterious reason [and was not reported back
> to the installer and the user clearly???]
Yes, that is why I ask for the output of
dpkg -l tex-common
which is responsible for building the formats.
Norbert
------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
