Your message dated Sun, 15 Feb 2009 16:32:14 +0000
with message-id <e1lyjug-0004fx...@ries.debian.org>
and subject line Bug#515278: fixed in posh 0.6.16
has caused the Debian Bug report #515278,
regarding posh segfaults in xtrace mode
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
515278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: posh
Version: 0.6.15
Severity: normal

When putting posh into xtrace mode, the next entered command causes to
crash posh with a segfault.

zsh% posh
$ set -x
$ echo foo
[1]    32044 segmentation fault (core dumped)  posh

Reproducible in scripts and in interactive mode.

Regards, Frank


-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.27.8-loopaes (PREEMPT)
Locale: LANG=C, lc_ctype=de...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages posh depends on:
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy
ii  libc6                         2.7-18     GNU C Library: Shared libraries

posh recommends no packages.

posh suggests no packages.

-- debconf information excluded



--- End Message ---
--- Begin Message ---
Source: posh
Source-Version: 0.6.16

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

posh_0.6.16.dsc
  to pool/main/p/posh/posh_0.6.16.dsc
posh_0.6.16.tar.gz
  to pool/main/p/posh/posh_0.6.16.tar.gz
posh_0.6.16_i386.deb
  to pool/main/p/posh/posh_0.6.16_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 515...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Clint Adams <sch...@debian.org> (supplier of updated posh 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 ftpmas...@debian.org)


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

Format: 1.8
Date: Sun, 15 Feb 2009 11:15:30 -0500
Source: posh
Binary: posh
Architecture: source i386
Version: 0.6.16
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams <sch...@debian.org>
Changed-By: Clint Adams <sch...@debian.org>
Description: 
 posh       - Policy-compliant Ordinary SHell
Closes: 515278
Changes: 
 posh (0.6.16) unstable; urgency=medium
 .
   * Fix segfault in XTRACE.  closes: #515278.
Checksums-Sha1: 
 9eb1effc2fb9cc834928ae00df14346e4371c95e 830 posh_0.6.16.dsc
 9d92e2db400fbd64354af44974ae9e441bd81a41 416481 posh_0.6.16.tar.gz
 436d6603bde578b46793ef5e0b1ba4839ad9f42b 83990 posh_0.6.16_i386.deb
Checksums-Sha256: 
 d1a5ad29abc8e7fbfed28ddce90487ca75bf5000279b05aae126394f9dc20783 830 
posh_0.6.16.dsc
 35b805bde7fdcb648336db63857bea050f6dd83fd30c1ea633176afa11f23fe1 416481 
posh_0.6.16.tar.gz
 d5418de63ce44a598d30122cafed9e64fec301dbf4fb60e67f6d7688299ef471 83990 
posh_0.6.16_i386.deb
Files: 
 977d04865739870b61ba22ee5eb2d76e 830 shells optional posh_0.6.16.dsc
 c41d9d0b86ef7dae4611119945eee618 416481 shells optional posh_0.6.16.tar.gz
 583efb73cbba3808413357e0887ffecc 83990 shells optional posh_0.6.16_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Debian!

iD8DBQFJmEDz5m0u66uWM3ARAvwcAJ9WKwoLY9fVEOX97YydIyEubOKrWwCggXEy
OBnJrCyYgYksEN8qSxKpG4s=
=bx5C
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to