We have moved to a new Sailfish OS Forum. Please start new discussions there.
0

deploying to jolla phone - problem with ssh or rsync [answered]

asked 2019-04-13 18:33:07 +0200

monkeywithkeyboard gravatar image

I have trouble deploying binary files and rpm to my jolla phone (sailfish v3.0.2.8).

ssh: connect to host 192.168.2.15 port 22: No route to host rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0] 15:26:59: The process "/home/uganda/.config/SailfishOS-SDK/mer-sdk-tools/Sailfish OS Build Engine/SailfishOS-3.0.2.8-armv7hl/deploy" exited with code 1. Error while building/deploying project harbour-test7 (kit: SailfishOS-3.0.2.8-armv7hl (in Sailfish OS Build Engine)) When executing step "RPM" 15:26:59: Elapsed time: 01:07.

I can manually deploy RPMs to the device using rsync (console). Thats working. But i want to deploy binary files to the device via Qt Creator. I dont want to use the emulator because the machine i am using is too weak to process the emulation in an acceptable manner.

It looks like a problem with ssh. But i also checked rsync. Rsync versions are 3.1.0 (sailfish) and 3.1.1 (ubuntu). As long as some internal script isnt deploying via rsync using the -zz option there shouldnt be a problem using this versions together. And using this option wouldnt make sense here because the rsync version on the device does not support it.

The device is added to devices at the qt creator ui. I am able to check the connection (positive) and i am also able to show the running processes.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by olf
close date 2019-04-14 00:37:43.512554

1 Answer

Sort by » oldest newest most voted
1

answered 2019-04-13 21:27:43 +0200

monkeywithkeyboard gravatar image

Ok, i got it.

As you can see from my first post the build/deploy process needs 67 seconds (old machine).

I just changed the timeout under Options->Devices to 80 seconds and now it works.

Its a little odd to me that the ssh timeout starts before building the app because its just needed for deployment.

edit flag offensive delete publish link more

Question tools

Follow
2 followers

Stats

Asked: 2019-04-13 18:33:07 +0200

Seen: 422 times

Last updated: Apr 13 '19