You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Theo Van Dinter <fe...@apache.org> on 2007/01/27 18:26:22 UTC
Re: Output from "cron" command
Had to do a "svn cleanup . rulesrc" on ~release/versions/cvshead, then accept
the cert during "update". fyi.
On Sat, Jan 27, 2007 at 09:27:53AM +0000, release@spamassassin.zones.apache.org wrote:
> Your "cron" job on spamassassin.zones.apache.org
> $HOME/versions/cvshead/build/nightlymc/corpora_runs >> /home/corpus-rsync/corpus/weekly-versions.txt
>
> produced the following output:
>
> Error validating server certificate for 'https://svn.apache.org:443':
> - The certificate is not issued by a trusted authority. Use the
> fingerprint to validate the certificate manually!
> Certificate information:
> - Hostname: svn.apache.org
> - Valid: from Jan 26 14:18:55 2007 GMT until Jan 26 14:18:55 2009 GMT
> - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, Inc., Scottsdale, Arizona, US
> - Fingerprint: a7:a5:3f:1a:ae:bb:98:b2:f3:ec:91:1b:63:29:2d:e8:58:b6:53:28
> (R)eject, accept (t)emporarily or accept (p)ermanently? Abort - core dumped
> Problem doing svn update
--
Randomly Selected Tagline:
"The weaknesses and the strengths of computer networking derive from the same
feature: it is easy to send messages to anyone who has access to the
network." - Donald A. Norman, The Trouble with Networks (Datamation 1/1982)
Re: Output from "cron" command
Posted by Doc Schneider <ma...@maddoc.net>.
Theo Van Dinter wrote:
> On Sat, Jan 27, 2007 at 11:37:23AM -0600, Doc Schneider wrote:
>> I get an error trying to update the trunk
>>
>> [maddoc@lists sadev]$ svn up
>> https://svn.apache.org/repos/asf/spamassassin/trunk/ .
>> Skipped 'https://svn.apache.org/repos/asf/spamassassin/trunk'
>> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
>> svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
>> (https://svn.apache.org)
>
> Hrm. "Bad Request" is usually a bad proxy somewhere in between. I just
> did an update w/out issue fwiw.
>
Never mind ... I didn't cd deep enough and was trying to do it from the
wrong directory... going to be one of those days! [THUD]
--
-Doc
SA/SARE/URIBL/SURBL -- Ninja
12:08pm up 13 days, 21:06, 15 users, load average: 4.97, 4.69, 3.96
SARE HQ http://www.rulesemporium.com/
Re: Output from "cron" command
Posted by Theo Van Dinter <fe...@apache.org>.
On Sat, Jan 27, 2007 at 11:37:23AM -0600, Doc Schneider wrote:
> I get an error trying to update the trunk
>
> [maddoc@lists sadev]$ svn up
> https://svn.apache.org/repos/asf/spamassassin/trunk/ .
> Skipped 'https://svn.apache.org/repos/asf/spamassassin/trunk'
> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
> svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
> (https://svn.apache.org)
Hrm. "Bad Request" is usually a bad proxy somewhere in between. I just
did an update w/out issue fwiw.
--
Randomly Selected Tagline:
"Bank error in your favor. Collect $200."
Re: Output from "cron" command
Posted by Doc Schneider <ma...@maddoc.net>.
Theo Van Dinter wrote:
> Had to do a "svn cleanup . rulesrc" on ~release/versions/cvshead, then accept
> the cert during "update". fyi.
>
> On Sat, Jan 27, 2007 at 09:27:53AM +0000, release@spamassassin.zones.apache.org wrote:
>> Your "cron" job on spamassassin.zones.apache.org
>> $HOME/versions/cvshead/build/nightlymc/corpora_runs >> /home/corpus-rsync/corpus/weekly-versions.txt
>>
>> produced the following output:
>>
>> Error validating server certificate for 'https://svn.apache.org:443':
>> - The certificate is not issued by a trusted authority. Use the
>> fingerprint to validate the certificate manually!
>> Certificate information:
>> - Hostname: svn.apache.org
>> - Valid: from Jan 26 14:18:55 2007 GMT until Jan 26 14:18:55 2009 GMT
>> - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, Inc., Scottsdale, Arizona, US
>> - Fingerprint: a7:a5:3f:1a:ae:bb:98:b2:f3:ec:91:1b:63:29:2d:e8:58:b6:53:28
>> (R)eject, accept (t)emporarily or accept (p)ermanently? Abort - core dumped
>> Problem doing svn update
>
I get an error trying to update the trunk
[maddoc@lists sadev]$ svn up
https://svn.apache.org/repos/asf/spamassassin/trunk/ .
Skipped 'https://svn.apache.org/repos/asf/spamassassin/trunk'
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: REPORT of '/repos/asf/!svn/vcc/default': 400 Bad Request
(https://svn.apache.org)
--
-Doc
Penguins: Do it on the ice.
11:36am up 13 days, 20:34, 15 users, load average: 2.17, 2.51, 2.29
SARE HQ http://www.rulesemporium.com/