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
Here is a quick and dirty implementation that adds an --use-local
parameter. It involves creating a local repository (Packages and Release
files), signing them with gpg, add the key to the repository and
updating it before building.
** Patch added: use-local-repository.patch
** Tags added: patch
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/371221
Title:
[pbuilder-dist] Use packages from ~/pbuilder/dist_result to satisfy
deps
To manage notifications
2010/12/3 Stefano Rivera launch...@rivera.za.net:
Do we want this as a default behavior?
No, I don't think so.
pbuilder-dist doesn't take options.
Actually, it does take one option (--main-only, plus --debug-echo, if
you want to count it).
--
You received this bug notification because you are
Do we want this as a default behavior? pbuilder-dist doesn't take
options.
Note that it does currently support /var/cache/archive/$dist (although
it doesn't run dpkg-scanpackages on it{
--
You received this bug notification because you are a member of MOTU,
which is subscribed to
** Changed in: ubuntu-dev-tools (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New = Triaged
--
[pbuilder-dist] Use packages from ~/pbuilder/dist_result to satisfy deps
https://bugs.launchpad.net/bugs/371221
You received this bug
