Please note that the testing PPA will always contain the newest PackageKit Debian package (even if it is an unstable version) - so take care if you use it. The problem has already been fixed, the very last step is to get it uploaded to Ubuntu, where I don't have the rights to do this. So we just need to wait.
The way to detect if git-buildpackage should be used is only heuristic. Someone could check for a "gpb.conf" file in "debian/" (which does not have to be there) or check if branches "upstream" and "pristine-tar" are present. But usually Debian maintainers can figure out how to build a package from a Git source - usually it's git-buildpackage. I don't see that much need to make this process super-duper-user-friendly, as it's very technical and requires some knowledge by design. But you can ask the debuild maintainers to include an hint to use gbp. Or you maybe can improve the documents. I don't know if the KDE bug is related, we'll see. Thanks for confirming that this bug here is fixed with the new PK release which will be synced with Oneiric! Btw: You might want to remove the Smart package manager and PackageKit's Smart backend which you installed with your commands above ;-) Cheers, Matthias -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847591 Title: Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/847591/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
