Your message dated Wed, 09 Nov 2005 11:47:18 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334017: fixed in wmii 2-2
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; 15 Oct 2005 01:51:45 +0000
>From [EMAIL PROTECTED] Fri Oct 14 18:51:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from moutng.kundenserver.de [212.227.126.177] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EQbD7-00044e-00; Fri, 14 Oct 2005 18:51:45 -0700
Received: from [85.197.17.85] (helo=localhost.localdomain)
        by mrelayeu.kundenserver.de with ESMTP (Nemesis),
        id 0MKwh2-1EQbD61C5l-0008UO; Sat, 15 Oct 2005 03:51:44 +0200
Received: from diego by localhost.localdomain with local (Exim 4.54)
        id 1EQbCR-0003my-GP; Sat, 15 Oct 2005 03:51:03 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Diego Biurrun <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: wmii: should use x-terminal-emulator instead of xterm
X-Mailer: reportbug 3.17
Date: Sat, 15 Oct 2005 03:51:03 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Provags-ID: kundenserver.de [EMAIL PROTECTED] 
login:cda85dccaaeec2d03fac572ff7daa982
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-Level: 
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

Package: wmii
Version: 2-1
Severity: important

Hi,

I don't have xterm installed, now if I press Alt-t I don't get a
terminal.  wmii should start x-terminal-emulator instead of xterm so
that this problem does not appear.

Diego


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-powerpc
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages wmii depends on:
ii  libc6                     2.3.5-6        GNU C Library: Shared libraries an
ii  libx11-6                  6.8.2.dfsg.1-8 X Window System protocol client li
ii  xlibs                     6.8.2.dfsg.1-8 X Window System client libraries m

Versions of packages wmii recommends:
ii  python2.3-libixp [python-libi 2-1        Python bindings for libixp

-- no debconf information

---------------------------------------
Received: (at 334017-close) by bugs.debian.org; 9 Nov 2005 19:51:46 +0000
>From [EMAIL PROTECTED] Wed Nov 09 11:51:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EZvug-00076U-00; Wed, 09 Nov 2005 11:47:18 -0800
From: Daniel Baumann <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#334017: fixed in wmii 2-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 09 Nov 2005 11:47:18 -0800
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-Level: 
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

Source: wmii
Source-Version: 2-2

We believe that the bug you reported is fixed in the latest version of
wmii, which is due to be installed in the Debian FTP archive:

python2.3-libixp_2-2_i386.deb
  to pool/main/w/wmii/python2.3-libixp_2-2_i386.deb
wmii_2-2.diff.gz
  to pool/main/w/wmii/wmii_2-2.diff.gz
wmii_2-2.dsc
  to pool/main/w/wmii/wmii_2-2.dsc
wmii_2-2_i386.deb
  to pool/main/w/wmii/wmii_2-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann <[EMAIL PROTECTED]> (supplier of updated wmii package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu,  3 Nov 2005 22:58:00 +0100
Source: wmii
Binary: python2.3-libixp wmii
Architecture: source i386
Version: 2-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann <[EMAIL PROTECTED]>
Changed-By: Daniel Baumann <[EMAIL PROTECTED]>
Description: 
 python2.3-libixp - Python bindings for libixp
 wmii       - lightweight tabbed and tiled X11 window manager
Closes: 334017 335446 338033
Changes: 
 wmii (2-2) unstable; urgency=low
 .
   * Added temporary conflict to wmifs (Closes: #335446, #338033). I will
     rename wmifs in the next revision, this conflict is just a quick fix.
   * Modifing default configuration:
     - using x-terminal-emulator instead of xterm (Closes: #334017).
Files: 
 03495b6e23d447c38aeae818c80a05fc 619 x11 optional wmii_2-2.dsc
 c5a05a08308a904f17145417cf861d78 2933 x11 optional wmii_2-2.diff.gz
 bce0a96f1012cece0a7d2fb81a96292b 319530 x11 optional wmii_2-2_i386.deb
 85645873bfdbf3698b867342d86a590d 27694 python optional 
python2.3-libixp_2-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDclBoxa93SlhRC1oRAhK1AKDRt9rSOqCMSjRBHCb92sqGWtJEqACgoh/0
B+eOu6VfYXZpUJlN+Ub5xgo=
=Aad3
-----END PGP SIGNATURE-----


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

Reply via email to