gitian-builder icon indicating copy to clipboard operation
gitian-builder copied to clipboard

failed to run on-target -u root bash < target-bin/upgrade-system.sh >> var/install.log 2>&1 (RuntimeError)

Open Kailkox opened this issue 3 years ago • 2 comments

Hi, I'm building my own cryptocurrency to windows executable. I was following that guy on yt: https://www.youtube.com/watch?v=_ti-d5t1WX8 I was using tips from https://github.com/devrandom/gitian-builder/issues/180 too, and got some progress, but now I'm stuck on this error: Upgrading system, may take a while (log in var/install.log) Traceback (most recent call last): from ./bin/gbuild:334:in <main>' from ./bin/gbuild:334:in each' from ./bin/gbuild:336:in block in <main>' from ./bin/gbuild:336:in each' from ./bin/gbuild:341:in block (2 levels) in <main>' from ./bin/gbuild:138:in build_one_configuration' ./bin/gbuild:23:in `system!': failed to run on-target -u root bash < target-bin/upgrade-system.sh >> var/install.log 2>&1 (RuntimeError)

My install.log is:

Setting up zip (3.0-4) ... Setting up binutils-mingw-w64-i686 (2.22-2ubuntu1+1) ... Setting up binutils-mingw-w64-x86-64 (2.22-2ubuntu1+1) ... Setting up faketime (0.8-1) ... Setting up mingw-w64-dev (2.0.1-1) ... Setting up gcc-mingw-w64-base (4.6.3-1ubuntu5+5ubuntu1) ... Setting up gcc-mingw-w64-i686 (4.6.3-1ubuntu5+5ubuntu1) ... Setting up g++-mingw-w64-i686 (4.6.3-1ubuntu5+5ubuntu1) ... Setting up gcc-mingw-w64-x86-64 (4.6.3-1ubuntu5+5ubuntu1) ... Setting up g++-mingw-w64-x86-64 (4.6.3-1ubuntu5+5ubuntu1) ... Setting up g++-mingw-w64 (4.6.3-1ubuntu5+5ubuntu1) ... Setting up gcc-mingw-w64 (4.6.3-1ubuntu5+5ubuntu1) ... Setting up mingw-w64 (2.0.1-1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place stdin: is not a tty

And I don't know if I'm doing something wrong, or what.

Kailkox avatar Jan 07 '22 20:01 Kailkox

Have you fixed it? Its the same error here for me. It used to work earlier but its not working again

Vitalik-Hakim avatar Feb 07 '22 22:02 Vitalik-Hakim

Have you fixed it? Its the same error here for me. It used to work earlier but its not working again

oh, so im not alone with that, I'm creating new virtual machine to fix this, hope it works I will give info in few hours about that

Kailkox avatar Feb 09 '22 15:02 Kailkox