Error At Entry In Entries File For Bogus Date
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How can I fix a bogus date error in TortoiseSVN up vote 5 down vote favorite I'm trying to update a folder and I get the following message in TortoiseSVN: Error at entry 2 in entries file for PathToFile: Bogus Date Is there a way I can fix this through TortoiseSVN? Thanks svn tortoisesvn share|improve this question edited May 2 '11 at 20:17 Andy Lester 50.7k1166121 asked Nov 11 '10 at 11:33 Paul Sheldrake 2,79472442 Have you tried deleting the folder and recommitting it? –Neil Nov 11 '10 at 11:36 What I ended up down was just checking out the project again. Not ideal but none of the other SVN commands would work –Paul Sheldrake Nov 20 '10 at 16:21 add a comment| 3 Answers 3 active oldest votes up vote 4 down vote accepted I ran into the same problem and cleanup didn't work either. Here's what I did to resolve it Checkout to new folder Export all items from corrupt folder Copy over clean checkout Checkout To Clean Folder Use TortoiseSVN's standard checkout commands to checkout to a different folder. Export all items from corrupt folder From Explorer, Right-click on the corrupt folder and drag to the desktop. Select "Export all items here". This basically copies the entire folder except for the .svn meta folders. Copy over clean checkout Copy the exported items over the newly checked out version. This restores any changes you might have made and puts you in a place to check them in. share|improve this answer answered May 2 '11 at 19:50 Paul Alexander 21.7k771122 I hate to do this every now and then. Versioning program should make programmers life easier not harder. I wonder if mercury and/or git have the same problems. –Petr Peller May 10 '11 at 12:41 add a comment| up vote 1 down vote Old topic, but I just came up against it, considering the time for a checkout runs around 2 hours, deleting and doing a complete new CO wasn't an option. I did however checkout the directory with the problem to a new folder, then in the file system deleted the corrupt folder and copied the newly
Threaded ♦ ♦ Locked 1 message Nicolás Grossi Reply | Threaded Open this post in threaded view ♦ ♦ | http://stackoverflow.com/questions/4153954/how-can-i-fix-a-bogus-date-error-in-tortoisesvn Report Content as Inappropriate ♦ ♦ how to fix svn: Error at entry 2 in entries file for '08-Software Configuration Management\ People: http://subversion.1072662.n5.nabble.com/how-to-fix-svn-Error-at-entry-2-in-entries-file-for-08-Software-Configuration-Management-td146545.html I´m getting this error trying to do a ci or cleanup on my wc. I´m using svn 1.6 client against svn 1.5.6 server repository C:\SVNRepositories\invest\trunk>svn up svn: Error at entry 2 in entries file for '08-Software Configuration Management\ 08_02-Varios\software\flashmediaserver': svn: Bogus date Does anyone knows how to fix this issue? thanks in advance! Nico ------------------------------------------------------ http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1731083To unsubscribe from this discussion, e-mail: [[hidden email]]. « Return to Subversion Users | 1 view|%1 views Loading... Free forum by Nabble Edit this page
on a NFS mount. Checkingout works fine, but whenever I try to svn stat/info/up a certaindirectory, I get the messagesvn: Error at entry 6 in entries file for 'cfg':svn: Bogus dateI traced it down to an empty file in this directory http://grokbase.com/t/subversion/users/105cehgfe8/problem-with-bogus-date-on-nfs that has a weird"text last changed" date in the entries file:1949-12-07T10:27:14.-840919ZThis date is different (random) each time I make a new checkout on theNFS mount. But everything is fine when I check out the repository on alocal disk.I tried https://groups.google.com/d/topic/tortoisesvn/AslXvVdcRkM removing, committing and re-adding the offending file, but thatdoesn't fix the problem.Any ideas what is going on there?My svn version is 1.5.7 (r36142).Thanks!Andreas reply Tweet Search Discussions Search All Groups users 1 response Oldest Nested David Brodbeck Are error at you by any chance using NFSv4, and mounting this filesystem from a Solaris NFS server? I encountered the same issue a few months ago. It appears to only happen with zero-length files, because as soon as data is written to the file the timestamp gets fixed. It's actually a Solaris bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6854659 One workaround is to use NFSv3. Another is to put some data in the zero-length file. The fix is in snv_126, which means it should error at entry be fixed in David Brodbeck at May 12, 2010 at 5:22 pm ⇧ On May 12, 2010, at 6:55 AM, Andreas Schwarz wrote:Hi,I have a strange problem with a working copy on a NFS mount. Checkingout works fine, but whenever I try to svn stat/info/up a certaindirectory, I get the messagesvn: Error at entry 6 in entries file for 'cfg':svn: Bogus dateI traced it down to an empty file in this directory that has a weird"text last changed" date in the entries file:1949-12-07T10:27:14.-840919ZThis date is different (random) each time I make a new checkout on theNFS mount. But everything is fine when I check out the repository on alocal disk.I tried removing, committing and re-adding the offending file, but thatdoesn't fix the problem.Any ideas what is going on there?Are you by any chance using NFSv4, and mounting this filesystem from a Solaris NFS server? I encountered the same issue a few months ago. It appears to only happen with zero-length files, because as soon as data is written to the file the timestamp gets fixed. It's actually a Solaris bug:http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6854659One workaround is to use NFSv3. Another is to put some data in the zero-length file.The fix is in snv_126, which means it should be fixed in the next version of OpenSolaris that comes out (the one that was supposed to be 2010.03, before the Oracle merger delayed everything.)--David BrodbeckSystem Administr
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen