Frank Küster <[EMAIL PROTECTED]> wrote: > Norbert Preining <[EMAIL PROTECTED]> wrote: > >> 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? > > I don't really have an explanation.
One morething which is strange is that the original reporter said that there were *two* fork bombs after each other, and that the first was "related" to mktexlsr, but still there were *etex* processes running. This I cannot explain anyhow, I assume that the bug reporter mixed something up, please ask him to clarify that (I'm in a hurry, leaving for holiday, and have no time to look up the launchpad bug and reporter's e-mail address, sorry). > I'm not sure what texlive and tex-common versions feisty had, but > if I assume it resembles sarge (tex-common 1.0*), *then* I do not have > an explanation. We should really try to get exact version numbers (aptitude log?) Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) -- 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
