After creating a ~/.devscripts file (another detail missing from your recommended tutorial) that sets DEBSIGN_MAINT and DEBSIGN_KEYID to my email address and key id respectively, the git-buildpackage tool ran to completion.
-- "If you want a working PK *right now*," Well, of course I will switch to the official package once it is working, but yes, I would like my broken system fixed as soon as possible, and I'm willing to do some work to make it happen. I thought that would have been obvious from my level of participation so far. I can testify that after the following steps, I can now purge and install a package without getting the originally-reported error: * git clone git://anonscm.debian.org/pkg-packagekit/packagekit.git * sudo apt-get build-dep packagekit * sudo apt-get install git-buildpackage * echo '[email protected]' > ~/.devscripts * echo 'DEBSIGN_KEYID=02811FE8' >> ~/.devscripts * cd packagekit * git-buildpackage * cd ../build-area * sudo dpkg -i *.deb * sudo apt-get install smartpm-core python-smartpm Hopefully this will fix a possibly related problem. See https://bugs.kde.org/show_bug.cgi?id=281650 ** Bug watch added: KDE Bug Tracking System #281650 http://bugs.kde.org/show_bug.cgi?id=281650 -- 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
