The suggested workaround to generate a local repository of the packages that are built in ~/pbuilder/dist_result is a good one, but it is fragile because we are forced to assume the location of ~/pbuilder/dist_result when writing our ~/.pbuilderrc and hooks.
This is because pbuilder-dist does not export an environment variable with the build result directory.
Thus if someone were to call pbuilder-dist with the --buildresult option then everything will break.
If pbuilder-dist exported the build result directory as an environment variable that would be an improvement because it could be used to write a more robust ~/.pbuilderrc.
However, the real fix here is to accept the patch by Benjamin Drung. With that patch there would be no need for workarounds or hacks.
I am currently working around this bug also.
The suggested workaround to generate a local repository of the packages that are built in ~/pbuilder/ dist_result is a good one, but it is fragile because we are forced to assume the location of ~/pbuilder/ dist_result when writing our ~/.pbuilderrc and hooks.
This is because pbuilder-dist does not export an environment variable with the build result directory.
Thus if someone were to call pbuilder-dist with the --buildresult option then everything will break.
If pbuilder-dist exported the build result directory as an environment variable that would be an improvement because it could be used to write a more robust ~/.pbuilderrc.
However, the real fix here is to accept the patch by Benjamin Drung. With that patch there would be no need for workarounds or hacks.