Community
cancel
Showing results for 
Search instead for 
Did you mean: 
TMalh
Novice
1,587 Views

Paho MQTT repository not found

Dear All,

I am trying to build an intel edison image using bitbake, but I am getting this error:

fatal: repository 'http://git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.c.git/ http://git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.c.git/' not found

while doing:

~/edison-src/out/linux64/poky/meta-intel-iot-middleware/recipes-connectivity/paho-mqtt/paho-mqtt_3.1.bb, do_fetch

13 Replies
idata
Community Manager
240 Views

Hi,

 

 

What BSP are you using? The recommended BSP is the latest one found here http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonbsp_ug_331188007.pdf .

 

 

To include Paho-MQTT you have to follow the steps from Section 4 and use IMAGE_INSTALL += "" but the reason why you're getting a repository not found is because paho-mqtt is not in http://recipes.yoctoproject.org/rrs/recipes/2.1/M4/ http://recipes.yoctoproject.org/rrs/recipes/2.1/M4/ . In this case you'd have to follow Section 4.3 specifically to add the Paho-MQTT package. Have you already followed this section?

 

 

Sergio

 

TMalh
Novice
240 Views

Dear Sergio,

Thank you!

I have followed section 2 of such document ("Build an Intel® Edison Image using bitbake"). Since I was not able to download the zip from step 2, I have found the edison-src-ww25.5-15.tgz (should it be?).

During the bitbake of edison-image, do_fetch of Paho-MQTT was failing with repository not found.

I did not followed section 4, because such package was already included... Not that I need it, it just is in the recipes...

Having further searched for the problem, I noticed that eclipse web site does not host the C client of such package.

I have then replaced the SRC_URI in the file ~/edison-src/out/linux64/poky/meta-intel-iot-middleware/recipes-connectivity/paho-mqtt/paho-mqtt_3.1.bb to https://github.com/eclipse/paho.mqtt.c.git githttps://github.com/eclipse/paho.mqtt.c.git ://github.com/eclipse/paho.mqtt.c.git

It was able to fetch, I just do not know if this is the proper solution, or if it is compatible.

Best,

Tiago

idata
Community Manager
240 Views

Have you had any issues using Paho MQTT after fetching using this method? As I said, the recommended method for adding third party packages is following the steps from section 4.3. If you see any issues with the paho MQTT installation, please report back to us.

 

 

Sergio

 

TMalh
Novice
240 Views

Dear Sergio,

After fetching Paho MQTT I had no issues in compiling or building and flashing the image in Edison.

I must mention, though, that I do not use Paho MQTT, and thus I have not tested it to see if it is working properly.

I understand that section 4.3 should be followed to include third party packages, but I did not added it myself. I have downloaded the BSP document mentioned previously and have only followed section 2. So I imagine that either I was doing something wrong, or MQTT is already included in either BSP or yocto recipes.

Thank you,

Best,

Tiago

xyina
Novice
240 Views

TMalh
Novice
240 Views

Dear Yinan,

Yes!, thank you. As mentioned previously, that fixes the fetching problem!

Best,

Tiago

mgiun
New Contributor I
240 Views

Tiago, did you build 2.1 or 3.0 ?

TMalh
Novice
240 Views

I am using the edison-src-ww25.5-15.tgz bsp, I assume it is 2.1.

mgiun
New Contributor I
240 Views

thks Tiago,

the problem i found is in edison-GPL_LGPL-sources-ww18-15.zip , which is the 2.1 :-(

another problem, another delay...

I'm starting to doubt about continuing develop on this board

TMalh
Novice
240 Views

Have you changed from https to git? from your previous output you have https://github.com https://github.com but it should be git://

Another thing, it could be that the specific source revision could not be found, but I have tried on my and the output error is different and clearly states that was not able to find the source revision.

In my bb file, it is SRCREV = "93a064dbe9fd2fc84b8bb2701e10d2de8004a11c".

So, I think you need to change the SRC_URI to:

SRC_URI = "git://github.com/eclipse/paho.mqtt.c.git;protocol=http \

file://makefile.patch \

"

Best,

Tiago

VVorn
New Contributor II
240 Views

Problem persists in 3.5 but the proposed solution of this thread helps

mgiun
New Contributor I
240 Views

I had this problem too.

I was building : bitbake edison-image -c populate_sdk

I modify ~/edison-src/out/linux64/poky/meta-intel-iot-middleware/recipes-connectivity/paho-mqtt/paho-mqtt_3.1.bb, in the way indicated

with 'http://git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.c.git/ http://git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.c.git/ replaced by https://github.com/eclipse/paho.mqtt.c.git https://github.com/eclipse/paho.mqtt.c.git

 

but... this did not solve the problem.

 

the building fails again BUT controlling the MD5 of the new files :

ERROR: No checksum specified for /home/mgiuncato/edison_new_img_v2.1/bitbake_download_dir/paho.mqtt.c.git, please add at least one to the recipe:

SRC_URI[md5sum] = "5787188a9e3c6bb7f5442a14189cf5df"

SRC_URI[sha256sum] = "4fac9fc606844b12265b562c52496b374ddfe97e79d017a80662b84891136deb"

ERROR: Function failed: Fetcher failure for URL: 'https://github.com/eclipse/paho.mqtt.c.git;protocol=https https://github.com/eclipse/paho.mqtt.c.git;protocol=https'. Missing SRC_URI checksum

ERROR: Logfile of failure stored in: /home/mgiuncato/edison_new_img_v2.1/edison-src/build/tmp/work/core2-32-poky-linux/paho-mqtt/3.1-r1/temp/log.do_fetch.15142

ERROR: Task 753 (/home/mgiuncato/edison_new_img_v2.1/edison-src/poky/meta-intel-iot-middleware/recipes-connectivity/paho-mqtt/paho-mqtt_3.1.bb, do_fetch) failed with exit code '1'

Î am still blocked in this issue.

TMalh
Novice
240 Views

mgiuncato,

my exact line is:

SRC_URI = "git://github.com/eclipse/paho.mqtt.c.git;protocol=http \

file://makefile.patch \

"

It seems that using https instead of git it fails.. So, see that it is git:// and protocol is specified as http and not https.

best,

Tiago

Reply