benlau / qtci

Collection of scripts to build Qt application in command line environment
Apache License 2.0
164 stars 54 forks source link

Installer stops after Welcome page #35

Open manang opened 4 years ago

manang commented 4 years ago

Hi, I'm trying to install qt 5.13.2 and the installer stops after the Welcome page:

 Installing Qt
/dev/disk3              GUID_partition_scheme
/dev/disk3s1            EFI
/dev/disk3s2            Apple_HFS                       /Volumes/qt-opensource-mac-x64-5.13.2 1
[806] QTCI:  Welcome Page

The problems started yesterday. Do you have a workaround?

manang commented 4 years ago

the login and password have to be set. it is impossible to install the qt environment without them.

magnesj commented 4 years ago

Same happened to me.

Here is the travis file causing hang https://github.com/OPM/ResInsight/blob/8c9b3085cf6e3f5a394a8b7b30780ae025efe974/.travis.yml

manang commented 4 years ago

you have to put the user and password i.e. export QT_CI_LOGIN=qt_user export QT_CI_PASSWORD=qt_password

robbel commented 4 years ago

It is possible to set the proxies manually to some arbitrary, invalid value (on the installer's Settings page). The installer will then fail the network connection and proceed directly to the install. Is it possible to automate that in the script so that the install will still go through? (Note: this is pertaining to the qtcreator installer but I assume it is similar for the Qt one).

kneirinck commented 4 years ago

It is possible to set the proxies manually to some arbitrary, invalid value (on the installer's Settings page). The installer will then fail the network connection and proceed directly to the install. Is it possible to automate that in the script so that the install will still go through? (Note: this is pertaining to the qtcreator installer but I assume it is similar for the Qt one).

I can confirm that setting the environment variable http_proxy to something invalid does as you say and drops the requirement of the qt account for an offline install export http_proxy=invalid

Thanks for the suggestion!