Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
6.6.2
-
None
Description
I found something else that (frustratingly) just cost me an entire morning.
I have been working on all this in an attempt to learn how to build Boot2Qt for beaglebone, raspberry pi, and other platforms.
I followed the directions at https://doc.qt.io/Boot2Qt/b2qt-how-to-create-b2qt-image.html ...
The command "repo init -u https://code.qt.io/yocto/boot2qt-manifest -m v6.6.2.xml" kept choking.
fatal: unable to connect to code.qt.io:
code.qt.io[0: 54.247.17.180]: errno=Connection timed out
manifests: sleeping 4.0 seconds before retrying
fatal: cannot obtain manifest git://code.qt.io/yocto/boot2qt-manifest
================================================================================
Repo command failed: UpdateManifestError
Unable to sync manifest v6.6.2.xml
One of our network guys helped me track it down to port 9418 being denied by our firewall. I looked into it further and port 9418 seems to have been somewhat deprecated and many firewalls are likely to block it.
I did find a Qt Bug Report at https://bugreports.qt.io/browse/QTBUG-97939 that says in the comments:
- Workaround is to stop using the meta-boot2qt repository sources from the online installer and instead use the boot2qt-manifests repository as documented: https://doc.qt.io/QtForDeviceCreation/b2qt-customization-requirements.html#initializing-yocto-build-environment
- "All the manifests have been adjusted to use https protocol."
Those directions lead you to https://doc.qt.io/Boot2Qt/b2qt-how-to-create-b2qt-image.html which is what I was following and they say:
cd <BuildDir>
repo init -u git://code.qt.io/yocto/boot2qt-manifest -m <manifest>
repo sync
So, I finally ended up trying the https protocol instead of the git protocol "repo init -u https://code.qt.io/yocto/boot2qt-manifest -m v6.6.2.xml"
and it worked.
SO , someone fixed the problem, but not the documentation.