gitian build is not formed by using the cmd ./bin/gbuild --commit batan=HEAD ../bitcoin/contrib/gitian.yml

[satyamakgec]

i execute the cmd -- ./bin/gbuild --commit batan=HEAD ../bitcoin/contrib/gitian.yml but it requires some qt-win-4.8.5.zip i download this as per the release-process.txt file but when i execute cmd --- ./bin/gbuild ../batan/contrib/gitian-descriptors/qt-win.yml to make zip available to the gitian build in the folder gitian-descriptors but it again show some error ----

explorer@CMT-PC:~/gitian-builder$ sudo ./bin/gbuild ../batan/contrib/gitian-descriptors/qt-win.yml
--- Building for precise amd64 ---
Stopping target if it is up
Making a new image copy
Formatting 'target-precise-amd64.qcow2', fmt=qcow2 size=11811160064 backing_file='base-precise-amd64.qcow2' encryption=off cluster_size=65536 lazy_refcounts=off
Starting target
Checking if target is up...............
Connection timed out during banner exchange
./bin/gbuild:21:in system!': failed to run on-target true (RuntimeError) from ./bin/gbuild:73:inbuild_one_configuration'
from ./bin/gbuild:285:in block (2 levels) in <main>' from ./bin/gbuild:280:ineach'
from ./bin/gbuild:280:in block in <main>' from ./bin/gbuild:278:ineach'
from ./bin/gbuild:278:in `

'
then how do i resolve this issue please help me in this problem

Thanks

[josephbisch]

The "Connection timed out during banner exchange" is the clear issue. Ssh fails to connect. Are you using a recent version of python-vm-builder?

Actually, I see you are trying to use a qt-win.yml descriptor. Bitcoin Core no longer includes a specific descriptor for building qt. If you are trying to build an old version of Bitcoin Core or an altcoin based on an old version of Bitcoin Core, it may be possible that you are having trouble because you are using a recent gitian-builder. If you are using a recent gitian-builder, that may be an explanation.

I would read documentation or contact the software project that you are trying to build and see what their instructions are for building with Gitian (either batan or bitcoin, it seems like you combine a commit name of batan with a descriptor for bitcoin). If you are building Bitcoin Core, then the development head isn't usually used as the commit option for Gitian builds I believe.

[aniket-kumar]

I am also getting the same error in running : ./bin/gbuild ../coinname/contrib/gitian-descriptors/boost-win32.yml .
Error is Checking if target is up.......... Connection timed out during banner exchange bin/gbuild:21:in system!': failed to run on-target true (RuntimeError)
from bin/gbuild:73:in build_one_configuration' from bin/gbuild:285:in block (2 levels) in

'
from bin/gbuild:280:in each' from bin/gbuild:280:in block in '
from bin/gbuild:278:in each' from bin/gbuild:278:in '`

I am stucked here since 5 days. I tried multiple things but it never goes successful. Any help will be appreciated a lot. Please look into this.

[josephbisch]

I don't know which coin it is that you are trying to build. Maybe including the contents of boost-win32.yml would be helpful.

As I mentioned to @satyamakgec in my first comment here, Bitcoin Core no longer separates out the descriptors in the way that whatever coins you two are trying to build do so.

It would be most helpful if you can link to the descriptors and the instructions that you are following that lead up to these errors.

[aniket-kumar]

I have created one altcoin by making some configuration changes. I am following the guide given in doc folder release-process.md file. My coin is also pow based. Content of boost-win32.yml are as
`

name: "boost"
suites:

"xenial"
architectures:
"i386"
packages:
"mingw32"
"faketime"
"zip"
reference_datetime: "2011-01-30 00:00:00"
remotes: []
files:
"boost_1_50_0.tar.bz2"
script: |
TMPDIR="$HOME/tmpdir"
mkdir -p $TMPDIR/bin/$GBUILD_BITS $TMPDIR/include
tar xjf boost_1_50_0.tar.bz2
cd boost_1_50_0
echo "using gcc : 4.4 : i586-mingw32msvc-g++
:
i586-mingw32msvc-windres
i586-mingw32msvc-ar
-frandom-seed=boost1
;" > user-config.jam
./bootstrap.sh --without-icu
./bjam toolset=gcc target-os=windows threadapi=win32 threading=multi variant=release link=static --user-config=user-config.jam --without-mpi --without-python -sNO_BZIP2=1 -sNO_ZLIB=1 --layout=tagged --build-type=complete $MAKEOPTS stage
for lib in chrono date_time exception filesystem graph iostreams math_c99f math_c99l math_c99 math_tr1f math_tr1l math_tr1 prg_exec_monitor program_options random regex serialization signals system test_exec_monitor thread_win32 unit_test_framework wave wserialization; do
mkdir $lib
(cd $lib ; ar xf ../stage/lib/libboost_${lib}-mt-s.a)
mv $lib $TMPDIR/bin/$GBUILD_BITS
done
cp -a boost $TMPDIR/include
cd $TMPDIR
export LD_PRELOAD=/usr/lib/faketime/libfaketime.so.1
export FAKETIME=$REFERENCE_DATETIME
zip -r boost-win32-1.50.0-gitian2.zip *
cp boost-win32-1.50.0-gitian2.zip $OUTDIR
`

