Bug 133971 - enemy-territory-fortress-1.6-r1 installs some files with executable permissions
Bug#: 133971 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: games@gentoo.org Reported By: denilsonsa@gmail.com
Component: Games
URL: 
Summary: enemy-territory-fortress-1.6-r1 installs some files with executable permissions
Keywords:  
Status Whiteboard: 
Opened: 2006-05-21 11:50 0000
Description:   Opened: 2006-05-21 11:50 0000
Lots of .pk3 files, as well as some .cfg and .dat, are installed with
executable bit set, even though they are not executable. I'm not sure if .so
files should be executable or not.

$ ls -lhF /opt/enemy-territory/etf/
total 266M
-rwxr-x--- 1 root games  717 May 20 22:16 ChangeLog*
-rw-r----- 1 root games 7.7K May 20 22:16 LICENSE
-rw-r----- 1 root games  11K May 20 22:16 README
-rw-r----- 1 root games 7.2K May 20 22:16 README.etf
drwxr-x--- 2 root games 4.0K May 20 22:18 adv_srv_conf/
drwxr-x--- 2 root games 4.0K May 20 22:18 advanced server configs/
-rwxr-x--- 1 root games   10 May 20 22:16 autoexec.cfg*
-rwxr-x--- 1 root games 762K May 20 22:16 cgame.mp.i386.so*
drwxr-x--- 2 root games 4.0K May 20 22:17 classconfigs/
drwxr-x--- 6 root games 4.0K May 20 22:17 docs/
-rw-r----- 1 root games  27K May 20 22:16 enemy-territory.xml
-rw-r----- 1 root games 5.0K May 20 22:16 etf.xpm
-rwxr-x--- 1 root games 2.5M May 20 22:16 etf_border.pk3*
-rwxr-x--- 1 root games 4.2M May 20 22:16 etf_bringit.pk3*
-rwxr-x--- 1 root games 6.1M May 20 22:16 etf_dissect.pk3*
-rwxr-x--- 1 root games 203M May 20 22:16 etf_pak0.pk3*
-rwxr-x--- 1 root games  22M May 20 22:16 etf_pak1.pk3*
-rwxr-x--- 1 root games 1.3K May 20 22:16 etf_pak2.28249d08.pk3*
-rwxr-x--- 1 root games 1.3K May 20 22:16 etf_pak2.pk3*
-rwxr-x--- 1 root games  18M May 20 22:16 etf_pak3.pk3*
-rwxr-x--- 1 root games 1.7M May 20 22:16 etf_pak4.pk3*
-rwxr-x--- 1 root games  84K May 20 22:16 etf_pak5.pk3*
-rwxr-x--- 1 root games 5.9K May 20 22:16 etf_server.cfg*
-rwxr-x--- 1 root games 5.3M May 20 22:16 etf_smartbases2.pk3*
-rwxr-x--- 1 root games 7.2K May 20 22:16 history.txt*
-rwxr-x--- 1 root games 879K May 20 22:16 mp_bin.pk3*
drwxr-x--- 2 root games 4.0K May 20 22:18 nav/
-rw-r----- 1 root games 1.9M May 20 22:16 omnibot_etf.so
-rwxr-x--- 1 root games    0 May 20 22:16 preset_normal.cfg*
-rwxr-x--- 1 root games 593K May 20 22:16 qagame.mp.i386.so*
-rwxr-x--- 1 root games 6.0K May 20 22:16 sample_server.cfg*
drwxr-x--- 2 root games 4.0K May 20 22:17 sample_srv/
drwxr-x--- 2 root games 4.0K May 20 22:17 scripts/
-rwxr-x--- 1 root games 460K May 20 22:16 servercache.dat*
drwxr-x--- 3 root games 4.0K May 20 22:17 ui/
-rwxr-x--- 1 root games 342K May 20 22:16 ui.mp.i386.so*
-rwxr-x--- 1 root games 1.3K May 20 22:16 uninstall*
drwxr-x--- 2 root games 4.0K May 20 22:17 video/

------- Comment #1 From Chris Gianelloni (RETIRED) 2006-09-29 07:34:35 0000 -------
I believe that I fixed this in the eclass now.

------- Comment #2 From Denilson 2006-09-29 09:20:40 0000 -------
I've just resynched and reemerged it, and I can confirm the bug is not fixed
yet.

------- Comment #3 From SpanKY 2006-09-29 21:53:02 0000 -------
verified how ?  re-emerging ?  that wont update the permissions

`emerge -C` the package first, make the files are gone, and then try
re-emerging

------- Comment #4 From Denilson 2006-09-30 07:46:28 0000 -------
(In reply to comment #3)
> verified how ?  re-emerging ?  that wont update the permissions
> 
> `emerge -C` the package first, make the files are gone, and then try
> re-emerging

Hum... Portage should update permissions without need of unmerging the package
first.

Anyway, I did this:
# eix-sync -v ; emerge -C enemy-territory-fortress ; emerge
enemy-territory-fortress
And I still see lots of files with +x permission.

------- Comment #5 From SpanKY 2006-09-30 12:11:24 0000 -------
the portage permission topic is a bigger issue ... we'll cover the specific
problem here

------- Comment #6 From Mr. Bones. 2006-10-02 00:27:59 0000 -------
Should be fixed up now.