Hi Juha
I am now on the train. Deployment also works with WiFi active, but not
properly connected.
This means that - at least in my case - adding SailfishSDK to the
/etc/hosts is a good fix for this error.
I think this is one for the Known Issues page.
I guess that (without the entry in /etc/hosts) active networking is
required for "SailfishSDK" to be resolved. Of course I could SSH in,
because I was using localhost as the machine name to connect (ssh -p
2222 -i ~/SailfishOS/vmshare/ssh/private_keys/engine/root root@localhost).
Thanks for your help and forebearance,
Chris
On 03.06.14 17:15, Christopher Lamb wrote:
Hi Juha
I have edited my /etc/hosts to look like this:
127.0.0.1 localhost SailfishSDK
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
Now in the office, with WIFI turned off, and no ethernet plugged in, I
can deploy as RPM successfully! So for the moment it looks like
editing the /etc/hosts may be enough.
Later this evening on train on the way home I will try with WiFi
activated but no proper connection (which means it will probably
default to the SBB/Swisscom WiFi which requires a logon to properly
connect).
Thanks
Chris
On 03.06.14 11:24, Juha Kallioinen wrote:
Hi Christopher,
the changing networks may play a part in this problem. Did I already
sometime earlier ask you to modify your Mac's /etc/hosts file?
It has helped in some cases to add the name for the MerSDK virtual
machine to /etc/hosts like this:
127.0.0.1 SailfishSDK
Or if you already have the 127.0.0.1 there, just add the SailfishSDK
to the end of the existing line like this:
127.0.0.1 localhost.localdomain localhost SailfishSDK
Could you try this and let me know if there's any improvement? ....
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
