[SailfishDevel] After April SDK Update Existing App fails on RPM deploy to Jolla Device: Possible rights problem
juha.kallioinen at jolla.com
Wed Apr 16 14:24:24 UTC 2014
On 16.04.2014 16:19, christopher.lamb at thurweb.ch wrote:
> Zitat von "Juha Kallioinen" <juha.kallioinen at jolla.com>:
> Hi Juha
> On my host the access permissions were
> total 72
> drwxr-xr-x 7 christopherlamb staff 238B 22 Feb 22:01 .
> drwxr-xr-x 9 christopherlamb staff 306B 8 Feb 19:57 ..
> -rw-r--r-- 1 christopherlamb staff 4,1K 22 Feb 22:01 jsonpath.js
> -rw------- 1 christopherlamb staff 349B 8 Nov 15:56 landed.js
> -rw------- 1 christopherlamb staff 1,1K 11 Feb 19:33 message.js
> -rwxrwxrwx 1 christopherlamb staff 9,4K 22 Feb 19:47 readDataModel.js
> -rw-r--r-- 1 christopherlamb staff 5,2K 8 Feb 17:29
> I am not sure why the files on my host have such wildly different
> permissions. This probably reflects the different ages / sources of
> the files. Until now the permissions set on the host was not an issue
> I had to think about.
> I have now done a chmod 777 *.js
> That got me a little further, it next complained about missing qml
> files, so we have a similar issue with the permissions of .qml files.
> Having gone through all my qml file in the project on my host with
> chmod 755 *.qml the project now deploys successfully to the device.
> So it looks like, that (at least on OSX) the permissions of files on
> the host are important and need to be set correctly as expected on the
> end device. Something for the known issues page?
Ok glad it was this issue. You can do permission management for RPM
packages in the yaml/spec file %files section using the %attr and
%defattr directives. Here's more information about those directives:
More information about the Devel