Hello,
thanks for the report.
Until I have time to dig down into this issue, you could try to disable
the debtagsplugin as a workaround.
Check the config XML-file $HOME/.packagesearch and add the line
<Plugin directory="plugins/" version="2.0" enabled="0" author="Benjamin
Mesing" name="aptplugin" />
into the <DisabledPlugin> node.
If you have an entry like this:
<DisabledPlugins/>
you have to replace it with
<DisabledPlugins>
<Plugin directory="plugins/" version="2.0" enabled="0" author="Benjamin
Mesing" name="aptplugin" />
</DisabledPlugins>
If you already have something like
<DisabledPlugins>
....
</DisabledPlugins>
Simply insert the line mentioned above. But probably you are familar
with XML anyways :-)
Now that I think about it, this is probably a bug only for older
versions of packagesearch, debtags was and is under heavy development.
It might be possible, that the 1.2 version of packagesearch which was
linked statically against the libdebtags available at the time, does no
longer work with the new debtags database format. The issue should _not_
be present in the packagesearch version currently in unstable (which is
2.0 and pretty cool :-).
Greetings Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
