Dev Random

It is a known issue that Gitian depends on an apt-cache mirror. You can set it to some host other than the default via the MIRROR_HOST environment variable. The PR...

A simple workaround for now is to execute the following after an LXC `gbuild`: `cp -a --sparse=always target-trusty-amd64 base-trusty-amd64`

(this is equivalent to running `gbuild -i` BTW, so it's not as clean... the build artifacts will remain, but that normally shouldn't affect future builds)

I was just going to suggest that. Here's the outline of the commands: ``` export SUITE=trusty export ARCH=amd64 make-clean-vm on-target -u root apt-get update on-target -u root bash < target-bin/upgrade-system.sh...

That's a good point. I just pushed a commit to make it idempotent: https://github.com/devrandom/gitian-builder/commit/7219c490cccf332837753690c6e21bfc8041ed0c

Right, I have a `|| true` on that line to make it idempotent. On 2015-06-05 07:22 AM, Michagogo wrote: > I seem to be getting an error, something about already...

What is the exact error?

I would prefer if this (or #249) would disable the caching based on a command line flag.

Well, the ideal solution for non-Debian OSes would be to run the apt-cache in a VM or a docker and point the gitian builder at that.

Maintaining per-OS conditionals is not ideal from a maintenance burden point of view. And a command line flag isn't that much additional effort.