dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Error checking in files

( SVNSCC )
Type: Public Status:Closed Created: 21 May 04 05:00 Updated: 25 Jun 04 06:00
--> Igor Pushkov (admin)  at 25 Jun 04 06:00 writes

Mnetioned issue with incompability with SVN fixed now. So I close this
ticket.
--> Tristan Bates (user)  at 21 May 04 05:00 writes

We may have resolved this one.

It looks like a problem on the svn repository server.

We did an svnadmin recover on the repository, restarted the svnserve
process, did an svn cleanup on our working copy directories and it seemed
to fix it (ie we can commit our changes now).

This did however highlight another aspect of another issue that I logged in
the ticket titled "Working Copy not compatible with TortoiseSVN". In that
issue, I noted that TortoiseSVN did not recognise that subdirectories were
under source control.
Performing svn cleanup is supposed to do a recursive cleanup, however it
did not. We had to manually cleanup each subdirectory that reported being
"locked".
Additionally, an svn status in our solution directory reports a '?' as the
status for each subdirectory, again indicating that subversion does not
think that subdirectories are under source control. It seems that something
is missing (probably out of the .svn folder) that lets svn know that the
folders are under source control.
--> Tristan Bates (user)  at 21 May 04 05:00 writes

Sometimes when a developer checks in files, the checkin process seems to
hang.

We hit cancel on the SVNProxy dialog and get the following error:

svn: Commit failed (details follow):
svn: Can't get password

and then
"Check In: The operation could not be completed"

At this point nothing appears to have been checked in (ie it looks like it
rolled back the checkin).

The next time that we try to check in, we get an error saying that we need
to run svn cleanup.

After running svn cleanup we get the first error again.

This appears to be happening on the machines of the developers who did not
originally create the svn repository. (ie I created the svn repository for
this project from my machine and I don't seem to ever get this message but
every other developer does).
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9755012 visitor since 20 Jan 2003.
1095 visitors today and 2 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com