[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#176036: marked as done (tetex-base: freeze in postinst )



Your message dated Fri, 10 Jan 2003 08:16:05 +0900 (JST)
with message-id <20030110.081605.74744510.kohda@pm.tokushima-u.ac.jp>
and subject line Bug#176029: /usr/bin/updmap script hangs during upgrade
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Jan 2003 19:31:26 +0000
>From at@gclab.org Thu Jan 09 13:31:25 2003
Return-path: <at@gclab.org>
Received: from 37.1.111.219.st.excite.co.jp (mail.gclab.org) [219.111.1.37] (postfix)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18WiOi-0004T3-00; Thu, 09 Jan 2003 13:31:24 -0600
Received: from localhost (chulip [127.0.0.1])
	by mail.gclab.org (Postfix) with ESMTP id 4B074112629
	for <submit@bugs.debian.org>; Fri, 10 Jan 2003 04:31:30 +0900 (JST)
Date: Fri, 10 Jan 2003 04:31:40 +0900 (JST)
Message-Id: <[🔎] 20030110.043140.304113613.at@gclab.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: tetex-base: freeze in postinst 
From: Akira TAGOH <at@gclab.org>
X-PGP-key-URL: http://keyring.debian.org:11371/pks/lookup?op=get&search=0x9DB19904
X-fingerprint: 06B7 CF30 4EF6 224A E660  7A2A D900 A735 9DB1 9904
X-URL: http://www.gclab.org/~at/
X-Attribution: AT
X-Mailer: Mew version 3.1 on XEmacs 21.5-b5 (beets)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=0.6 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.41
X-Spam-Level: 

Package: tetex-base
Version: 1.0.2+20021025-5
Severity: grave


If it's freshly installed in chroot for example, updmap is
freezed in postinst. -4 worked fine.

updmap calls kpsewhich internally, and tetex-bin has it. but
tetex-bin isn't configured yet so that tetex-bin depends on
tetex-base. some files are still named as .dpkg-new.
perhaps tetex-base.postinst shouldn't calls updmap? or
tetex-base needs a dependency of tetex-bin?

--
Akira TAGOH  : tagoh@gnome.gr.jp  / Japan GNOME Users Group
at@gclab.org : tagoh@gnome-db.org / GNOME-DB Project
             : tagoh@redhat.com   / Red Hat, Inc.
             : tagoh@debian.org   / Debian Project

---------------------------------------
Received: (at 176036-done) by bugs.debian.org; 9 Jan 2003 23:16:26 +0000
>From kohda@pm.tokushima-u.ac.jp Thu Jan 09 17:16:26 2003
Return-path: <kohda@pm.tokushima-u.ac.jp>
Received: from nsx.pm.tokushima-u.ac.jp [150.59.48.142] (mail)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18WluU-0007cb-00; Thu, 09 Jan 2003 17:16:26 -0600
Received: from localhost ([127.0.0.1] ident=kohda)
	by nsx.pm.tokushima-u.ac.jp with esmtp (Exim 3.36 #1 (Debian))
	id 18WluN-0003JB-00; Fri, 10 Jan 2003 08:16:19 +0900
Date: Fri, 10 Jan 2003 08:16:05 +0900 (JST)
Message-Id: <20030110.081605.74744510.kohda@pm.tokushima-u.ac.jp>
To: mast@lysator.liu.se, 176029-done@bugs.debian.org
Cc: at@gclab.org, 176036-done@bugs.debian.org
Subject: Re: Bug#176029: /usr/bin/updmap script hangs during upgrade
From: Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp>
In-Reply-To: <[🔎] 5bof6qgotp.fsf@lister.roxen.com>
References: <[🔎] 5bof6qgotp.fsf@lister.roxen.com>
X-Mailer: Mew version 3.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: 176036-done@bugs.debian.org
X-Spam-Status: No, hits=-7.3 required=5.0
	tests=IN_REP_TO,REFERENCES,SIGNATURE_SHORT_DENSE,
	      SPAM_PHRASE_00_01
	version=2.41
X-Spam-Level: 

I believe it was fixed (temporary?) in 1.0.2+20021025-6

But the reports were very helpful and I could fix
the problem in a more reasonable way in the next
1.0.2+20021025-7, I hope.

Thanks,			2003-1-10(Fri)

-- 
 Debian Developer & Debian JP Developer - much more I18N of Debian
 Atsuhito Kohda <kohda@debian.org>
 Department of Math., Tokushima Univ.



Reply to: