Package: wajig Version: 2.0.22 Followup-For: Bug #288852 I too have observed this behaviour. The problem is that wajig is running grep under my default locale (en_GB.UTF-8 in my case) which is much slower than grep in C locale. This is arguably a grep bug, but the practical upshot is that wajig needlessly hogs the CPU.
An example command under which this happens is wajig daily-upgrade, which is one of the commands I use most frequently, so it's particularly annoying. Rather than blanket-setting the locale as it did before, perhaps wajig could specifically set the C locale before running sub-commands where a) it doens't matter (from a locale point of view) and b) the program being run is much slower under a non-8-bit locale. grep is in fact the only such command that springs immediately to mind. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages wajig depends on: ii apt 0.5.28.1 Advanced front-end for dpkg ii python 2.3.4-5 An interactive high-level object-o ii python-apt 0.5.10 Python interface to libapt-pkg -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
