update-apt-xapian-index: dies with an unknown opcode

[Martin-Éric Racine]

/etc/cron.daily/apt:
XXX lineno: 679, opcode: 165
Traceback (most recent call last):
 File "/usr/sbin/update-apt-xapian-index", line 104, in <module>
   indexer.rebuild(opts.pkgfile)
 File "/usr/lib/pymodules/python2.6/axi/indexer.py", line 681, in rebuild
   self.buildIndex(dbdir, generator)
 File "/usr/lib/pymodules/python2.6/axi/indexer.py", line 656, in buildIndex
   for doc in documents:
 File "/usr/lib/pymodules/python2.6/axi/indexer.py", line 538, in gen_documents_apt
   yield self.get_document_from_apt(pkg)
 File "/usr/lib/pymodules/python2.6/axi/indexer.py", line 506, in get_document_from_apt
   addon.obj.index(document, pkg)
 File "/usr/share/apt-xapian-index/plugins/sizes.py", line 74, in index
   ver = pkg.candidate
 File "/usr/lib/python2.6/dist-packages/apt/package.py", line 679, in candidate
   def candidate(self):
SystemError: unknown opcode

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-xapian 1.0.20-1
ProcVersionSignature: Ubuntu 2.6.32-10.14+bug396286v2-generic
Uname: Linux 2.6.32-10-generic i586
Architecture: i386
Date: Thu Sep 9 07:42:57 2010
ProcEnviron:
 LANGUAGE=fi_FI:fi:en_US:en
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: xapian-bindings

[Olly Betts (ojwb)]

This doesn't look like a bug in python-xapian to me - it doesn't feature at all in the backtrace.

[Olly Betts (ojwb)]

It seems most likely this is a bug in python's byte code compilation or interpreter.

[Matthias Klose (doko)]

unlikely. you need to look at the .pyc file which is missing

[Olly Betts (ojwb)]

xapian-bindings still doesn't feature in the backtrace...

[Martin-Éric Racine (q-funk)]

Sorry, what missing .pyc file?

[Olly Betts (ojwb)]

I would imagine the relevant one is the lowest level of the backtrace, i.e.:

/usr/lib/python2.6/dist-packages/apt/package.pyc

[Martin-Éric Racine (q-funk)]

Repeatedly marking the bug as invalid just because you cannot agree on which package is at cause is not productive.

[Richard Boulton (richardboulton)]

Is it possible to reassign bugs to another package? I think this bug should be assigned to apt-xapian-index (since the bug is occurring when running a program from that package), or possibly python-apt (since it looks like a problem with a python file from python-apt). It might have a chance of being fixed there, since the backtrace looks to me like an invalid .pyc file for has been generated (no idea how) for /usr/lib/python2.6/dist-packages/apt/package.py, which I think is part of python-apt. The Xapian developers don't have particular expertise in broken .pyc files.

As Olly says, xapian-bindings doesn't feature in the backtrace at all, and I can't see how it could be related to this bug. Therefore, as far as xapian-bindings is concerned, the bug is invalid. I would try reassigning to python-apt or apt-xapian-index, but I can't see any option for doing that in the UI here.

[Martin-Éric Racine (q-funk)]

It was filed against the right binary package. I suspect that the source package that generate the target happens to have been auto-selected by 'ubuntu-bug'

[Richard Boulton (richardboulton)]

How unhelpful of ubuntu-bug.

If anyone knows a way to change the package this ticket is filed against, please do so (and remove xapian-developers from the list of subscribers while you're at it). Otherwise, I suggest that this ticket should remain marked as invalid, and a new ticket should be filed without using ubuntu-bug's "assistance".

[Olly Betts (ojwb)]

It looks like it was filed against python-xapian, which is a binary package built from the xapian-bindings source package:

    Package: python-xapian 1.0.20-1

Richard: Select "Also affects distribution" and enter the source package name there.

[Colin Watson (cjwatson)]

Martin-Éric, perhaps you could attach your /usr/lib/python2.6/dist-packages/apt/package.pyc file and the corresponding .py, so that we can see whether it looks corrupted.

[Martin-Éric Racine (q-funk)]

Here's the .pyc

[Martin-Éric Racine (q-funk)]

Here's the .py