On 11/07/11 09:23, S. Anthony Sequeira wrote:
Yes, but please don't close this bug yet, I'll check after the weekly
schedule is run from cron, and report then.
It ran successfully from cron this morning on all machines. Many thanks
for the help.
I'd say this report can be closed.
Regards
such missing module errors, I reckon it's the same as
#629303 happening with them.
Yes, I did mention this when I raised the bug.
Does it help?
Yes, but please don't close this bug yet, I'll check after the weekly
schedule is run from cron, and report then.
--
S. Anthony Sequeira
+44 7542 455
Identical symptoms...
The fourth is the last one I upgraded.
I can provide any information required, this is bugging me. :)
--
S. Anthony Sequeira
+44 7542 455 233
++
Ideals are like stars. You will not succeed in touching them with your
hands. But, like the seafaring man on the desert
Package: apt-xapian-index
Version: 0.41
Severity: normal
Probably related to bug: #629303, which was resolved by a reinstall:
/etc/cron.weekly/apt-xapian-index failed again at the scheduled time
with:
/etc/cron.weekly/apt-xapian-index:
Traceback (most recent call last):
File
Package: initscripts
Version: 2.88dsf-13.1
Severity: normal
Jun 26 10:16:44 tachyon fetchmail[1449]: starting fetchmail 6.3.18
daemon
Jun 26 10:16:44 tachyon /usr/sbin/gpm[1367]: *** info [mice.c(2059)]:
Jun 26 10:16:44 tachyon /usr/sbin/gpm[1367]: Detected EXPS/2 protocol
mouse.
Jun 26 10:16:46
On 21/06/11 19:37, Enrico Zini wrote:
On Tue, Jun 21, 2011 at 06:27:13PM +0100, S. Anthony Sequeira wrote:
[...]
It could be http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594814
(which noone has found out how to reproduce) or it could be something
else.
In the meantime, you can try
Package: apt-xapian-index
Version: 0.41
Severity: important
/etc/cron.weekly/apt-xapian-index fails:
/etc/cron.weekly/apt-xapian-index:
Traceback (most recent call last):
File /usr/sbin/update-apt-xapian-index, line 58, in module
import axi
ImportError: No module named axi
7 matches
Mail list logo