[aniket-kumar]

Please let me know if you require anything else to get it resolved. i have downloaded the related dependencies successfully as listed in the same doc.

[josephbisch]

It may have to do with the ssh timeout not being enough for your system. In the past it was increased and is currently 30 seconds, but maybe that isn't enough? Here's the last PR that increased the timeout, so you can see if making those changes to a larger number (maybe 60 seconds?) gets rid of the connection timeout.

Have you tried to follow the sanity checks from the gitian-builder readme? Here's the specific instructions, based on it appearing that you are using xenial and kvm.

cd gitian-builder
PATH=$PATH:$(pwd)/libexec
make-clean-vm --suite xenial --arch i386
# For KVM:
start-target 32 xenial-i386 &
# wait a few seconds for VM to start
on-target ls -la
stop-target

After you run the on-target command does it timeout or display a list of files? After you increase the timeout number, does the connection still timeout when you repeat the above commands? If you add -v to the ssh command in libexec/on-target such that it now looks something like ssh -v -oConnectTimeout..., what is the output when you repeat the above commands? There should be a lot of debugging output because of the -v. Is there any new error message?

[hamundnic]

hello i have this error too:

`sudo bin/gbuild --commit learncoin=HEAD ../learncoin/contrib/gitian-descriptors/gitian-win32.yml

remote: Repository not found.
fatal: repository 'https://github.com/sheetgold-project/sheetgold.git/' not found
bin/gbuild:21:in system!': failed to run cd inputs/sheetgold && git fetch --update-head-ok https://github.com/sheetgold-project/sheetgold.git +refs/tags/*:refs/tags/* +refs/heads/*:refs/heads/* (RuntimeError) from bin/gbuild:268:in block in

'
from bin/gbuild:256:in each' from bin/gbuild:256:in '
`
and i have not idea how to fix it

[ivan-cbqa]

were any of you able to solve this issue? I have the same problem

apparently when I try to run the following command " service ssh status "
I get
"status: Unknown job: ssh"

Please help me to solve this :v

[hamundnic]

have you ssh installed ?

[BhumikaB]

sudo bin/gbuild inputs/lcoin/contrib/gitian-descriptors/deps-win32.yml

--- Building for precise amd64 ---
Stopping target if it is up
Connection timed out during banner exchange
Killing target since it did not shutdown within 10 seconds
Making a new image copy
Formatting 'target-precise-amd64.qcow2', fmt=qcow2 size=11811160064 backing_file=base-precise-amd64.qcow2 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
Starting target
Checking if target is up..............................
Connection timed out during banner exchange
bin/gbuild:21:in system!': failed to run on-target true (RuntimeError) from bin/gbuild:74:in build_one_configuration'
from bin/gbuild:309:in block (2 levels) in <main>' from bin/gbuild:304:in each'
from bin/gbuild:304:in block in <main>' from bin/gbuild:302:in each'
from bin/gbuild:302:in `

'

[ivan-cbqa]

thanks for the help! I don't even remember how I solved this but I did it :v

[BhumikaB]

I am not able to solve stuck for five days please help.......
sudo bin/gbuild inputs/lcoin/contrib/gitian-descriptors/deps-win32.yml

--- Building for precise amd64 ---
Stopping target if it is up
Making a new image copy
Formatting 'target-precise-amd64.qcow2', fmt=qcow2 size=11811160064 backing_file=base-precise-amd64.qcow2 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
Starting target
Checking if target is up..............................
OpenSSH_7.2p2 Ubuntu-4ubuntu2.6, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 2223.
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /home/softmac/gitian-builder/var/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/softmac/gitian-builder/var/id_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.6
Connection timed out during banner exchange
bin/gbuild:21:in system!': failed to run on-target true (RuntimeError) from bin/gbuild:74:in build_one_configuration'
from bin/gbuild:309:in block (2 levels) in <main>' from bin/gbuild:304:in each'
from bin/gbuild:304:in block in <main>' from bin/gbuild:302:in each'
from bin/gbuild:302:in `

'

[ivan-cbqa]

I ran into the same problem. It got solved by deleting and remaking the vm-base
make sure your gitian descriptor is compatible with the distribution you use to run linux. I used lxc to make the base.

I am attaching a guide you can use
Cross Compile Xoat_ Linux Wallet using Gitian Builder, Qt5.docx

[BhumikaB]

Thanks a lot, it helps...