Your message dated Mon, 21 Mar 2005 23:41:14 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300764: missing depends (at least) on tetex-bin breaks 
install/removal and hoses buildds
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; 21 Mar 2005 17:41:09 +0000
>From [EMAIL PROTECTED] Mon Mar 21 09:41:09 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 83-216-141-215.jamest298.adsl.metronet.co.uk 
(shiri.gloaming.local) [83.216.141.215] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DDQtp-0005NB-00; Mon, 21 Mar 2005 09:41:09 -0800
Received: from james by shiri.gloaming.local with local (Exim 4.34 #1 (Debian))
        id 1DDQtJ-0004TF-RX
        for <[EMAIL PROTECTED]>; Mon, 21 Mar 2005 17:40:37 +0000
To: [EMAIL PROTECTED]
Subject: missing depends (at least) on tetex-bin breaks install/removal and
 hoses buildds
Mail-Copies-To: never
From: James Troup <[EMAIL PROTECTED]>
Date: Mon, 21 Mar 2005 17:40:37 +0000
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: musixlyr, pmx, musixtex
Version: 2.1c-1, 2.5.4-1, 0.112.1-3
Severity: grave

The postrm failure is particularly bad because it wedged the buildd
chroots in a broken state causing all subsequent builds to fail.
Please fix ASAP.

| Setting up musixlyr (2.1c-1) ...
| /var/lib/dpkg/info/musixlyr.postinst: line 13: /usr/bin/kpsewhich: No such 
file or directory
| dpkg: error processing musixlyr (--configure):
|  subprocess post-installation script returned error exit status 1
| Setting up musixtex (0.112.1-3) ...
| /var/lib/dpkg/info/musixtex.postinst: line 24: /usr/bin/kpsewhich: No such 
file or directory
| dpkg: error processing musixtex (--configure):
|  subprocess post-installation script returned error exit status 1
| Setting up p2c (1.21alpha2-2) ...
| Setting up pmx (2.5.4-1) ...
| /var/lib/dpkg/info/pmx.postinst: line 13: /usr/bin/kpsewhich: No such file or 
directory
| dpkg: error processing pmx (--configure):
|  subprocess post-installation script returned error exit status 1
| Errors were encountered while processing:
|  musixlyr
|  musixtex
|  pmx
| E: Sub-process /usr/bin/dpkg returned an error code (1)
| apt-get failed.
| Package installation failed
| Trying to reinstall removed packages:
| Trying to uninstall newly installed packages:
|   /usr/bin/sudo dpkg --root=/home/buildd/build/chroot-unstable --remove 
debconf-utils debhelper gettext gettext-base html2text intltool-debian libg2c0 
musixlyr musixtex p2c pmx po-debconf
| (Reading database ... 15628 files and directories currently installed.)
| Removing debhelper ...
| Removing html2text ...
| Removing libg2c0 ...
| Removing musixlyr ...
| Removing musixtex ...
| /var/lib/dpkg/info/musixtex.postrm: line 16: /usr/bin/kpsewhich: No such file 
or directory
| dpkg: error processing musixtex (--remove):
|  subprocess post-removal script returned error exit status 1
| /var/lib/dpkg/info/musixtex.postinst: line 24: /usr/bin/kpsewhich: No such 
file or directory
| dpkg: error while cleaning up:
|  subprocess post-installation script returned error exit status 1
| Removing p2c ...
| Removing pmx ...
| Removing po-debconf ...
| Removing debconf-utils ...
| Removing intltool-debian ...
| Removing gettext ...
| Removing gettext-base ...
| Errors were encountered while processing:
|  musixtex
| dpkg run to remove packages (debconf-utils debhelper gettext gettext-base 
html2text intltool-debian libg2c0 musixlyr musixtex p2c pmx po-debconf) failed!

A complete build log can be found at
http://buildd.debian.org/build.php?arch=arm&pkg=m-tx&ver=0.55c-1

-- 
James

---------------------------------------
Received: (at 300764-done) by bugs.debian.org; 21 Mar 2005 23:41:46 +0000
>From [EMAIL PROTECTED] Mon Mar 21 15:41:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 83-216-141-215.jamest298.adsl.metronet.co.uk 
(shiri.gloaming.local) [83.216.141.215] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DDWWn-00064a-00; Mon, 21 Mar 2005 15:41:45 -0800
Received: from james by shiri.gloaming.local with local (Exim 4.34 #1 (Debian))
        id 1DDWWI-0006v2-3W
        for <[EMAIL PROTECTED]>; Mon, 21 Mar 2005 23:41:14 +0000
To: [EMAIL PROTECTED]
Subject: Re: Bug#300764: missing depends (at least) on tetex-bin breaks
 install/removal and hoses buildds
Mail-Copies-To: never
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
From: James Troup <[EMAIL PROTECTED]>
Date: Mon, 21 Mar 2005 23:41:14 +0000
In-Reply-To: <[EMAIL PROTECTED]> (Roland Stigge's message of
 "Mon, 21 Mar 2005 21:12:42 +0100")
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Roland Stigge <[EMAIL PROTECTED]> writes:

> pmx already Depends on tetex-bin, so I don't know why this:

Hmm.  I really didn't think I'd checked this, but apparently not.
Sorry for wasting your time.  

-- 
James


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to