You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by kf...@collab.net on 2004/12/01 16:00:17 UTC
Re: 11.0 to 1.1.1 migration trouble ( WinXP )
Andrew Varabei <an...@tut.by> writes:
> I installed 1.1.1 and get error from apache. Now it do not like to
> start as service, but work as standalone application.
>
> When I copy files from 1.1.0 back - all resurrects.
>
> Do you have any idea what happens ?
You need to give us *much* more detail before we can help you.
Please see http://svn.collab.net/repos/svn/trunk/BUGS for how to help
us help you.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: 11.0 to 1.1.1 migration trouble ( WinXP )
Posted by Andrew Varabei <an...@intellimerce.com>.
Environment:
Path=[..]C:\Program Files\Subversion\bin;[..]
WindowsXP SP2
svn-1.1.1-setup-2.exe
Apache/2.0.52 (Win32) SVN/1.1.0 DAV/2 Server at localhost Port 80
# Subversion
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
[..]
<Location /svn>
DAV svn
SVNParentPath C:/www/Repos
#SVNPath C:/www/Repos/root
AuthzSVNAccessFile C:/www/Repos/svnaccessfile
Require valid-user
AuthType Basic
AuthName "Subversion repository"
AuthUserFile C:/www/Repos/svn-auth
</Location>
I have both 1.1.0 and 1.1.1 unpacked and after I copy files from
C:\Program Files\Subversion\ , httpd/mod_authz_svn.so
httpd/mod_dav_svn.so to Apache2/modules , restart apache I got error :
service cannot start
>net start apache2
The Apache2 service is starting.
The Apache2 service could not be started.
A service specific error occurred: 1.
More help is available by typing NET HELPMSG 3547.
That is application specific error.
Nothing writes to log files
kfogel@collab.net wrote:
>Andrew Varabei <an...@tut.by> writes:
>
>
>>I installed 1.1.1 and get error from apache. Now it do not like to
>>start as service, but work as standalone application.
>>
>>When I copy files from 1.1.0 back - all resurrects.
>>
>>Do you have any idea what happens ?
>>
>>
>
>You need to give us *much* more detail before we can help you.
>
>Please see http://svn.collab.net/repos/svn/trunk/BUGS for how to help
>us help you.
>
>-Karl
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
Re: Information about updated project branch/tag
Posted by Edvard Majakari <ed...@staselog.com>.
Ben Collins-Sussman <su...@collab.net> writes:
> Sure, examine the revision and looked at changed paths. 'svnlook changed'
> will do the trick, or you can use lower-level APIs.
Hey - just what I needed (well, even better to be precise, because now I get
to see which individual files were changed too). Thanks a lot!
--
# Edvard Majakari Software Engineer
# PGP PUBLIC KEY available Soli Deo Gloria!
$_ = '456476617264204d616a616b6172692c20612043687269737469616e20'; print
join('',map{chr hex}(split/(\w{2})/)),uc substr(crypt(60281449,'es'),2,4),"\n";
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Information about updated project branch/tag
Posted by Ben Collins-Sussman <su...@collab.net>.
On May 31, 2005, at 5:06 AM, Edvard Majakari wrote:
>
> So, is it possible to find out (relatively quickly) what project on
> the
> repository got updated in post-commit phase?
>
Sure, examine the revision and looked at changed paths. 'svnlook
changed' will do the trick, or you can use lower-level APIs.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Information about updated project branch/tag
Posted by Edvard Majakari <ed...@staselog.com>.
I use a daemon for building my projects. I have created a simple post-commit
script along the following lines:
repo, rev = sys.argv[1:]
conn = daemon_connection()
conn.send_notify(repo, rev)
After receiving notification, the build daemon updates the repository and
builds it. The problem is that the daemon doesn't know which branch to
update. I have a development branch (trunk), release branch and latest
release- and release-candidate tags, which may need updates. Thus, when the
build daemon receives notification, it has to update all the branches (and
tags for minor typofixes etc) before it knows what it needs to build.
So, is it possible to find out (relatively quickly) what project on the
repository got updated in post-commit phase?
--
# Edvard Majakari Software Engineer
# PGP PUBLIC KEY available Soli Deo Gloria!
$_ = '456476617264204d616a616b6172692c20612043687269737469616e20'; print
join('',map{chr hex}(split/(\w{2})/)),uc substr(crypt(60281449,'es'),2,4),"\n";
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org