Mailing List Archive

Stas Bekman wrote:
> Philippe, I've noticed that the docs weren't being updated. I see you've
> changed the cron but why didn't you tell that the whole thing is down?
>
> #MAILTO=docs-dev@perl.apache.org
>
> # Temporarly send to myself, don't want to spam the list until the
> # svn issues are resolved
>
> MAILTO=gozer@apache.org
>
> # every monday rebuild all, including pdf
> 30 03 * * 1
> /home/perlwww/apache.org/modperl-docs/bin/site_build_force_pdf_index
> # update all (only changes/no pdf) every 6 hours
> 15 6,12,18 * * * /home/perlwww/apache.org/modperl-docs/bin/site_build_index
> # update all (only changes and pdfs) once a day
> 15 0 * * * /home/perlwww/apache.org/modperl-docs/bin/site_build_pdf_index

looks like the repository was borked:

% cd /home/perlwww/apache.org/modperl-docs
% svn up
svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
% svn cleanup
% svn up
U src/docs/2.0/api/Apache/PerlSections.pod
U src/docs/2.0/user/handlers/filters.pod
U src/docs/2.0/user/config/config.pod
U src/docs/2.0/user/config/custom.pod
U src/download/index_top.html
Updated to revision 122936.

So what remains to be fixed?

In the future please log this kind of issues in the todo file, so others
know what's happening. Thanks.


--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org

Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>> Stas Bekman wrote:
>>
>>> Philippe, I've noticed that the docs weren't being updated. I see
>>> you've changed the cron but why didn't you tell that the whole thing
>>> is down?
>
>
> I've only changed the MAILTO address so that _if_ problems showed up after
> having moved the doc building to svn, I'd be bothered, and nobody else.

[...]

> That's it and I am not quite sure what caused that lockup to happen in the
> first place. Might be a safe thing to add 'svn cleanup' to the part of the
> build that 'svn update' just in case this happens again.

And you didn't receive any problem report on this one?

>> In the future please log this kind of issues in the todo file, so
>> others know what's happening. Thanks.
>
>
> Will do in the future. I've just removed my email address from there, so
> now
> problems do go once again to docs-dev@perl.apache.org

Cool.

--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org

Stas Bekman wrote:
> Stas Bekman wrote:
>
>>Philippe, I've noticed that the docs weren't being updated. I see you've
>>changed the cron but why didn't you tell that the whole thing is down?

I've only changed the MAILTO address so that _if_ problems showed up after
having moved the doc building to svn, I'd be bothered, and nobody else.

> [...]
> looks like the repository was borked:
>
> % cd /home/perlwww/apache.org/modperl-docs
> % svn up
> svn: Working copy '.' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
> % svn cleanup
> % svn up
> U src/docs/2.0/api/Apache/PerlSections.pod
> U src/docs/2.0/user/handlers/filters.pod
> U src/docs/2.0/user/config/config.pod
> U src/docs/2.0/user/config/custom.pod
> U src/download/index_top.html
> Updated to revision 122936.
>
> So what remains to be fixed?

That's it and I am not quite sure what caused that lockup to happen in the
first place. Might be a safe thing to add 'svn cleanup' to the part of the
build that 'svn update' just in case this happens again.

> In the future please log this kind of issues in the todo file, so others
> know what's happening. Thanks.

Will do in the future. I've just removed my email address from there, so now
problems do go once again to docs-dev@perl.apache.org

--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5