[SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread christopher . lamb
Hi All I have just installed the April SDK update, and have opened an existing app, and am trying to deploy to my Jolla. The app worked with the previous SDK release, and is already installed on the phone. If I deploy as Deploy by copying Binaries then thinks work as expected, and the

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread Andrey Kozhevnikov
IMHO you should manage file permissions yourself before deploying? 16.04.2014 18:39, christopher.l...@thurweb.ch пишет: Hi All I have just installed the April SDK update, and have opened an existing app, and am trying to deploy to my Jolla. The app worked with the previous SDK release, and

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread christopher . lamb
Hi Andrey Thanks for the fast answer Given that we are talking about cross-platform development - developing on one and deploying to another I am not sure that is always possible. What if my development host was Windows? And as a developer I want to worry about writing code, not all the

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread Luca Donaggio
This reminds me of SDK RPM-validator tool complaining about files with executable permission (it issued a warning about possible deprecation of executable files in RPM according to Harbour rules). If any sort of permission-scheme has to be enforced, shouldn't the SDK's RPM generator take care of

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread Juha Kallioinen
On 16.04.2014 15:39, christopher.l...@thurweb.ch wrote: Hi All ... I also get the white screen when trying to open the app. Via SSH on the jolla device I can find the file is present: [nemo@Jolla javascript]$ pwd /usr/share/landed26_QT5/qml/javascript [nemo@Jolla javascript]$ ls -ahl total

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread christopher . lamb
Zitat von Juha Kallioinen juha.kallioi...@jolla.com: Hi Juha On my host the access permissions were apple-pip:javascript christopherlamb$ cd /Users/christopherlamb/QTProjects/landed/landed26_QT5/landed26_QT5/qml/javascript apple-pip:javascript christopherlamb$ ls -ahl total 72 drwxr-xr-x

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread Mohammed Hassan
You don't need executable permission (x) for js files. Read bit is enough so the SDK is correct here. I noticed that the missing scripts do not have read permission set which is the problem. I have no idea how it happened though. Cheers, -- Sent from my Nokia N9On 16.4.2014 15:39

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread christopher . lamb
Hi Mohammed thanks The varied permission on the qml / js files on my host probably reflect that the project originated in pre-sailfish days, and thus the files have come from various sources / versions of Qt Creator / edited with different text editors etc. since then. I have now set

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread Juha Kallioinen
On 16.04.2014 16:19, christopher.l...@thurweb.ch wrote: Zitat von Juha Kallioinen juha.kallioi...@jolla.com: Hi Juha On my host the access permissions were apple-pip:javascript christopherlamb$ cd /Users/christopherlamb/QTProjects/landed/landed26_QT5/landed26_QT5/qml/javascript

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread Mohammed Hassan
On Wed, 16 Apr 2014 16:17:07 +0200 christopher.l...@thurweb.ch wrote: Hi Mohammed thanks The varied permission on the qml / js files on my host probably reflect that the project originated in pre-sailfish days, and thus the files have come from various sources / versions of Qt Creator

Re: [SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem

2014-04-16 Thread khertan
I got the exactly same surprise. Rights of file was readable only by root. My projects is placed on a foldr that is synced between many devices, os, and fs, (btsync on windows/fat32, linux ext4, ext3 on rasp, n9) ... and look like file attrb are badly set :) Regards À Wed Apr 16 2014