Ubuntu
ubuntu-dev-tools package

[pbuilder-dist] Use packages from ~/pbuilder/dist_result to satisfy deps

Bug #371221 reported by Rail Aliiev on 2009-05-03

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	ubuntu-dev-tools (Ubuntu)	Triaged	Wishlist	Unassigned

Bug Description

Binary package hint: ubuntu-dev-tools

Use case: sometimes I need to build 2 packages and second one depends on the first one.

It will be great to add a command line switch to pbuilder-dist which would enforce pbuilder-dist to use of built packages from ~/pbuilder/dist_result to satisfy dependencies.

Currently I use pbuilder's hooks to generate simple repository but I need to set it up for every distro separately.

Tags:

Siegfried Gevatter (rainct) on 2009-05-03

Changed in ubuntu-dev-tools (Ubuntu):
importance:	Undecided → Wishlist
status:	New → Triaged

Revision history for this message

Stefano Rivera (stefanor) wrote on 2010-12-03:

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{

Revision history for this message

Siegfried Gevatter (rainct) wrote on 2010-12-04: Re: [Bug 371221] Re: [pbuilder-dist] Use packages from ~/pbuilder/dist_result to satisfy deps

2010/12/3 Stefano Rivera <email address hidden>:
> 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).

Revision history for this message

Benjamin Drung (bdrung) wrote on 2013-12-19:

use-local-repository.patch Edit (6.4 KiB, text/plain)

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.

Ubuntu Foundations Team Bug Bot (crichton) on 2013-12-19

tags:

added: patch

Revision history for this message

Andrew Bate (andrewdbate) wrote on 2021-11-26:

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.