According to this site, there's a new ppa for gimp. Seems to be working fine, installation instructions are the following:
sudo add-apt-repository ppa:otto-kesselgulasch/gimp
sudo apt-get update
sudo apt-get install gimp
The answer is that you don't. pbuilder takes the source package and builds binaries. It also can take the source code without a source package built and create the binaries that you would either host yourself or add to your own debian repository systems to host on your own.
That's not what you need for a PPA.
What you want to do, and what I strongly recommend, is that you follow traditional packaging procedures, and run debuild -S on the code, with the directory for the package there, containing the source code, the debian/ folder, and everything else.
Then, after you've built the source package by debuild -S, you can then upload the created .changes file in one directory above the source directory to the PPA via dput. (this step is referred to on Launchpad's PPA Uploading help docs).
You can in theory use pdebuilder to keep your system clean and build inside a chroot, but read on for my statements on this, as to why it failed previously for you.
Per the comments, you have correctly identified that debhelper is unable to find the autoreconf plugin.
Also as I said in my comments on this answer, pbuilder and pdebuilder are both not smart enough to determine the debhelper dependencies.
To solve your issue so that your stuff can build, you will have to manually use pbuilder or pdebuilder to login to the chroot. Then, you will have to manually install dh-autoreconf into the chroot, usually with apt-get install dh-autoreconf after you've logged into the chroot.
Once you've done that, and saved the state of the chroot, you should be able to pbuilder or pdebuilder your package.
(However, I prefer traditionally working with packages, and I don't care if my build system is entirely clean or not, all I really build are source packages, and the debhelper plugins aren't going to clutter my system that badly)
Best Answer
I'm using pbuilder with an enhanced config and not pbuilder-dist but the steps should be basically the same:
Add your extra sources to the
OTHERMIRRORvariable in your~/.pbuilderrc:Chroot into your pbuilder environment to add the repository keys (or alternatively create a local keyring with those two keys and add it to
APTKEYSTRINGSvariable or add your local/etc/apt/trusted.gpgkeyring):(Of course you can extend your sources.list directly and skip step 1 and 3 but an
pbuilder-dist updatewill reset the sources.list.)Update your pbuilder environment (with plain pbuilder you have to add
--override-config):Note: Since raring a development release has the
proposedsources enabled as default. This is done by passing theproposedsources to pbuilder's--othermirrorcommand line option - which overwrites the config file value. So you have to use the--release-onlyswitch.Build your package: