I would like to build intel aero image to include mono, but already I can't to build the original image.
I'm following you quickstart guide, but when I start this command:
bitbake intel-aero-image, I have an error with pymavlink:
WARNING: pymavlink-2.0.6-r0 do_fetch: Failed to fetch URL https://pypi.python.org/packages/ae/d3/2bcc417b127e7230b67cb65ecb7b3865af8d7ea2f7f458c203facbe961eb/..., attempting MIRRORS if available
ERROR: pymavlink-2.0.6-r0 do_fetch: Fetcher failure: Fetch command failed with exit code 8, output:
2017-03-02 17:57:21 ERROR 404: Not Found.
ERROR: pymavlink-2.0.6-r0 do_fetch: Function failed: Fetcher failure for URL: ' https://pypi.python.org/packages/ae/d3/2bcc417b127e7230b67cb65ecb7b3865af8d7ea2f7f458c203facbe961eb/...'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /opt/intel_aero/poky/build/tmp/work/core2-64-poky-linux/pymavlink/2.0.6-r0/temp/log.do_fetch.30706
ERROR: Task 3840 (/opt/intel_aero/poky/meta-uav/recipes-mavlink/mavlink/pymavlink_2.0.6.bb, do_fetch) failed with exit code '1'
Can you help me?
Thanks for your interest in the Intel® Aero Platform for UAVs.
Let us investigate this error, we will get back to you as soon as we have some useful information.
Have a great day!
This was fixed with https://github.com/intel-aero/intel-aero-manifest/commit/69c1837f18a3b46dbfeca1bfa46a9f801d33fdc7 Fix the build break with pymavlink · intel-aero/intel-aero-manifest@69c1837 · GitHub
First, we will like to thank you for reporting this error!
Now, like vilvo stated this error has been fixed. You can attempt to rebuild the image by syncing to the repo, here are the official fixes:
-https://github.com/intel-aero/meta-uav/commit/0f9395139b6a3c3f0f2c18a6a87f4048d0ca1a4f Changing sources for pymavlink · intel-aero/meta-uav@0f93951 · GitHub
- https://github.com/intel-aero/meta-intel-aero/commit/5c631a7faf9c07122207825c76dd5ebf5a240d74 mavlink-router: Fix python usage on recipe... · intel-aero/meta-intel-aero@5c631a7 · GitHub
Please let us know if any questions come up, have a great day!
Thanks, the pymavlink are correct, but I'm now this error:
ERROR: rosunit-1.11.13-r0 do_fetch: Fetcher failure: Fetch command failed with exit code 8, output:
2017-03-09 17:33:39 ERROR 500: Internal Server Error.
ERROR: rosunit-1.11.13-r0 do_fetch: Function failed: Fetcher failure for URL: ' https://github.com/ros/ros/archive/1.11.13.tar.gz;downloadfilename=ros-1.11.13.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /opt/intel_aero/poky/build/tmp/work/core2-64-poky-linux/rosunit/1.11.13-r0/temp/log.do_fetch.29876
ERROR: Task 4076 (/opt/intel_aero/poky/meta-ros/recipes-ros/ros/rosunit_1.11.13.bb, do_fetch) failed with exit code '1'
I'm testing this url in browser, and I'm the same error. I'll restart later if it's just a server problem.
That's exactly right course of action with yocto build. Retry.
Some of these "unable to fetch" errors happen due to a few reasons:
If you want to benefit from the latest, sometimes experimental and not validated packages in Intel Aero it's good to understand the nature of the yocto build system.
Intel Aero with all the yocto layers is 8049 build tasks and some of them are following the latest versions of upstream packages, not fixed versions. Unless you provide full details from bitbake debug, it's not possible to tell what is the reason for your build to fail. If many users encounter the same, we work to fix it with some delay but of course pull requests are appreciated even more.
To give you an idea on the complexity of the build, I just started a clean build with full bitbake debug - http://ec2-52-59-242-235.eu-central-1.compute.amazonaws.com:8080/job/aero-build-release/6/console aero-build-release # 6 Console [Jenkins] - please have a look.
I'll configure some scheduled builds next week so it would be easy to check how the build looks in AWS cloud instance which has great connection to the Internet. That way we can all see continuous feedback - the state of the Aero build.
Anyway, I propose we close this because the original issue was fixed and let's follow-up broken packages (consistently broken between trials or many users see the issue) in the github https://github.com/intel-aero/meta-intel-aero/issues Issues · intel-aero/meta-intel-aero · GitHub
As a final note, feel free to start new discussion topics to learn if other users are encountering the same issue with a package you encounter.