Hi all,
(see https://bugs.launchpad.net/bugs/122863)
this is going to the debian-tex-maint list, too, since we could be hit
by this, too. Frank, please take a look.
The OP upgraded from feisty to gutsy on 2007-06-28.
feisty containes:
xmltex 1.9-11.1ubuntu1
jadetex 3.13-7.1ubuntu2
tex-common 0.42
gutsy at this time contained:
xmltex 1.9-12
jadetex 3.13-8ubuntu1
tex-common 1.9
At the upgrade time ...
> When the post-inst script of texlive-base-bin runs, it spawns around 900
> "etex" processes in the first step ("Running mktexlsr...").
> When running the second step ("Building format(s)...") it gets up to
> around 2500 "etex" processes, until the system reached a load average of
> 731 and i killed the post-inst script.
As usual, removing xmltex and jadetex fixed the problem:
On Sam, 30 Jun 2007, Mads Chr. Olesen wrote:
> removing xmltex and jadetex seems to solve the problem :-)
> Thanks! - I guess this bug can be closed
What wonders me is that this did happen at all.
As far as I see, since the tex-common 1.8 was introduced definitely
*before* the tried upgrade, it should have been selected for the
upgrade and the whole stuff shouldn't have happened.
Frank, do you have any explanation for this? And whether this could
happen to etch->lenny upgrade, too?
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <[EMAIL PROTECTED]> Vienna University of Technology
Debian Developer <[EMAIL PROTECTED]> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
BERKHAMSTED
The massive three-course midmorning blow-out enjoyed by a dieter who
has already done his or her slimming duty by having a teaspoonful of
cottage cheese for breakfast.
--- Douglas Adams, The Meaning of Liff
--
package texlive-base-bin 2007-11 failed to install/upgrade: post-installation
script spawns thousands of processes
https://bugs.launchpad.net/bugs/122863
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
