Debian Bug report logs - #560665
zshdb: FTBFS: tests failed

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: submit@bugs.debian.org

Subject: zshdb: FTBFS: tests failed

Date: Fri, 11 Dec 2009 13:33:52 +0100

Source: zshdb
Version: 0.03+git20090920-1
Severity: serious
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20091210 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[4]: Entering directory `/build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration'
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/brkpt1.check	2009-12-10 21:50:24.657436656 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/brkpt1.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,8 +1,5 @@
>  (dbg-test1.sh:4):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# 
>  +# Test of breakpoint handling
>  +# 
> FAIL: test-brkpt1
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/bug-args.check	2009-12-10 21:50:24.813686199 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/bug-args.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,5 +1,5 @@
>  (bug-args.sh:2):
> -echo First parm i ...
> +echo First parm is: $1
>  +# Debugger test to see that parameter handling of $1, $2, etc is correct.
>  +print $#
>  0
> @@ -8,7 +8,7 @@
>  +step 2
>  First parm is:
>  (bug-args.sh:4):
> -sh ...
> +shift 2
>  +# There should now be 5 args set and $5 should have a value
>  +print $#
>  5
> @@ -18,7 +18,7 @@
>  e
>  +step 
>  (bug-args.sh:6):
> -e ...
> +exit 0
>  +# There should now be 3 args set and $5 should not have a value
>  +print $#
>  3
> FAIL: test-bug-args
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/bugIFS.check	2009-12-10 21:50:24.901935460 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/bugIFS.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,10 +1,10 @@
>  (bugIFS.sh:2):
> -IFS ...
> +IFS="."
>  +# Debugger test of an old IFS bug
>  +# 
>  +step 
>  (bugIFS.sh:3):
> -PS4=' ...
> +PS4='foo'
>  +## Make sure PS4 in an eval is the same as what we just set.
>  +print "+$IFS+"
>  +.+
> FAIL: test-bugIFS
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/bug-errexit.check	2009-12-10 21:50:25.009936768 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/bug-errexit.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,13 +1,13 @@
>  (bug-errexit.sh:4):
> -set -o er ...
> +set -o errexit
>  +# We once had a bug when some options were set (errexit and -u)
>  +# Make sure this doesn't happen again.
>  +step- 
>  (bug-errexit.sh:5):
> -s ...
> +set -u
>  +step- 
>  (bug-errexit.sh:6):
> -prin ...
> +print one
>  +where 1
>  ->0 in file `bug-errexit.sh' at line 6
>  +quit 
> FAIL: test-bug-errexit
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/bug-ksharrays.check	2009-12-10 21:50:25.118185801 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/bug-ksharrays.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,16 +1,16 @@
>  (bug-ksharrays.sh:3):
> -unsetopt ksha ...
> +unsetopt ksharrays
>  +# Get past initial unsetopt
>  +next 
>  (bug-ksharrays.sh:4):
> -setopt ksharrays sh_word_ ...
> +setopt ksharrays sh_word_split
>  +# Show we don't have ksharrays set
>  +eval setopt
>  norcs
>  +# Now move past set ksharrays
>  +next 
>  (bug-ksharrays.sh:5):
> - ...
> +x=1
>  +# See that we have this set inside eval
>  +eval setopt
>  ksharrays
> FAIL: test-bug-ksharrays
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/condition.check	2009-12-10 21:50:25.222186094 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/condition.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,8 +1,5 @@
>  (dbg-test1.sh:4):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# 
>  +# Test of condition handling (on breakpoints)
>  +############################################################### 
> FAIL: test-condition
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/delete.check	2009-12-10 21:50:25.582186172 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/delete.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,6 +1,5 @@
>  (stepping.sh:3):
> -for ((i=0; i<3; i++)) do
> -	print 1st loop $i ...
> +for ((i=0; i<3; i++)) do print 1st loop $i done
>  +# Make sure autostep is off for next text
>  +set force on
>  +############################### 
> @@ -35,8 +34,7 @@
>  2nd loop 2
>  Breakpoint 2 hit.
>  (stepping.sh:5):
> -for ((i=0; i<3; i++)) do
> -	print 3rd loop $i ...
> +for ((i=0; i<3; i++)) do print 3rd loop $i done
>  +# Should stop at line 5 not 4
>  +where 1
>  ->0 in file `stepping.sh' at line 5
> @@ -67,8 +65,7 @@
>  4th loop 2
>  Breakpoint 4 hit.
>  (stepping.sh:7):
> -for ((i=0; i<3; i++)) do
> -	print 5th loop $i ...
> +for ((i=0; i<3; i++)) do print 5th loop $i done
>  +# Should be at breakpoint but not one that's been deleted
>  +where 1
>  ->0 in file `stepping.sh' at line 7
> FAIL: test-delete
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/enable.check	2009-12-10 21:50:25.826190893 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/enable.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,7 +1,5 @@
>  (nexting.sh:3):
> -p () {
> -	print ${funcfiletrace[0]##*/}
> -	print '= ...
> +p () { print ${funcfiletrace[0]##*/} print '===' }
>  +############################### 
>  +break 5
>  Breakpoint 1 set in file nexting.sh, line 5.
> @@ -22,7 +20,7 @@
>  +continue 
>  Breakpoint 2 hit.
>  (nexting.sh:3):
> -print ${funcfiletrace[0] ...
> +print ${funcfiletrace[0]##*/}
>  +info break
>  Num Type       Disp Enb What
>  1   breakpoint keep n   nexting.sh:5
> @@ -44,7 +42,7 @@
>  ===
>  Breakpoint 3 hit.
>  (nexting.sh:6):
> - ...
> +p
>  +# Should get back to 6
>  +info break
>  Num Type       Disp Enb What
> @@ -61,7 +59,7 @@
>  ===
>  Breakpoint 3 hit.
>  (nexting.sh:6):
> - ...
> +x=6
>  +info break
>  Num Type       Disp Enb What
>  1   breakpoint keep y   nexting.sh:5
> FAIL: test-enable
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/examine.check	2009-12-10 21:50:26.030435646 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/examine.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,5 +1,5 @@
>  (exam.sh:3):
> -unsetopt ksha ...
> +unsetopt ksharrays
>  +# Examine with blanks
>  +examine 
>  
> @@ -19,7 +19,7 @@
>  One-time breakpoint 1 set in file exam.sh, line 10.
>  Breakpoint 1 hit.
>  (exam.sh:10):
> -unset s ...
> +unset string
>  +examine ary
>  typeset -ar ary
>  ary=(10 100 100)
> FAIL: test-examine
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/frame.check	2009-12-10 21:50:26.406435055 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/frame.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,9 +1,5 @@
>  (hanoi.sh:6):
> -init () {
> -	if (( $tracing ))
> -	then
> -		_Dbg_linetrace=1 
> - ...
> +init () { if (( $tracing )) then _Dbg_linetrace=1 fi }
>  +# Test of frame commands
>  +# We also try all of the various where/backtrace variants
>  +# Do we give a valid stack listing initially?
> @@ -19,9 +15,7 @@
>  +# Let's start with a couple of stack entries
>  +step 7
>  (hanoi.sh:8):
> -if (( $tracing ))
> -then
> -	_Dbg_linetrace= ...
> +if (( $tracing )) then _Dbg_linetrace=1 fi
>  +where 2
>  ->0 in file `hanoi.sh' at line 8
>  ##1 init called from file `hanoi.sh' at line 41
> @@ -57,7 +51,7 @@
>  +## continue hanoi
>  +step 12
>  (hanoi.sh:16):
> -typeset -r ...
> +typeset -r a=$2
>  +where 3
>  ->0 in file `hanoi.sh' at line 16
>  ##1 hanoi called from file `hanoi.sh' at line 21
> FAIL: test-frame
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/list.check	2009-12-10 21:50:26.612940550 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/list.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,8 +1,5 @@
>  (dbg-test1.sh:4):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# Test of debugger 'list' command
>  +# 
>  +help l
> FAIL: test-list
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/next.check	2009-12-10 21:50:27.186436661 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/next.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,7 +1,5 @@
>  (nexting.sh:3):
> -p () {
> -	print ${funcfiletrace[0]##*/}
> -	print '= ...
> +p () { print ${funcfiletrace[0]##*/} print '===' }
>  +set basename on
>  +# Make sure autostep is off for next text
>  +set force off
> @@ -9,12 +7,12 @@
>  Show stepping forces a new line is off.
>  +next 
>  (nexting.sh:4):
> -setopt ksha ...
> +setopt ksharrays
>  +where 1
>  ->0 in file `nexting.sh' at line 4
>  +next 
>  (nexting.sh:5):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 5
>  +# Test that next+ skips multiple statements
> @@ -22,7 +20,7 @@
>  nexting.sh:5
>  ===
>  (nexting.sh:6):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 6
>  +# Same thing - but should stop at 2nd statement in line
> @@ -30,12 +28,12 @@
>  nexting.sh:6
>  ===
>  (nexting.sh:6):
> - ...
> +x=6
>  +where 1
>  ->0 in file `nexting.sh' at line 6
>  +next 
>  (nexting.sh:7):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 7
>  +# Now check with set force on
> @@ -46,7 +44,7 @@
>  nexting.sh:7
>  ===
>  (nexting.sh:8):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 8
>  +# Override force
> @@ -54,12 +52,12 @@
>  nexting.sh:8
>  ===
>  (nexting.sh:8):
> - ...
> +x=8
>  +where 1
>  ->0 in file `nexting.sh' at line 8
>  +next- 
>  (nexting.sh:9):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 9
>  +# A null command should use the last next
> @@ -67,17 +65,17 @@
>  nexting.sh:9
>  ===
>  (nexting.sh:9):
> - ...
> +x=9
>  +where 1
>  ->0 in file `nexting.sh' at line 9
>  +next- 
>  (nexting.sh:10):
> - ...
> +p
>  +next 
>  nexting.sh:10
>  ===
>  (nexting.sh:11):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 11
>  +# Try a null command the other way
> @@ -85,14 +83,14 @@
>  nexting.sh:11
>  ===
>  (nexting.sh:12):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 12
>  +next+ 
>  nexting.sh:12
>  ===
>  (nexting.sh:13):
> - ...
> +p
>  +where 1
>  ->0 in file `nexting.sh' at line 13
>  +quit 
> FAIL: test-next
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/sopts.check	2009-12-10 21:50:27.266685708 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/sopts.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,8 +1,4 @@
> -/build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
>  (dbg-test1.sh:4):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# Just a simple quit command.
>  +quit 
> --- /tmp/sopts-filtered.check	2009-12-10 21:50:27.429186221 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/lopts.right	2009-09-21 03:06:50.000000000 +0200
> @@ -19,19 +19,11 @@
>      -V | --version          Print the debugger version number.
>      -x | --eval-command CMDFILE
>                              Execute debugger commands from CMDFILE.
> -/build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
>  (dbg-test1.sh:4):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# Just a simple quit command.
>  +quit 
> -/build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
>  (dbg-test1.sh:4):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# Just a simple quit command.
>  +quit 
> FAIL: test-opts
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /tmp/restart-filtered.check	2009-12-10 21:50:27.565186309 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/restart.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,5 +1,5 @@
>  (restart.sh:4):
> - ...
> +x=1
>  +# Test Restart command
>  +list 
>    4: => x=1
> @@ -8,10 +8,10 @@
>    7:    z=0
>  +step 
>  (restart.sh:5):
> - ...
> +cd /
>  +step 
>  (restart.sh:6):
> - ...
> +y=2
>  +break 7
>  Breakpoint 1 set in file restart.sh, line 7.
>  +run -B -q -L ... restart.sh
> FAIL: test-restart
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /tmp/setshow-filtered.check	2009-12-10 21:50:27.673186693 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/setshow.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,8 +1,5 @@
>  (dbg-test2.sh:6):
> -fn1 () {
> -	echo "fn1 here"
> -	x=5 
> -	 ...
> +fn1 () { echo "fn1 here" x=5 fn3 }
>  +# Test of miscellaneous commands:
>  +# 'source', 'info args', 'show args', 'show warranty', 'show copying', etc.
>  +#### *** GNU things...
> FAIL: test-setshow
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/skip.check	2009-12-10 21:50:27.801186768 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/skip.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,19 +1,16 @@
>  (stepping.sh:3):
> -for ((i=0; i<3; i++)) do
> -	print 1st loop $i ...
> +for ((i=0; i<3; i++)) do print 1st loop $i done
>  +# Make sure autostep is off for next text
>  +set force on
>  +# Test that skip skips multiple statements
>  +skip 
>  (stepping.sh:4):
> -for ((i=0; i<3; i++)) do
> -	print 2nd loop $i ...
> +for ((i=0; i<3; i++)) do print 2nd loop $i done
>  +where 1
>  ->0 in file `stepping.sh' at line 4
>  +skip 2
>  (stepping.sh:6):
> -for ((i=0; i<3; i++)) do
> -	print 4th loop $i ...
> +for ((i=0; i<3; i++)) do print 4th loop $i done
>  +where 1
>  ->0 in file `stepping.sh' at line 6
>  +quit 
> FAIL: test-skip
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/step.check	2009-12-10 21:50:28.209186400 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/step.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,6 +1,5 @@
>  (stepping.sh:3):
> -for ((i=0; i<3; i++)) do
> -	print 1st loop $i ...
> +for ((i=0; i<3; i++)) do print 1st loop $i done
>  +# Make sure autostep is off for next text
>  +set force off
>  +show force
> @@ -11,8 +10,7 @@
>  1st loop 1
>  1st loop 2
>  (stepping.sh:4):
> -for ((i=0; i<3; i++)) do
> -	print 2nd loop $i ...
> +for ((i=0; i<3; i++)) do print 2nd loop $i done
>  +set force on
>  +show force
>  Show stepping forces a new line is on.
> @@ -22,39 +20,35 @@
>  2nd loop 1
>  2nd loop 2
>  (stepping.sh:5):
> -for ((i=0; i<3; i++)) do
> -	print 3rd loop $i ...
> +for ((i=0; i<3; i++)) do print 3rd loop $i done
>  +# Override force
>  +step- 
>  (stepping.sh:5):
> -print 3rd lo ...
> +print 3rd loop $i
>  +step- 
>  3rd loop 0
>  (stepping.sh:5):
> -print 3rd lo ...
> +print 3rd loop $i
>  +# A null command should use the last step
>  +step- 
>  3rd loop 1
>  (stepping.sh:5):
> -print 3rd lo ...
> +print 3rd loop $i
>  +step 
>  3rd loop 2
>  (stepping.sh:6):
> -for ((i=0; i<3; i++)) do
> -	print 4th loop $i ...
> +for ((i=0; i<3; i++)) do print 4th loop $i done
>  +# Try a null command the other way
>  +step+ 
>  4th loop 0
>  4th loop 1
>  4th loop 2
>  (stepping.sh:7):
> -for ((i=0; i<3; i++)) do
> -	print 5th loop $i ...
> +for ((i=0; i<3; i++)) do print 5th loop $i done
>  +step+ 
>  5th loop 0
>  5th loop 1
>  5th loop 2
>  (stepping.sh:8):
> -for ((i=0; i<3; i++)) do
> -	print 6th loop $i ...
> +for ((i=0; i<3; i++)) do print 6th loop $i done
>  +quit 
> FAIL: test-step
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/subshell.check	2009-12-10 21:50:28.425186709 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/subshell.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,25 +1,23 @@
>  (subshell.sh:2):
> - ...
> +x=2
>  +# Test of debugging through a subshell
>  +examine x
>  x
>  +step 
>  (subshell.sh:3):
> -(
> -	x='line 3' 
> -	y='line  ...
> +( x='line 3' y='line 4' )
>  +examine x
>  typeset x=2
>  +step 
>  (subshell.sh:3):
> -x='lin ...
> +x='line 3'
>  +print $ZSH_SUBSHELL
>  1
>  +examine x
>  typeset x=2
>  +step 
>  (subshell.sh:4):
> -y='lin ...
> +y='line 4'
>  +# Set inside a subshell
>  +set autoeval on
>  +examine x
> @@ -39,9 +37,7 @@
>     12  examine x
>  +step 
>  (subshell.sh:6):
> -(
> -	x=$(print line 7) 
> -	y='line  ...
> +( x=$(print line 7) y='line 8' )
>  +examine x
>  typeset x=2
>  +print $ZSH_SUBSHELL
> @@ -69,7 +65,7 @@
>     18  show autoeval
>  +step 3
>  (subshell.sh:8):
> -y='lin ...
> +y='line 8'
>  +examine x
>  typeset x='line 7'
>  +print $ZSH_SUBSHELL
> FAIL: test-subshell
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> --- /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/integration/tbreak.check	2009-12-10 21:50:28.609186043 +0100
> +++ /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/test/data/tbreak.right	2009-09-21 03:06:50.000000000 +0200
> @@ -1,11 +1,9 @@
>  (nexting.sh:3):
> -p () {
> -	print ${funcfiletrace[0]##*/}
> -	print '= ...
> +p () { print ${funcfiletrace[0]##*/} print '===' }
>  +# Get past line 3
>  +step 
>  (nexting.sh:4):
> -setopt ksha ...
> +setopt ksharrays
>  +# Temporary breakpoint inside function
>  +tbreak 3
>  One-time breakpoint 1 set in file nexting.sh, line 3.
> @@ -17,7 +15,7 @@
>  One-time breakpoint 2 set in file nexting.sh, line 6.
>  Breakpoint 1 hit.
>  (nexting.sh:3):
> -print ${funcfiletrace[0] ...
> +print ${funcfiletrace[0]##*/}
>  +# Breakpoint at line 6 should still be shown
>  +info break
>  Num Type       Disp Enb What
> @@ -27,7 +25,7 @@
>  ===
>  Breakpoint 2 hit.
>  (nexting.sh:6):
> - ...
> +p
>  +# Now we get to line 6 and
>  +# no more breakpoints should be shown.
>  +info break
> FAIL: test-tbreak
> ==============================
> 19 of 19 tests failed
> Please report to rocky@gnu.org
> ==============================
> make[4]: *** [check-TESTS] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/12/10/zshdb_0.03+git20090920-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #10 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Clint Adams <schizo@debian.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 560665@bugs.debian.org

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 11 Dec 2009 18:20:48 +0000

On Fri, Dec 11, 2009 at 01:33:52PM +0100, Lucas Nussbaum wrote:
> > /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 

What? Where did it go?

Message #15 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Ilya Barygin <barygin@gmail.com>

To: 560665@bugs.debian.org

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Sat, 30 Jan 2010 00:56:11 +0300

We have this problem in Ubuntu (where arch:all packages are built on
buildds), and some testing shows that the failure can be reproduced in
sbuild, but not in pbuilder.

Message #20 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Clint Adams <schizo@debian.org>

To: Ilya Barygin <barygin@gmail.com>, 560665@bugs.debian.org

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Sat, 30 Jan 2010 04:36:34 +0000

On Sat, Jan 30, 2010 at 12:56:11AM +0300, Ilya Barygin wrote:
> We have this problem in Ubuntu (where arch:all packages are built on
> buildds), and some testing shows that the failure can be reproduced in
> sbuild, but not in pbuilder.

Any idea why?

Message #25 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Ilya Barygin <barygin@gmail.com>

To: Clint Adams <schizo@debian.org>

Cc: 560665@bugs.debian.org

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Sat, 30 Jan 2010 13:01:48 +0300

> Any idea why?

Unfortunately, no. We're tracking this at
https://launchpad.net/bugs/514359 (not much info there at the moment).

Message #30 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Loïc Minier <lool@dooz.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 560665@bugs.debian.org

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 12 Feb 2010 12:16:16 +0100

        Hi

On Fri, Dec 11, 2009, Lucas Nussbaum wrote:
> Relevant part:

 Actually that's not the whole relevant part; there's also:
checking whether make sets $(MAKE)... yes
get_processor:3: command not found: ps
./ok4zshdb.sh:43: command not found: -if
checking Checking whether /bin/zsh is compatible with zshdb... Your zsh doesn't have the fc -l patches.
yes!
checking for diff... /usr/bin/diff
adding -w to diff in regression tests

 This particular problem is due to a missing build-dep on procps which
 provides ps, used in test/zsh/ok4zshdb.sh:get_processor().
 (debootstrap --variant=buildd wont pull procps)

> > /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 

 That's the meat of the problem: lib/processor.sh:37 breaks the build
 because it uses $TTY:
# For zsh, using this builtin parameter $TTY seems preferred over &0
# because it will find/fake a terminal when &0 might not be one.
exec {_Dbg_fdi}<$TTY

TTY isn't set

 I managed to reproduce the problem in my build environment with:
    sudo mv /dev/tty /dev/tty.bak
    env -i dpkg-buildpackage -b </dev/null >log 2>&1
 (obviously this might break your system)

 So I believe the buildd environment has a partial /dev without
 /dev/tty.

 I tried replacing $TTY with &0, and a real file, but that didn't work
 (hit the same test failures), and with a fifo, but that hanged the
 build waiting for the fifo to fill in.

 I'm not familiar with zshdb, but I suspect it might need a TTY during
 debug sessions which might be why the testsuite would use one as well.
 Someone more familiar with zshdb could perhaps check whether we can use
 coproc here, or a pair of fifos (adding code to properly close them as
 well), to replace the use of $TTY.  Perhaps another way would be to
 pass a script (list of commands to run) to zshdb.

 As a last resort, I tried running make check under "expect", but oddly
 that failed in the same way.  While expect correctly sets up stdin,
 stdout, stderr on a pty,
 test/integration/check-common.sh:run_test_check() ruins that effort by
 using redirections:
        (cd $srcdir && run_debugger $debugged_script 2>&1 >$TEST_FILE </dev/null)
 so zsh sees that stdin, stdout, and stderr aren't ttys and falls back
 to /dev/tty (which doesn't exist apparently).

 So I tried working around that with:
    expect -c 'spawn zsh -c "ZSH_TTY=\$$TTY $(MAKE) check"; expect'
 and changing lib/processor.sh to use ZSH_TTY.  I don't know why *that*
 still fails.

 So it seems the only way is to rework the testsuite to not rely on
 using a real tty...

     Bye
-- 
Loïc Minier

Message #35 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Clint Adams <schizo@debian.org>

To: Rocky Bernstein <rocky.bernstein@gmail.com>

Cc: Loïc Minier <lool@dooz.org>, 560665@bugs.debian.org, Lucas Nussbaum <lucas@lucas-nussbaum.net>

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 12 Feb 2010 20:32:36 +0000

On Fri, Feb 12, 2010 at 12:16:16PM +0100, Loïc Minier wrote:
> On Fri, Dec 11, 2009, Lucas Nussbaum wrote:
> > Relevant part:
> 
>  Actually that's not the whole relevant part; there's also:
> checking whether make sets $(MAKE)... yes
> get_processor:3: command not found: ps
> ./ok4zshdb.sh:43: command not found: -if
> checking Checking whether /bin/zsh is compatible with zshdb... Your zsh doesn't have the fc -l patches.
> yes!
> checking for diff... /usr/bin/diff
> adding -w to diff in regression tests
> 
>  This particular problem is due to a missing build-dep on procps which
>  provides ps, used in test/zsh/ok4zshdb.sh:get_processor().
>  (debootstrap --variant=buildd wont pull procps)
> 
> > > /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37: no such file or directory: 
> 
>  That's the meat of the problem: lib/processor.sh:37 breaks the build
>  because it uses $TTY:
> # For zsh, using this builtin parameter $TTY seems preferred over &0
> # because it will find/fake a terminal when &0 might not be one.
> exec {_Dbg_fdi}<$TTY
> 
> TTY isn't set
> 
>  I managed to reproduce the problem in my build environment with:
>     sudo mv /dev/tty /dev/tty.bak
>     env -i dpkg-buildpackage -b </dev/null >log 2>&1
>  (obviously this might break your system)
> 
>  So I believe the buildd environment has a partial /dev without
>  /dev/tty.
> 
>  I tried replacing $TTY with &0, and a real file, but that didn't work
>  (hit the same test failures), and with a fifo, but that hanged the
>  build waiting for the fifo to fill in.
> 
>  I'm not familiar with zshdb, but I suspect it might need a TTY during
>  debug sessions which might be why the testsuite would use one as well.
>  Someone more familiar with zshdb could perhaps check whether we can use
>  coproc here, or a pair of fifos (adding code to properly close them as
>  well), to replace the use of $TTY.  Perhaps another way would be to
>  pass a script (list of commands to run) to zshdb.
> 
>  As a last resort, I tried running make check under "expect", but oddly
>  that failed in the same way.  While expect correctly sets up stdin,
>  stdout, stderr on a pty,
>  test/integration/check-common.sh:run_test_check() ruins that effort by
>  using redirections:
>         (cd $srcdir && run_debugger $debugged_script 2>&1 >$TEST_FILE </dev/null)
>  so zsh sees that stdin, stdout, and stderr aren't ttys and falls back
>  to /dev/tty (which doesn't exist apparently).
> 
>  So I tried working around that with:
>     expect -c 'spawn zsh -c "ZSH_TTY=\$$TTY $(MAKE) check"; expect'
>  and changing lib/processor.sh to use ZSH_TTY.  I don't know why *that*
>  still fails.
> 
>  So it seems the only way is to rework the testsuite to not rely on
>  using a real tty...

Rocky, any thoughts?  I guess at the worst case we could simply disable
the tests if no tty is available.

Message #40 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Rocky Bernstein <rocky.bernstein@gmail.com>

To: Clint Adams <schizo@debian.org>

Cc: Loïc Minier <lool@dooz.org>, 560665@bugs.debian.org, Lucas Nussbaum <lucas@lucas-nussbaum.net>

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 12 Feb 2010 15:50:07 -0500

[Message part 1 (text/plain, inline)]

First and foremost, thanks everyone for such diligent and detailed work;
also thanks for the interest in zshdb and contacting me about this.

In theory, I suppose it is possible to make this work, but in practice I
don't see much of a point of it here.

Some debuggers do support the notion of remote debugging -- in that
situation there need not be an interactive tty. zsh has the primitives to
support remote debugging (I think). But it's not something I want to
undertake; if someone else were interested in this enough to work on it I'd
help them out.

Also it is possible to segregate tests into those that require tty's and
those don't. For example test/unit/test-columnized.sh just tests the ability
to sort an array and display it in column order. It doesn't pull in the full
debugger or need an interactive tty (I think). However, segregating tests is
a bit of work for what strikes me as somewhat limited benefit.

I generally test everything before a release. And mosts system that want to
run zshdb have interactive tty's. So in the end I wonder what the overall
benefit of this would be to make the tests work for a scenario that is a bit
odd and out of the mainstream intended use.

Therefore what I suggest is do some sort of test to see if there's an
interactive tty and if not skip all of the tests. Or unconditionally skip
all tests when building on Debian for packaging.

2010/2/12 Clint Adams <schizo@debian.org>

> On Fri, Feb 12, 2010 at 12:16:16PM +0100, Loďc Minier wrote:
> > On Fri, Dec 11, 2009, Lucas Nussbaum wrote:
> > > Relevant part:
> >
> >  Actually that's not the whole relevant part; there's also:
> > checking whether make sets $(MAKE)... yes
> > get_processor:3: command not found: ps
> > ./ok4zshdb.sh:43: command not found: -if
> > checking Checking whether /bin/zsh is compatible with zshdb... Your zsh
> doesn't have the fc -l patches.
> > yes!
> > checking for diff... /usr/bin/diff
> > adding -w to diff in regression tests
> >
> >  This particular problem is due to a missing build-dep on procps which
> >  provides ps, used in test/zsh/ok4zshdb.sh:get_processor().
> >  (debootstrap --variant=buildd wont pull procps)
> >
> > > >
> /build/user-zshdb_0.03+git20090920-1-amd64-hSCnaM/zshdb-0.03+git20090920/lib/processor.sh:37:
> no such file or directory:
> >
> >  That's the meat of the problem: lib/processor.sh:37 breaks the build
> >  because it uses $TTY:
> > # For zsh, using this builtin parameter $TTY seems preferred over &0
> > # because it will find/fake a terminal when &0 might not be one.
> > exec {_Dbg_fdi}<$TTY
> >
> > TTY isn't set
> >
> >  I managed to reproduce the problem in my build environment with:
> >     sudo mv /dev/tty /dev/tty.bak
> >     env -i dpkg-buildpackage -b </dev/null >log 2>&1
> >  (obviously this might break your system)
> >
> >  So I believe the buildd environment has a partial /dev without
> >  /dev/tty.
> >
> >  I tried replacing $TTY with &0, and a real file, but that didn't work
> >  (hit the same test failures), and with a fifo, but that hanged the
> >  build waiting for the fifo to fill in.
> >
> >  I'm not familiar with zshdb, but I suspect it might need a TTY during
> >  debug sessions which might be why the testsuite would use one as well.
> >  Someone more familiar with zshdb could perhaps check whether we can use
> >  coproc here, or a pair of fifos (adding code to properly close them as
> >  well), to replace the use of $TTY.  Perhaps another way would be to
> >  pass a script (list of commands to run) to zshdb.
> >
> >  As a last resort, I tried running make check under "expect", but oddly
> >  that failed in the same way.  While expect correctly sets up stdin,
> >  stdout, stderr on a pty,
> >  test/integration/check-common.sh:run_test_check() ruins that effort by
> >  using redirections:
> >         (cd $srcdir && run_debugger $debugged_script 2>&1 >$TEST_FILE
> </dev/null)
> >  so zsh sees that stdin, stdout, and stderr aren't ttys and falls back
> >  to /dev/tty (which doesn't exist apparently).
> >
> >  So I tried working around that with:
> >     expect -c 'spawn zsh -c "ZSH_TTY=\$$TTY $(MAKE) check"; expect'
> >  and changing lib/processor.sh to use ZSH_TTY.  I don't know why *that*
> >  still fails.
> >
> >  So it seems the only way is to rework the testsuite to not rely on
> >  using a real tty...
>
> Rocky, any thoughts?  I guess at the worst case we could simply disable
> the tests if no tty is available.
>

[Message part 2 (text/html, inline)]

Message #45 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Loïc Minier <lool@dooz.org>

To: Rocky Bernstein <rocky.bernstein@gmail.com>

Cc: Clint Adams <schizo@debian.org>, 560665@bugs.debian.org, Lucas Nussbaum <lucas@lucas-nussbaum.net>

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 12 Feb 2010 23:52:47 +0100

[Message part 1 (text/plain, inline)]

On Fri, Feb 12, 2010, Rocky Bernstein wrote:
> Therefore what I suggest is do some sort of test to see if there's an
> interactive tty and if not skip all of the tests. Or unconditionally skip
> all tests when building on Debian for packaging.

 I think that's fair; let's make the Debian packaging only run make
 check if /dev/tty exists.  @Clint: would the attached patch be ok with
 you?  I fixed some other small things with respect to double builds and
 the like.

 (I noticed some additional issues such as the testsuite not working
 under my locale -- fr_FR.UTF-8 -- and some files getting cleaned by the
 upstream distclean which are in the tarball and wont be present in the
 second build, but didn't research these)

   Thanks,
-- 
Loïc Minier

[zshdb-testsuite2.diff (text/x-diff, attachment)]

Message #50 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Clint Adams <schizo@debian.org>

To: Loïc Minier <lool@dooz.org>

Cc: Rocky Bernstein <rocky.bernstein@gmail.com>, 560665@bugs.debian.org, Lucas Nussbaum <lucas@lucas-nussbaum.net>

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 12 Feb 2010 23:20:52 +0000

On Fri, Feb 12, 2010 at 11:52:47PM +0100, Loïc Minier wrote:
>  I think that's fair; let's make the Debian packaging only run make
>  check if /dev/tty exists.  @Clint: would the attached patch be ok with
>  you?  I fixed some other small things with respect to double builds and
>  the like.

Looks fine though I'm inclined to use /usr/bin/test -t to avoid the dep
on coreutils.

>  (I noticed some additional issues such as the testsuite not working
>  under my locale -- fr_FR.UTF-8 -- and some files getting cleaned by the
>  upstream distclean which are in the tarball and wont be present in the
>  second build, but didn't research these)

We can LC_ALL=C for the test.

Message #55 received at 560665@bugs.debian.org (full text, mbox, reply):

From: Clint Adams <schizo@debian.org>

To: Loïc Minier <lool@dooz.org>, 560665@bugs.debian.org

Cc: Rocky Bernstein <rocky.bernstein@gmail.com>, Lucas Nussbaum <lucas@lucas-nussbaum.net>

Subject: Re: Bug#560665: zshdb: FTBFS: tests failed

Date: Fri, 12 Feb 2010 23:23:14 +0000

On Fri, Feb 12, 2010 at 11:52:47PM +0100, Loïc Minier wrote:
> +  * Add procps build-dep to allow the testsuite to call "ps" in
> +    test/zsh/ok4zshdb.sh:get_processor().

Er, scratch my last comment.

Message #60 received at 560665-close@bugs.debian.org (full text, mbox, reply):

From: Clint Adams <schizo@debian.org>

To: 560665-close@bugs.debian.org

Subject: Bug#560665: fixed in zshdb 0.04+git20100102-1

Date: Sat, 13 Feb 2010 00:17:26 +0000

Source: zshdb
Source-Version: 0.04+git20100102-1

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

zshdb_0.04+git20100102-1.debian.tar.gz
  to main/z/zshdb/zshdb_0.04+git20100102-1.debian.tar.gz
zshdb_0.04+git20100102-1.dsc
  to main/z/zshdb/zshdb_0.04+git20100102-1.dsc
zshdb_0.04+git20100102-1_all.deb
  to main/z/zshdb/zshdb_0.04+git20100102-1_all.deb
zshdb_0.04+git20100102.orig.tar.bz2
  to main/z/zshdb/zshdb_0.04+git20100102.orig.tar.bz2



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 560665@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 12 Feb 2010 18:26:27 -0500
Source: zshdb
Binary: zshdb
Architecture: source all
Version: 0.04+git20100102-1
Distribution: unstable
Urgency: low
Maintainer: Clint Adams <schizo@debian.org>
Changed-By: Clint Adams <schizo@debian.org>
Description: 
 zshdb      - debugger for Z-Shell scripts
Closes: 560665
Changes: 
 zshdb (0.04+git20100102-1) unstable; urgency=low
 .
   [ Loïc Minier ]
   * Add procps build-dep to allow the testsuite to call "ps" in
     test/zsh/ok4zshdb.sh:get_processor().
   * Only run testsuite if /dev/tty exists and nocheck isn't in
     DEB_BUILD_OPTIONS; closes: #560665.
   * Split make check in its own check target.
   * Revise tty check to use "tty" instead of just checking for the presence of
     /dev/tty.
   * Clean debian/files.
   * Clean doc/zshdb.1 and test/lopts.check which are not cleaned up by the
     upstream build.
 .
   [ Clint Adams ]
   * New upstream snapshot.
   * Bump to Standards-Version 3.8.4.
   * Switch to 3.0 (quilt) source format.
   * Run testsuite with LC_ALL=C.
Checksums-Sha1: 
 3e49cc0c857b65ab124487a9b827d4e68e0620aa 1824 zshdb_0.04+git20100102-1.dsc
 2ec93bb8e733d86e87f6d5fd0b2739688ab0da55 92585 zshdb_0.04+git20100102.orig.tar.bz2
 75d05271055df25ed70fb5ab10d8bc8ebdac436e 90110 zshdb_0.04+git20100102-1.debian.tar.gz
 ec01de2bfd0d96b884fb4931f252c3e893b4476b 89366 zshdb_0.04+git20100102-1_all.deb
Checksums-Sha256: 
 93b298b944d87d3d873ae198553dbb83c2cd5b6aa292114d6770a8de82add8a0 1824 zshdb_0.04+git20100102-1.dsc
 8b3c958bf9361e7dad0ced59cef12ec27d68711d6bec1d60192bf0ed685f9d5f 92585 zshdb_0.04+git20100102.orig.tar.bz2
 6026d185d21ebede9e44da5f9c1677e477ea823b561b2919652900790a948f01 90110 zshdb_0.04+git20100102-1.debian.tar.gz
 1e8eee7b4deba3b181e6eed449659377abf968b2d2d86956aafcbfdd04f7ae3d 89366 zshdb_0.04+git20100102-1_all.deb
Files: 
 204ee80e6faa1297fbc695f4593c8295 1824 devel extra zshdb_0.04+git20100102-1.dsc
 d9720653b023741c025bd8351f27cda6 92585 devel extra zshdb_0.04+git20100102.orig.tar.bz2
 45b2b9d5d95a1cf5097e8409515b7d32 90110 devel extra zshdb_0.04+git20100102-1.debian.tar.gz
 bb5f326da4f24cc76dab6b32ac60a8ca 89366 devel extra zshdb_0.04+git20100102-1_all.deb

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

iQIcBAEBCgAGBQJLdeuDAAoJEFWSMx4ZnTiolEwP/0rwzf6F1tYP73qEm0scIjCE
qAirJBWCQ4whHz+VQeiHiRvhdPtwdmx5XmmF3JEbRpQGpUT5MyXl9Id+H7GFGqy9
Ish+Mk/8PWP8z+5LifO+QLIKwqfFaHzTE48ZqK+jP7VcdjVVUaRYgcfg0jLSFo54
w8cbvPc2EZdVxyb56Cn48g8rpyRZjHerGy/eXEHftv1OKWlEFvzjvo9wEYVOE5JS
EFR6kOpWau3sIw39lhjL0nsAu1uzYTrN8unSow2WfAc7OYQ/GvGw0xWd6cNQnhur
W4QNZlUpAg7+mWphjrE9q24wv82wAXnhmjoLDhTOxZdZnPWKK0uAQn6eDhg7L4NG
vxAU2LjPfzfyASKSIUkmbTrrZl4J+n3HQgfz+61IdTTYSTFBv98JwJ58egPr+pPk
t1VDGpLDFjyJrwYLS9qjSxIkFbRMi1vZK5maRFl3XNb8lNQyy58faaS2kNRI9DNN
GMS48WzVcQcKZz8l5BpjrLg1lPI7EZ9zhT0KDXudrAyopl5Rhifa9lIWLCmOjKsm
rjUuZ3nZWC3srMVZHV2vj98eCbJFiYq902ElPY0ge06vTKZvc8V4AzGqoJwx8xff
NIcEx3mM79pqVJTD0gas9r+izpEFf3LfZFIvcOLGHGfPeQWf3Fn9+Z0OmweYcr0H
/sQs2ZYQrEMdrPhW68Oi
=GEw2
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.