Bug#337587: bad behavior after Ctrl-C at wajig source continue prompt
Received Mon 07 Nov 2005 1:03am +1100 from John Belmonte: Graham, since you removed the implicit apt-get build-dep, this is likely no longer an issue for wajig source. However, it may be worth investigating if other commands such as wajig build have a similar issue. Yep. Now fixed. Thanks for the bug report John. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337587: bad behavior after Ctrl-C at wajig source continue prompt
Graham, since you removed the implicit apt-get build-dep, this is likely no longer an issue for wajig source. However, it may be worth investigating if other commands such as wajig build have a similar issue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337587: bad behavior after Ctrl-C at wajig source continue prompt
Graham Williams wrote:
Hi John,
Thanks for the bug report.
Could you show me the output of wajig -t source ... so I might
see where the question is being asked. I don;t get this question.
Regards,
Graham
Hi Graham, here you go:
$ wajig -t source swig1.3
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/john/.wajig/pelochan/tmpZWAGNN
Performing: apt-get build-dep 'swig1.3'
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
autoconf automake1.4 autotools-dev bison chicken chicken-dev gcj
gcj-4.0 gij
gij-4.0 guile-1.6 guile-1.6-dev guile-1.6-libs java-common libgcj-common
libgcj6 libgcj6-common libgmp3c2 libguile-ltdl-1 libice-dev
libncurses5-dev
libnettle2 libpcre3-dev libperl-dev libqthreads-12 libreadline5-dev
libruby1.8 libsm-dev libssl-dev libtool libttf2 libx11-dev libxext-dev
libxi-dev libxkbfile-dev libxt-dev libzzip-0-12 m4 mime-support ocaml
ocaml-base ocaml-base-nox ocaml-interp ocaml-nox php4-cgi php4-common
php4-dev pike7.6 pike7.6-core pike7.6-dev pike7.6-gdbm pike7.6-image
python-dev ruby1.8 ruby1.8-dev shtool tcl8.4 tcl8.4-dev tk8.4 tk8.4-dev
x-dev
0 upgraded, 61 newly installed, 0 to remove and 1 not upgraded.
Need to get 48.9MB of archives.
After unpacking 160MB of additional disk space will be used.
Do you want to continue [Y/n]?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337587: bad behavior after Ctrl-C at wajig source continue prompt
Package: wajig Version: 2.0.29 Severity: normal When running wajig source, hitting Ctrl-C at the Do you want to continue? prompt causes wajig to behave as if you've entered yes. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968) Versions of packages wajig depends on: ii apt 0.6.42.1 Advanced front-end for dpkg ii python2.3.5-3An interactive high-level object-o ii python-apt0.6.13.1 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]
Bug#337587: bad behavior after Ctrl-C at wajig source continue prompt
Received Sat 05 Nov 2005 2:49pm +1100 from John V. Belmonte: Package: wajig Version: 2.0.29 Severity: normal When running wajig source, hitting Ctrl-C at the Do you want to continue? prompt causes wajig to behave as if you've entered yes. Hi John, Thanks for the bug report. Could you show me the output of wajig -t source ... so I might see where the question is being asked. I don;t get this question. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
