Re: [tlug] Permissions on local Apache web testing environment (and JavaScript file location problem) [SOLVED]

[Dave M G <dave@example.com>]

Edmund,

Thank you for responding.

> OK, I think I know what's going on here...
> Debian (so presumably Ubuntu too) has a package called javascript-common...
> In practice... it's completely psychotic.

You totally nailed it.

And I am so glad you told me because I don't know if I would have ever
figured that out. I have been searching Google endlessly without any hits.

Also, I agree completely with your analysis. The principle has an outer
appearance of sensibility, but I've already experienced that upgrading
libraries can sometimes break extensions based on previous versions. So
I'd much rather just take responsibility for downloading the right
libraries on a per-site basis.

And although I could rename my directories to "js" or something,
whenever possible, I want to be the person deciding my own naming
conventions.

I removed the javascript-common package. It must be a default option in
the LAMP configuration in Ubuntu Karmic - it was never an issue in
Jaunty. (I think I'm even going to suggest to the Ubuntu developers that
it not be the default, it should be an option specifically selected by
the user)

The end summary I think is that after upgrading to Karmic and restoring
from backup, initially the permissions were off. I reset them with the
commands I mentioned earlier in the thread, but it didn't take effect
until I rebooted - restarting Apache wasn't enough. Once that was done,
the secondary problem of this new javascript-common package came to light.

All done now, and it looks like I'm back on track.

Thanks so much to everyone for helping me through this. I learned a few
new pointers along the way.