Your message dated Tue, 9 Sep 2014 09:02:49 +0200
with message-id
<trinity-dcf1015e-3520-4c37-a8ed-a029c1bc964e-1410246169739@3capp-gmx-bs70>
and subject line Fixed in 2.7.2
has caused the Debian Bug report #676811,
regarding packagesearch: apparently enters an endless loop if xapian index is
missing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
676811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676811
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: packagesearch
When I started packagesearch the first time in a multiarch Debian/Sid
chroot (including the usual mounts) as root, it complained that the
xapian index was not generated and offered to generate it. The systems
CPU usage raised to 100% and nothing user visible happend in the one or
two minutes I waited, neither in the GUI nor on the terminal I used to
start packagesearch.
The output of ps axuf contained:
| root 16779 85.2 0.3 377520 19780 pts/22 Rl+ 13:51 1:25 | |
\_ packagesearch
| root 16784 0.0 0.0 0 0 pts/22 Z+ 13:52 0:00 | |
\_ [packagesearch] <defunct>
| root 16785 0.0 0.0 148796 3712 pts/29 Ss+ 13:52 0:00 | \_
/bin/zsh
I saw no process that seemed to be related to xapian or apt.
If I just did not wait long enough and missed the xapian process, then
there are still two issues:
* PID 16784 was a zombie.
* There should be something user visible whilst the xapian cache is
generated, or at least the user notice should be noticed that
generating the cache might take some minutes.
After manually invoking /usr/sbin/update-apt-xapian-index --update,
packagesearch started as expected.
Regards
Carsten
--- End Message ---
--- Begin Message ---
Version: 2.7.2
thanks
This was fixed long ago: changelog entry here:
* changed RunCommandInXterm to use /usr/bin/uxterm, because
only there I can guarantee consistent behaviour (Closes: #676811)
* make apt default package management tool
* inform user to configure to use apt if aptitude
is not available (Closes: #676810)
* fixed several multiarch issues
--- End Message ---
