Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-12-06 Thread Frank Küster
Hi all, what should we do about this bug? Julian Gilbey [EMAIL PROTECTED] wrote: On Thu, Nov 23, 2006 at 02:23:15PM +0100, Marcin Juszkiewicz wrote: echo $HOME /home/hrw/ That's not: $HOME should not have a trailing slash. Should this be documented somewhere more clearly? Or can we

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-12-06 Thread Julian Gilbey
On Wed, Dec 06, 2006 at 09:37:30AM +0100, Frank Küster wrote: Hi all, what should we do about this bug? I don't know. Julian Gilbey [EMAIL PROTECTED] wrote: On Thu, Nov 23, 2006 at 02:23:15PM +0100, Marcin Juszkiewicz wrote: echo $HOME /home/hrw/ That's not: $HOME should

Bug#396835: kernel package bug and kpathsea (was: Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h))

2006-12-06 Thread Frank Küster
Julian Gilbey [EMAIL PROTECTED] wrote: echo $HOME /home/hrw/ That's not: $HOME should not have a trailing slash. Should this be documented somewhere more clearly? Or can we just assume a sane setting, at least for the TeX packages? This we should either do, or suggest that

Bug#396835: kernel package bug and kpathsea (was: Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h))

2006-12-06 Thread Hilmar Preusse
On 06.12.06 Frank Küster ([EMAIL PROTECTED]) wrote: Hi, This symlink is an absolute reference to the source tree on the builder's machine. How could that possibly be useful on anyone else's random machine? If it were a symlink to /usr/src/linux* that would be a different story. Note

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-23 Thread Marcin Juszkiewicz
Dnia środa, 22 listopada 2006 18:43, Frank Küster napisał: Marcin Juszkiewicz [EMAIL PROTECTED] wrote: On this machine kpsewhich was stat-ing all files in filesystem Oh, this should not happen. Maybe some conffile setting is wrong? Can you please send the output of grep '^TEXMF ='

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-23 Thread Julian Gilbey
On Thu, Nov 23, 2006 at 11:30:39AM +0100, Marcin Juszkiewicz wrote: Dnia środa, 22 listopada 2006 18:43, Frank Küster napisał: Marcin Juszkiewicz [EMAIL PROTECTED] wrote: On this machine kpsewhich was stat-ing all files in filesystem Oh, this should not happen. Maybe some conffile

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-23 Thread Ralf Stubner
Marcin Juszkiewicz wrote: [...] kdebug:start search(files=[ls-R ls-r], must_exist=1, find_all=1, path=/home/hrw//texmf:/var/lib/texmf:/usr/local/share/texmf:/usr/share/texmf:/tmp/texfonts:/usr/share/texmf-texlive:/usr/share/texmf-tetex). kdebug:kpse_normalize_path (/home/hrw//texmf) = 1

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-23 Thread Marcin Juszkiewicz
Dnia czwartek, 23 listopada 2006 12:09, Julian Gilbey napisał: On Thu, Nov 23, 2006 at 11:30:39AM +0100, Marcin Juszkiewicz wrote: Dnia środa, 22 listopada 2006 18:43, Frank Küster napisał: kdebug:kpse_normalize_path (/home/hrw//texmf) = 1 It seems that $TEXMFHOME is expanding to

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-23 Thread Julian Gilbey
On Thu, Nov 23, 2006 at 02:23:15PM +0100, Marcin Juszkiewicz wrote: Dnia czwartek, 23 listopada 2006 12:09, Julian Gilbey napisał: On Thu, Nov 23, 2006 at 11:30:39AM +0100, Marcin Juszkiewicz wrote: Dnia środa, 22 listopada 2006 18:43, Frank Küster napisał: kdebug:kpse_normalize_path

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-22 Thread Marcin Juszkiewicz
Dnia wtorek, 14 listopada 2006 19:24, Frank Küster napisał: Hello Marcin, do you just rarely use this machine, or have you forgotten about the problem?  I hope you don't mind that I ping you. I was overloaded recently. Today I looked more into problem and found why it was a problem. On

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-22 Thread Frank Küster
Marcin Juszkiewicz [EMAIL PROTECTED] wrote: Dnia wtorek, 14 listopada 2006 19:24, Frank Küster napisał: Hello Marcin, do you just rarely use this machine, or have you forgotten about the problem?  I hope you don't mind that I ping you. I was overloaded recently. Today I looked more into

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-14 Thread Frank Küster
Hello Marcin, do you just rarely use this machine, or have you forgotten about the problem? I hope you don't mind that I ping you. Frank Küster [EMAIL PROTECTED] wrote: Marcin Juszkiewicz [EMAIL PROTECTED] wrote: PID TTY STAT TIME COMMAND 2077 ?Ss 0:01 kdeinit

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-08 Thread Marcin Juszkiewicz
Dnia piątek, 3 listopada 2006 14:23, Frank Küster napisał: One more question:  Please send us the listing of the directories /etc/texmf/texmf.d/ /etc/texmf/updmap.d/ /etc/texmf/fmtutil.d/ /etc/texmf/language.d/ and if there are any files in there that are not from tex-common (names

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-08 Thread Marcin Juszkiewicz
Dnia piątek, 3 listopada 2006 11:47, Frank Küster napisał: If that happens again, please send the output of ps axf.  One thing is different to the older bug, though:  Back then, it wasn't possible to stop it with Ctrl-C. I rebooted machine since then and did 'apt-get remove tex-common tetex*'

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-08 Thread Frank Küster
Hi Marcin, the BTS server seems to be overloaded again, so this mail only reached me directly, not through the maintainer list - which means that no one else is able to comment on it yet. What a pity. Marcin Juszkiewicz [EMAIL PROTECTED] wrote: Dnia piątek, 3 listopada 2006 11:47, Frank

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-07 Thread Frank Küster
Hi Marcin, are you still there? I'd really like to fix this bug, but we need some of the pieces of information I have already asked from you. If you don't have time currently, but hopefully later, just tell us when we should remind you. Thanks in advance, Frank -- Dr. Frank Küster Single

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-07 Thread Marcin Juszkiewicz
Dnia wtorek, 7 listopada 2006 18:21, Frank Küster napisał: are you still there?  I'd really like to fix this bug, but we need some of the pieces of information I have already asked from you. If you don't have time currently, but hopefully later, just tell us when we should remind you. Sorry

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-06 Thread Florent Rougon
Frank Küster [EMAIL PROTECTED] wrote: But that - does not explain why tetex-bin's postinst was called at all before tetex-base' was ready My hypothesis is that dpkg somehow forgot that tetex-bin.postinst was running (maybe because dpkg was killed). Then, if you install or upgrade

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-06 Thread Frank Küster
Florent Rougon [EMAIL PROTECTED] wrote: Hi, Frank Küster [EMAIL PROTECTED] wrote: tetex-bin's postinst script is already being run. Does anybody know whether it is expected that a maintainer script does not look like being a child of apt-get, as is the case here for tetex-bin?

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-03 Thread Marcin Juszkiewicz
Package: tetex-bin Version: 3.0-23 Severity: important I want to install tetex to generate some documentation. But on this system it is stuck in postinst - looking at top it looks like kpsewhich is a problem - it took over 600M of RAM (1.2G installed) and when I left it for whole night it did not

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-03 Thread Frank Küster
Dzien dobry, thanks for reporting. This might be the same as #315762. Marcin Juszkiewicz [EMAIL PROTECTED] wrote: Package: tetex-bin Version: 3.0-23 Severity: important I want to install tetex to generate some documentation. But on this system it is stuck in postinst - looking at top it

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-03 Thread Marcin Juszkiewicz
Dnia piątek, 3 listopada 2006 11:47, Frank Küster napisał: Dzien dobry, thanks for reporting. This might be the same as #315762. Marcin Juszkiewicz [EMAIL PROTECTED] wrote: Package: tetex-bin Version: 3.0-23 Severity: important I want to install tetex to generate some

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-03 Thread Frank Küster
Marcin Juszkiewicz [EMAIL PROTECTED] wrote: ps afx output taken when it was not stopped (cut to related things): 13780 ?Ss 0:01 kdeinit Running... 13836 ?S 3:46 \_ konsole [kdeinit] 13838 pts/1Ss 0:00 | \_ /bin/bash 30006 pts/11 S 0:00 | | \_

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-03 Thread Frank Küster
Hi Marcin, thinking about it, I have one more question: Marcin Juszkiewicz [EMAIL PROTECTED] wrote: 12:29 [EMAIL PROTECTED]:hrw# time LC_ALL=C apt-get install tetex-extra [...] Setting up tetex-base (3.0.dfsg.3-1) ... done Creating config file /etc/texdoctk/texdocrc with new version [1]+

Bug#396835: tetex-bin postinst take unlimited amount of time and ram (kpsewhich took 600M and 14h)

2006-11-03 Thread Frank Küster
Hi Marcin, I hope I don't upset you by this e-mail bombardment... But currently I have some time to think about it and test, but I won't have much time this weekend. Here's one more suggestion for debugging. Add the following line to your sources.list: deb