>Subject: Re: Converted Repo not displaying historical differences > > >Michael Swanson schrieb: >> >> Dirk, >> >> Well, I just tried it on another computer here (a Win2K >loaner laptop) >> and it worked fine. Hrmph. It must be something with my machine. >> This doesn't require admin rights or anything like that to run, does >> it? >> >> At least I know its something with my particular machine now. I'll >> investigate here and see what I can figure out. If you think of >> anything that I might need, I'd be very glad to hear it. Thanks >> again. >> > >The only thing I can image is the way the temporary files are handled. >While retrieving the history I generate a new temporary file from the >latests revision with the delta record applied. The temporary file is >then copied to the output file if the user wants to see this >file, e.g. >in the "bulk" get operation. It seems that you have some problems with >these temporary files? > >tmpnam is said to create a temporary file in the current directory. If >just checked the code. It could be, that if you can't create a file in >the current directory, then this error condition is not properly >handled. From a quick glance through the code it could also be >that you >will see the behavoir, that you describe. > >Best regards >Dirk
I just ran a full conversion successfully when I had local admin privileges. If this does in fact have something to do with file privileges, then I have a feeling this has something to do with the way my company handles network security. We have a mixed Novell/AD network, and our file permissions are handled through the "Special Permissions" part of the security tab on the file properties dialog. When I'm logged in as a regular user, I don't actually have the rights assigned in the regular Security tab on the properties dialog, you have to dig in one more level, under the "Advanced" button, and that's where we're given our access rights. Meanwhile, the admin group *does* have the regular, top level rights assigned. The user level people do actually have full rights to the hard drive, but it's granted through something called "Special Permissions". This looks to be one of those situations where something *shouldn't* have an effect but it does. Unless there's some other reason why a local admin would be able to do this and a regular user wouldn't, this would seem to be the problem. Anyway, we've got the solution now, so we should be good to go. Thanks for all your help, Dirk, I greatly appreciate it. Mike Swanson _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
