Re: pkg_comp: How to keep sandbox active?

[Mayuresh <mayuresh%acm.org@localhost>]

On Sun, Jul 10, 2022 at 03:59:30PM +0530, Mayuresh wrote:
> Firstly how to avoid landing in a state where sandbox exists and mounts
> don't. Secondly are manual mounts required now to get out of this
> situation?

Turns out, pkg_comp does the mounts automatically, hence it's ok to not
see them after pkg_comp exits. The problems I faced were due to missing
logs and packages/All directories which I created manually.

Now facing a different error: (*.tgz No such file)

# pkg_comp -c local build bash
pkg_comp: I: Adding packages to be built to pbulk.list
pkg_comp: I: Starting pbulk build in the sandbox
Scanning...
. 1/1
Resolving...
Scanning...
.... 4/4
Resolving...
Scanning...
... 3/3
Resolving...
Scanning...
.. 2/2
Resolving...
Building...
Initialisation complete.
[1/10] Starting build of  cwrappers-20220403
[1/10] Failed to build    cwrappers-20220403
Building pkg_summary...
Build reports...
Sending report mail...
Uploading report...
Uploading packages...
pkg_comp: I: Generating pkg_summary
ls: *.tgz: No such file or directory
pkg_comp: E: Failed to build cwrappers-20220403; see
/usr/pkgsrc/packages/log/ for detailed logs

-- 
Mayuresh