Package: wajig
Version: 2.0.22
Severity: minor
Since the last 3 weeks or so, everytime I do a wajig update, after
downloading the package files, wajig sits there hogging the CPU for
~10-15 seconds. The same operation happens much more quickly (and
without eating any significant CPU) if I simply use aptitude
update or apt-get update.
While wajig is eating the CPU, I did a ps to see what kind of things
were eating the CPU:
root 19130 0.0 0.2 3820 1084 pts/0 S+ 17:00 0:00 /bin/sh
-f /usr/bin/wajig update
root 19131 0.1 0.9 8832 4860 pts/0 S+ 17:00 0:00
/usr/bin/python -O /usr/share/wajig/w
root 19335 0.0 0.2 3816 1056 pts/0 S+ 17:01 0:00 sh -c
set -o noglob; apt-cache dumpav
root 19336 0.2 0.7 11268 4060 pts/0 S+ 17:01 0:00
apt-cache dumpavail
root 19337 89.1 0.1 3052 752 pts/0 R+ 17:01 0:13 grep -E
^(Package|Version):
root 19338 0.0 0.0 2876 412 pts/0 S+ 17:01 0:00 tr ?
root 19339 0.0 0.2 4672 1464 pts/0 S+ 17:01 0:00 perl -p
-e s|Package: |?|g; s|Version
root 19340 0.0 0.0 28488 488 pts/0 S+ 17:01 0:00 sort
root 19343 0.0 0.0 3100 472 pts/0 S+ 17:01 0:00 tail +2
root 19344 0.0 0.1 2912 608 pts/0 S+ 17:01 0:00 sed s|
$||
Maybe its a bug with apt, I'm not sure. But its weird behavior for
sure. Do let me know if this has nothing to do with wajig (as I suspect)
and if so, where might the problem lie.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-2005-01-26
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages wajig depends on:
ii apt 0.5.28.4 Advanced front-end for dpkg
ii python 2.3.4-6 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]
