After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762951 - GIMP 2.8.16 permissions incorrect
GIMP 2.8.16 permissions incorrect
Status: RESOLVED DUPLICATE of bug 759684
Product: GIMP
Classification: Other
Component: General
2.8.16
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2016-03-01 20:33 UTC by Matthew Riley
Modified: 2016-03-01 22:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew Riley 2016-03-01 20:33:31 UTC 
The currently published version of GIMP (at http://www.gimp.org/downloads/) has incorrect permissions set on the GIMP binary.

In general this won't cause issues for users manually copying the application bundle. However, when deploying via something like munki the lack of group execute causes issues.


GIMP pulled from http://download.gimp.org/mirror/pub/gimp/v2.8/osx/gimp-2.8.16-x86_64.dmg

md5 gimp-2.8.16-x86_64.dmg
MD5 (gimp-2.8.16-x86_64.dmg) = 58e9843cbfd99eb07bf5204cfd9d913f

Note the lack of group/everyone execute:
ls -la /Volumes/GIMP\ 2.8.16/GIMP.app/Contents/MacOS/ |awk '{ print $1,$9 }'
total
drwxr-xr-x .
drwxr-xr-x ..
-rwxr--r-- GIMP
-rwxr-xr-x GIMP-bin
-rwxr-xr-x python


Looking back at the 2.8.14 dmg this was set properly:
ls -la /Volumes/Gimp-2.8.14/GIMP.app/Contents/MacOS/ |awk '{ print $1,$9 }'
total
drwxr-xr-x@ .
drwxr-xr-x@ ..
-rwxr-xr-x@ GIMP
-rwxr-xr-x@ GIMP-bin
-rwxr-xr-x@ python

This is fairly trivial to fix in munki with a postinstall script but should probably be corrected moving forward.
Comment 1 Michael Schumacher 2016-03-01 22:25:31 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 759684 ***