Re: XML website status

2009-01-29 Thread Jeremias Maerki
Good point. If noone beats me to it, I'll touch up the Commons site in the next few days and see to it that I can become usable once more. A short test showed that there is something DocBook-related that might need a second glance and never Forrest versions have a problem with the sources. On 30.0

Re: XML website status

2009-01-29 Thread Michael Glavassevich
Jeremias Maerki wrote on 01/29/2009 04:24:52 PM: > With the permissions fixed, I've now made a little progress cleaning up > some more directories. Still some way to go but getting there... > > Next step is figuring out if there's really still a cron job for > updating the XML Commons website as

Re: XML website status

2009-01-29 Thread Jeremias Maerki
With the permissions fixed, I've now made a little progress cleaning up some more directories. Still some way to go but getting there... Next step is figuring out if there's really still a cron job for updating the XML Commons website as the readme says. I doubt it, but we'll see what happens now

Re: XML website status

2009-01-03 Thread Michael Glavassevich
Jeremias Maerki wrote on 01/01/2009 12:13:34 PM: > I've tried to update the XML website today but was quite unlucky. I > currently can't do a "svn up" to update the XML website because various > things are in the way: > - files and directories with bad permissions from "apbackup" > - Missing .svn

XML website status

2009-01-01 Thread Jeremias Maerki
I've tried to update the XML website today but was quite unlucky. I currently can't do a "svn up" to update the XML website because various things are in the way: - files and directories with bad permissions from "apbackup" - Missing .svn directories due to unclean website updates - .svn directorie