-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse -
Thanks for the changes. I managed to get the 3.0.4 site up. Not as concerned about the directories I can't access (rw) - they're extra and not referenced (at least not 3.0.3), so having them there doesn't hurt. (just cruft left over). I'm still trying to figure out a 'good' way to be able to update without modifying both 3 and 4 but am kind of pointing that to 3.0.5 timeframe. For now, it works. Thanks again. Brian Jesse Kuhnert wrote: > Hey Brian, > > It's not a complete fix yet (I don't have enough perms to do it), but I did > the following to the /www/jakarta.apache.org/tapestry directory: > > chmod -R g+rw ./tapestry > chgrp -R tapestry ./tapestry > > The only directories you won't be able to write to are the 3.0.3 and > outdated subdirectories. (I can't write to them either). The overall group > owner is now tapestry though, so you should be able to create a new > subdirectory called simply "3.0" or whatever you like, and link in the right > things as you see fit to the core documentation. > > Let me know if this doesn't fix things and we can try a few more commands. > > jesse -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEQrZCaCoPKRow/gARAkqKAJ4ujOxYD0CHtul/SQDMpcxX9ckGywCeNQBc WwfcIVx7Z3DfXt2NbB2ivCo= =Hhh9 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
