xwmario / rutorrent

Automatically exported from code.google.com/p/rutorrent
0 stars 0 forks source link

User dont have write permissions to files in tar ball #870

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. download rutorrent-3.6.tar.gz
2. unpack 
3. user don't have write access to files

What is the expected output? What do you see instead?

user/owner should have write permissions on files
user/owner don't have write permissions on files

this is not good!!

What environment are you using?
1. My ruTorrent version is 3.6
2. My rTorrent version is 0.9.3
3. I use web-server... it version is... on OS...
4. I use browser... it version is... on OS...

Are some errors present in the web-server log?

Are some errors present in the browser error console?

Please provide any additional information below.

I cant patch the config.php file from my install script and cant sed files.

Original issue reported on code.google.com by daniel.f...@gmail.com on 3 Nov 2013 at 9:43

GoogleCodeExporter commented 8 years ago
This is a normal.

>I cant patch the config.php file from my install script and cant sed files.

If you can't change permission of the file than you don't need to edit it.

Original comment by novik65 on 4 Nov 2013 at 6:28

GoogleCodeExporter commented 8 years ago

user/owner should always have write access to distributed files in My opinion.

I use your fantastic rutorrent web-ui in my OpenELEC service addon rTorrent 
here: 
https://github.com/OpenELEC/unofficial-addons/tree/master/addons/service/downloa
dmanager/rTorrent

This change makes the builds fail!!

Of course I could ask the OpeneELEC theme to add the ability to chmod after 
unpack in there build scripts but I don't think they will. 

Nothing else is packed like this.

please consider changing the packaging?

Original comment by daniel.f...@gmail.com on 4 Nov 2013 at 11:58

GoogleCodeExporter commented 8 years ago
This is a not so easy on BinTray. For this i must to remove the version 
entirely and create new one. With losing statistics etc. I will think about 
that.

Original comment by novik65 on 4 Nov 2013 at 1:19