Comment 2 for bug 1071029

I've exhausted my Internet search and have found two articles on how to use pbuilder-scripts:

http://www.mattfischer.com/blog/?p=514
http://askubuntu.com/questions/53014/why-use-sbuild-over-pbuilder

They are very good. But the problem is that they are *wrong* at the same time. E.g.,

http://www.mattfischer.com/blog/?p=514 says,

"To avoid polluting the root folder, I generally lay the folders out like this:

~/Projects/raring-i386/project/project-0.52

Then I just do this

cd ~/Projects/raring-i386/project/project-0.52
pbuild"

It never works for me that way. Whenever I use pbuild, I will always get:

$ pbuild
Could not determine project. Please specify one with -p.

Also it doesn't show how to use the "pget" from the package to get the source before building.

Moreover, when I tried the pget from the package, the result is not consistent with above folder layout. E.g., when try to pget pbuilder-scripts source, the folder layout I get is

~/Projects/saucy/pbuilder-scripts-19

instead of the recommended

~/Projects/saucy/pbuilder-scripts/pbuilder-scripts-19

Furthermore, http://askubuntu.com/questions/53014/why-use-sbuild-over-pbuilder says,

"# 'quantal-armhf' is the name of the chroot created earlier
# results in downloading package to: ~/Projects/quantal-armhf/casper/
pget quantal-armhf casper"

and I found that wrong as well:

$ pget saucy pbuilder-scripts
Could not determine project. Please specify one with -p.

The only I get it working is:

$ pget -p saucy pbuilder-scripts
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/saucy.tgz]
...