Thanks for the additional information Jeff and confirmation of the
problem on AMD64. Without access to such a machine its a little tricky
to debug but I'll see what I can do.
Regards,
Graham
Received Sun 06 Aug 2006 6:23am +1000 from Jeff King:
> Package: wajig
> Version: 2.0.34
> Followup-For: Bug #380242
>
> I was able to reproduce the same segfault (I note that both I and the
> original submitter are on amd64 -- maybe a bug in python on amd64?).
>
> Here's the result you asked for:
> $ wajig -t dependents wajig
> Performing: cat /var/lib/dpkg/status | egrep
> '^(Package|Status|Version):' | awk '/^Package: / {pkg=$2} /^Status:
> / {s1=$2;s2=$3;s3=$4} /^Version: / {print pkg,$2,s1,s2,s3}' | grep
> 'ok installed' | awk '{print $1,$2}' | sort >
> /home/peff/.wajig/sigio/tmpkOF_dA
> Performing: apt-cache showpkg wajig | awk 'BEGIN{found=0}/^Reverse
> Depends:/{found=1;next}/^[^ ]/{found=0}found==1{print}{next}' | sed
> 's|Reverse Depends:||' | tr "," " " | awk '{print $1}' | sort -u | grep
> -v '^$'
> Performing: apt-cache dumpavail > /home/peff/.wajig/sigio/tmprpfgQf
> s apt
> /usr/bin/wajig: line 8: 5639 Segmentation fault /usr/bin/python -O
> $WAJIGDIR/wajig.py "$@"
>
> I get the same error when doing 'wajig new' which also does an apt-cache
> dumpavail right before dying. Perhaps there's something confusing in the
> parsing of that result. Other wajig commands I tried ran fine (e.g.,
> dist-upgrade) and running python works fine. I can send the results of
> apt-cache dumpavail if you want, but it is, of course, large.
>
> -- System Information:
> Debian Release: testing/unstable
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.17-1-amd64-k8
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>
> Versions of packages wajig depends on:
> ii apt 0.6.45 Advanced front-end for dpkg
> ii python 2.3.5-11 An interactive high-level
> object-o
> ii python-apt 0.6.19 Python interface to libapt-pkg
>
> wajig recommends no packages.
>
> -- no debconf information
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
