Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7947 - lighttpd changed my permissions on /

Attached to Project: Arch Linux
Opened by Adam Štrauch (Cx) - Monday, 03 September 2007, 09:20 GMT-4
Last edited by Pierre Schmitz (Pierre) - Tuesday, 04 September 2007, 09:47 GMT-4
Task Type Bug Report
Category Packages: Extra
Status Unconfirmed
Assigned To Tobias Kieslich (tobias)
Operating System All
Severity Critical
Priority Normal
Reported Version 2007.08 Don't Panic
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No

Details

Hallo

After upgrade my system today i lost every permissions on my / :( Lighttpd contains script for changing permissions on document-root and temporarily i set it on / and i did't know about it :( Is it really necessary to change permissions on package which is just upgrated?

P.S. Sorry for my english.
This task depends upon

Comment by Pierre Schmitz (Pierre) - Tuesday, 04 September 2007, 09:47 GMT-4
Using / as document root is a very bad idea anyway. So I don`t think this is a packaging issue.
Comment by Adam Štrauch (Cx) - Tuesday, 04 September 2007, 10:05 GMT-4
Yes, it is, i shame :( I hadn't it on my eyes, i use simple vhost and document-root not. But the package change owner in running system, it is not good. If i set owner for my files, then set document-root to this files so after upgrade it will not be my files.
Comment by Georg Grabler (STiAT) - Friday, 14 September 2007, 03:22 GMT-4
In my opinion, the install script should be able to handle any document root given.

Also, adam, please attach the patch you created for this issue (as we talked on jabber lately), so we can have a look at it.

Thanks,
Georg
Comment by Georg Grabler (STiAT) - Friday, 14 September 2007, 03:47 GMT-4
Hmh, i'm just thinking about if it's the "best choice" anyway to fetch the data out of the configuration, or just leave it as it is. I wouldn't like of any of those scripts updates my files, which might be considered for a different use.
Comment by Dan McGee (toofishes) - Wednesday, 09 January 2008, 13:46 GMT-4
Updating files seems like a bad idea...I would highly recommend the install script didn't do this. The user really can figure out how to configure it, no?
Comment by Adam Štrauch (Cx) - Thursday, 10 January 2008, 05:53 GMT-4
Yes... may be i would kill upgrade script (same as install).
Comment by Mark Taylor (skymt) - Saturday, 03 May 2008, 18:31 GMT-4
I did a little refactoring to lighttpd.install. The warning message is now in a separate function, removing the need to call post_install from post_upgrade. Now the permissions changes are only applied on install. If the user changes document-root and forgets to fix the permissions, it's his own fault. ;)
   lighttpd.install (2.8 KiB)
Comment by Mark Taylor (skymt) - Saturday, 03 May 2008, 18:33 GMT-4
Uh, use this one instead. I missed a bracket in the first.
   lighttpd.install (2.8 KiB)

Loading...