Mac version issue #132

Activity

1. josephbisch commented on Sep 28, 2016

   

   josephbisch

   on Sep 28, 2016

   Collaborator

   More actions

   You need to check var/build.log (in your gitian-builder directory) to see what the error is.
2. devrandom

   added

   Feedback

   on Oct 2, 2016
3. unsystemizer commented on Nov 5, 2016

   

   unsystemizer

   on Nov 5, 2016

   Last edited by unsystemizer

   More actions

   I got this same error building Linux (with LXC and cached packages). I messed around with it (re-created apt-cacher-ng cache, upgraded it to a newer version from Debian testing, etc.) and think I got past this particular error that way.

   Upgrading system, may take a while
   ./bin/gbuild:21:in `system!': failed to run on-target -u root bash < target-bin/upgrade-system.sh > var/install.log 2>&1 (RuntimeError)
           from ./bin/gbuild:105:in `build_one_configuration'
           from ./bin/gbuild:285:in `block (2 levels) in <main>'
           from ./bin/gbuild:280:in `each'
           from ./bin/gbuild:280:in `block in <main>'
           from ./bin/gbuild:278:in `each'
           from ./bin/gbuild:278:in `<main>'
   

   Install.log didn't contain any additional information, by the way.

   But then I ran into the same error that you pasted, but in copy-from-target.
   I tried many things so I'm not sure what it was, but I think it's related to the way tar commands work.
   I looked at closed bugs here and there was a bug about tar a while ago.
   I injected some logging into the scripts (no idea whether I did it right) and got this:

   tar: This does not look like a tar archive
   tar: Exiting with failure status due to previous errors
   

   I don't know if this makes any sense and it's in another area, but it may be related.
   Originally I used Debian 8.6 with testing repos added separately but I nuked the whole thing after having spent 8 hours trying to make it work, so I can't provide additional details.