RE: problem on email notification hook

[Ul...@elektrobit.com]

Hi,
 
after upgrading mod_dav_svn, don't forget to restart Apache... ;-)
 
This happened to multiple people on this list before... ;-)
 
Ulli


________________________________

	From: fengbin [mailto:arithdon@gmail.com] 
	Sent: Tuesday, June 23, 2009 8:29 AM
	To: Ryan Schmidt
	Cc: users@subversion.tigris.org
	Subject: Re: problem on email notification hook
	
	
	Dear Ryan,
	Thank you for your warmly help.
	Yes ,you are right ,I am using http:// check out the files.
	I'll check how to upgrade mod_dav_svn..
	
	
	
	
	
	
	On Tue, Jun 23, 2009 at 1:42 PM, Ryan Schmidt
<su...@ryandesign.com> wrote:
	

		On Jun 23, 2009, at 00:34, fengbin wrote:
		
		

			What do you mean
			"repository was created with a newer version of
Subversion than the server that is now trying to read it"?
			The repository is created in the server ,right?
So there is another server to read the data created in svn server?
			


		If you ran "svnadmin create" using svnadmin from
Subversion 1.6.2, then the repository is in a format that only
Subversion 1.6.x and later can read ("format 5").
		
		So, by what URL protocol did you check out the
repository on the client -- http://, https://, svn://, svn+ssh://, or
file:///?
		
		If http:// or https://, then the version of mod_dav_svn
you are using in Apache on the server is too old (is older than 1.6.0)
and needs to be upgraded.
		
		If svn:// or svn+ssh://, then the version of svnserve
you are using on the server is too old.
		
		If file:///, then the version of svn on the client is
too old.
		
		In any case, if you just upgrade everything to
Subversion 1.6.x you should be able to access the repository no matter
what protocol you are using. And then we can see whether the email
configuration is working. But we need to get basic repository
functionality working first.
		
		
		






----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.

Re: problem on email notification hook

[fengbin <ar...@gmail.com>]

Thank you for your kindly reminder!!:-)

On Wed, Jul 1, 2009 at 3:46 PM, <Ul...@elektrobit.com> wrote:

>  Hi,
>
> after upgrading mod_dav_svn, don't forget to restart Apache... ;-)
>
> This happened to multiple people on this list before... ;-)
>
> Ulli
>
>  ------------------------------
> *From:* fengbin [mailto:arithdon@gmail.com]
> *Sent:* Tuesday, June 23, 2009 8:29 AM
> *To:* Ryan Schmidt
> *Cc:* users@subversion.tigris.org
> *Subject:* Re: problem on email notification hook
>
> Dear Ryan,
> Thank you for your warmly help.
> Yes ,you are right ,I am using http:// check out the files.
> I'll check how to upgrade mod_dav_svn..
>
>
>
>
>
> On Tue, Jun 23, 2009 at 1:42 PM, Ryan Schmidt <
> subversion-2009b@ryandesign.com> wrote:
>
>> On Jun 23, 2009, at 00:34, fengbin wrote:
>>
>> What do you mean
>>> "repository was created with a newer version of Subversion than the
>>> server that is now trying to read it"?
>>> The repository is created in the server ,right? So there is another
>>> server to read the data created in svn server?
>>>
>>
>> If you ran "svnadmin create" using svnadmin from Subversion 1.6.2, then
>> the repository is in a format that only Subversion 1.6.x and later can read
>> ("format 5").
>>
>> So, by what URL protocol did you check out the repository on the client --
>> http://, https://, svn://, svn+ssh://, or file:///?
>>
>> If http:// or https://, then the version of mod_dav_svn you are using in
>> Apache on the server is too old (is older than 1.6.0) and needs to be
>> upgraded.
>>
>> If svn:// or svn+ssh://, then the version of svnserve you are using on the
>> server is too old.
>>
>> If file:///, then the version of svn on the client is too old.
>>
>> In any case, if you just upgrade everything to Subversion 1.6.x you should
>> be able to access the repository no matter what protocol you are using. And
>> then we can see whether the email configuration is working. But we need to
>> get basic repository functionality working first.
>>
>>
>>
>
>
> ----------------------------------------------------------------
> Please note: This e-mail may contain confidential information
> intended solely for the addressee. If you have received this
> e-mail in error, please do not disclose it to anyone, notify
> the sender promptly, and delete the message from your system.
> Thank you.
>
>


-- 
Fengbin

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2366984

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].