KPackageKit error when searching for packages

[Heimen Stoffels]

Binary package hint: kpackagekit

When I'm searching for a package in KPackageKit on Kubuntu 10.04 RC, I'm getting this error:

Error Type: Error Value: 'in ' requires string as left operand, not list File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2213, in main() File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2210, in main run(args, options.single) File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 2172, in run backend.dispatcher(args) File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 723, in dispatcher self.dispatch_command(args[0], args[1:]) File : /usr/lib/python2.6/dist-packages/packagekit/backend.py, line 672, in dispatch_command self.search_name(options, values) File : /usr/share/PackageKit/helpers/apt/aptBackend.py, line 617, in search_name if search in pkg_name:

It displays this error and no search results are displayed.

Can you guys please fix this before 10.04 Final comes out?

[Heimen Stoffels (vistaus)]

Hmm, updating works fine though.

[Sebastian Heinlein (glatzor)]

Have you build PackageKit 0.6.x from source?

[Heimen Stoffels (vistaus)]

No, I haven't.

[Heimen Stoffels (vistaus)]

Seems like this bug isn't going tp be fixed before 10.04 comes out tomorrow.. You can't ship an LTS-release if package management is broken.

[Heimen Stoffels (vistaus)]

Hmm, no response on this bug.. How come? Is this bug so difficult?

[Sebastian Heinlein (glatzor)]

I cannot reproduce this bug here. What is your search string?

[Heimen Stoffels (vistaus)]

Everything I search for results in this error.

Btw, I heard more people about this bug on mailing lists and kubuntuforums so it should be reproducable.

[Heimen Stoffels (vistaus)]

Even the KPackageKit update manager gives an error now since today.

Never mind, if you guys aren't fixing it, then I'm ditching KPackageKit forgood. KPackageKit is on it's way, but if it's half broken, then I'm better off with good ol' Adept.
If you guys pay attention to this bug again, then I'm glad to help of course.

[Zus Nelem (zusvonnelem)]

i am using Kubuntu 10.04. i came across this error (my pastebin for the same as in descritpion http://pastebin.com/x2FCHAVg) i noticed this after i followed directions on a ppa for ktorrent 4.0.

[Guilo (guilo19)]

Exactly the same. I wanted ktorrent 4.0 and had to add a new repository : apt-add-repository ppa:blca/published

It gave me an update of kpackagekit : it has more features in configuration but nothing is working. How can I fond which version it is ?

[Sebastian Heinlein (glatzor)]

Vistaus: could you please copy and paste the output of the following commands:

apt-cache policy kpackagekit

apt-cache policy python-packagekit

apt-cache policy packagekit-backend-apt

Do you use PPAs?

[Sebastian Heinlein (glatzor)]

@Guilo:

Please understand that we can only support packages from Ubuntu. See the above commands for getting the installed versions.

[Heimen Stoffels (vistaus)]

Yes, I use PPAs. But not one of them contains a KPK upgrade as you can see in the output:

vistausss@vistausss-laptop:~$ apt-cache policy kpackagekit
kpackagekit:
  Installed: 0.5.4-1ubuntu4.1 0
  Candidate: 0.5.4-1ubuntu4.1 0
  Versietabel:
 *** 0.5.4-0ubuntu4.1 0
       500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
     0.5.4-0ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
vistausss@vistausss-laptop:~$

vistausss@vistausss-laptop:~$ apt-cache policy python-packagekit
python-packagekit:
  Installed: 0.5.7-0ubuntu2 0
  Candidate: 0.5.7-0ubuntu2 0
  Versietabel:
 *** 0.5.7-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
vistausss@vistausss-laptop:~$
vistausss@vistausss-laptop:~$ apt-cache policy packagekit-backend-apt
packagekit-backend-apt:
  Installed: 0.5.7-0ubuntu2 0
  Candidate: 0.5.7-0ubuntu2 0
  Versietabel:
 *** 0.5.7-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
vistausss@vistausss-laptop:~$

[Matthias Klumpp (ximion)]

Please use the APTcc backend instead of the APT backend to avoid this issue.
(Development of APT backend seems to have stopped now...)