You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Bart van Oerle <ba...@gmail.com> on 2013/06/20 14:59:26 UTC
error checking out in TortoiseSVN
Hello,
I got the following error when doing a Check out with a freshly installed
TortoiseSVN:
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
I downloaded the 'TortoiseSVN-1.8.0.24401-x64-svn-1.8.0.msi' file and
installed it on a Windows 8, 64 bit laptop.
I hope this information is sufficient to solve this bug.
Greetz,
Bart
--
- Do not seek the truth
Only cease to cherish your opinions.
Re: error checking out in TortoiseSVN
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Fri, Jun 21, 2013 at 4:51 PM, Ivan Zhakov <iv...@visualsvn.com> wrote:
> On Thu, Jun 20, 2013 at 11:23 PM, Philip Martin
> <ph...@wandisco.com> wrote:
>> Ivan Zhakov <iv...@visualsvn.com> writes:
>>
>>> As breser pointed on IRC all HTTP/1.1 applications MUST support
>>> chunked transfer encoding. From RFC2616:
>>> [[[
>>> All HTTP/1.1 applications MUST be able to receive and decode the
>>> "chunked" transfer-coding, and MUST ignore chunk-extension extensions
>>> they do not understand.
>>> ]]]
>>>
>>> And server is application:
>>> [[[
>>> server
>>> An application program that accepts connections in order to service
>>> requests by sending back responses.
>>> ]]]
>>
>> On the other hand the RFC also says:
>>
>> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.12
>>
>> 10.4.12 411 Length Required
>>
>> The server refuses to accept the request without a defined
>> Content-Length. The client MAY repeat the request if it adds a valid
>> Content-Length header field containing the length of the message-body in
>> the request message.
>>
>> I assume the server can send this error since it is in the RFC. The
>> client can only retry with a Content-Length request, not a chunked
>> request. So it appears that the only chunked support a server needs is
>> to be able to reply 411.
>>
> Should be fixed by r1495419 [1]:
The fix violated RFC 2145, Section 2 and reverted in r1495455:
http://svn.haxx.se/dev/archive-2013-06/0504.shtml
--
Ivan Zhakov
Re: error checking out in TortoiseSVN
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Thu, Jun 20, 2013 at 11:23 PM, Philip Martin
<ph...@wandisco.com> wrote:
> Ivan Zhakov <iv...@visualsvn.com> writes:
>
>> As breser pointed on IRC all HTTP/1.1 applications MUST support
>> chunked transfer encoding. From RFC2616:
>> [[[
>> All HTTP/1.1 applications MUST be able to receive and decode the
>> "chunked" transfer-coding, and MUST ignore chunk-extension extensions
>> they do not understand.
>> ]]]
>>
>> And server is application:
>> [[[
>> server
>> An application program that accepts connections in order to service
>> requests by sending back responses.
>> ]]]
>
> On the other hand the RFC also says:
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.12
>
> 10.4.12 411 Length Required
>
> The server refuses to accept the request without a defined
> Content-Length. The client MAY repeat the request if it adds a valid
> Content-Length header field containing the length of the message-body in
> the request message.
>
> I assume the server can send this error since it is in the RFC. The
> client can only retry with a Content-Length request, not a chunked
> request. So it appears that the only chunked support a server needs is
> to be able to reply 411.
>
Should be fixed by r1495419 [1]:
[[[[
Rework server chunked transfer encoding support detection in ra_serf.
Use HTTP/1.1 chunked transfer encoding for first OPTIONS request and
then fallback to HTTP/1.0 requests if HTTP 411 status code or
HTTP/1.0 response received.
]]]
I've tested my fix with all publicly available servers like
unfuddle.com and xp-dev.com
[1] http://svn.apache.org/r1495419
--
Ivan Zhakov
CTO | VisualSVN | http://www.visualsvn.com
Re: error checking out in TortoiseSVN
Posted by Philip Martin <ph...@wandisco.com>.
Ivan Zhakov <iv...@visualsvn.com> writes:
> As breser pointed on IRC all HTTP/1.1 applications MUST support
> chunked transfer encoding. From RFC2616:
> [[[
> All HTTP/1.1 applications MUST be able to receive and decode the
> "chunked" transfer-coding, and MUST ignore chunk-extension extensions
> they do not understand.
> ]]]
>
> And server is application:
> [[[
> server
> An application program that accepts connections in order to service
> requests by sending back responses.
> ]]]
On the other hand the RFC also says:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.12
10.4.12 411 Length Required
The server refuses to accept the request without a defined
Content-Length. The client MAY repeat the request if it adds a valid
Content-Length header field containing the length of the message-body in
the request message.
I assume the server can send this error since it is in the RFC. The
client can only retry with a Content-Length request, not a chunked
request. So it appears that the only chunked support a server needs is
to be able to reply 411.
--
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
www.wandisco.com
Re: error checking out in TortoiseSVN
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Thu, Jun 20, 2013 at 9:33 PM, Bert Huijben <be...@qqmail.nl> wrote:
>> -----Original Message-----
>> From: Stefan Küng [mailto:tortoisesvn@gmail.com]
>> Sent: donderdag 20 juni 2013 19:28
>> To: dev@subversion.apache.org >> Subversion Development
>> Subject: Re: error checking out in TortoiseSVN
>>
>> On 20.06.2013 17:02, Bart van Oerle wrote:
>> > I created and uploaded a dump file (damn it's big), I hope this will
>> > help you guys solving the problem.
>> > http://www.sendspace.com/file/8m1osy
>> >
>> Here's the stack trace:
>
> [We are busy on irc]
>
> We determined that this problem is caused by a proxy server in front of
> apache.
>
> Once ra_serf receives a http/1.1 response it assumes that the server
> supports the chunked encoding and at least nginx doesn't.
>
As breser pointed on IRC all HTTP/1.1 applications MUST support
chunked transfer encoding. From RFC2616:
[[[
All HTTP/1.1 applications MUST be able to receive and decode the
"chunked" transfer-coding, and MUST ignore chunk-extension extensions
they do not understand.
]]]
And server is application:
[[[
server
An application program that accepts connections in order to service
requests by sending back responses.
]]]
So right solution is fix/upgrade proxy. May be we can add client-side
configuration option to force using HTTP/1.0 in Subversion.
--
Ivan Zhakov
RE: error checking out in TortoiseSVN
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn@gmail.com]
> Sent: donderdag 20 juni 2013 19:28
> To: dev@subversion.apache.org >> Subversion Development
> Subject: Re: error checking out in TortoiseSVN
>
> On 20.06.2013 17:02, Bart van Oerle wrote:
> > I created and uploaded a dump file (damn it's big), I hope this will
> > help you guys solving the problem.
> > http://www.sendspace.com/file/8m1osy
> >
> Here's the stack trace:
[We are busy on irc]
We determined that this problem is caused by a proxy server in front of
apache.
Once ra_serf receives a http/1.1 response it assumes that the server
supports the chunked encoding and at least nginx doesn't.
Once we then issue a request to nginx, that causes a HTTP status 411
'Content-Length required'. And ra_serf (pre r1495104) ignored that error,
but didn't get a proper head revision either.
r1495104 makes ra_serf report the proper http error that the user should
have seen. (Nominated for backport)
The real fix would be to somehow detect this case and then we shouldn't use
the more efficient chunked algorithm from serf.
Bert
Re: error checking out in TortoiseSVN
Posted by Stefan Küng <to...@gmail.com>.
On 20.06.2013 17:02, Bart van Oerle wrote:
> I created and uploaded a dump file (damn it's big), I hope this will
> help you guys solving the problem.
> http://www.sendspace.com/file/8m1osy
>
Here's the stack trace:
BowPad
TortoiseProc.exe!svn_error_handle_malfunction(int can_return=0, const char * file=0x000000d5cb21b628, int line=-1, const char * expr=0x000000006ccd35c1) Line 2944 C++
libsvn_tsvn.dll!repos_locations(const char * * start_url=0x000000d5cb4b2ba0, const char * * end_url=0x000000d5cb21b549, svn_ra_session_t * ra_session=0x000000d5cb4b2ba0, const char * url=0x000007fc43c65458, long peg_revnum=-1, long start_revnum=-1, long end_revnum=-1, apr_pool_t * result_pool=0x000000d5cb4849d8, apr_pool_t * scratch_pool=0x000000d5cb4aaa98) Line 647 C
libsvn_tsvn.dll!svn_client__repos_locations(const char * * start_url=0x000000d5cb21b628, long * start_revision=0x000000d5cb21b630, const char * * end_url=0x0000000000000000, long * end_revision=0x0000000000000000, svn_ra_session_t * ra_session=0x000000d5cb4b2ba0, const char * path=0x000000d5cdb5f898, const svn_opt_revision_t * revision=0x000000d5cb21b5f0, const svn_opt_revision_t * start=0x000000d5cb21b5e0, const svn_opt_revision_t * end=0x0000000000000000, svn_client_ctx_t * ctx=0x000000d5cb485170, apr_pool_t * pool=0x000000d5cb4849d8) Line 860 C
libsvn_tsvn.dll!svn_client__resolve_rev_and_url(svn_client__pathrev_t * * resolved_loc_p=0x000000d5cdb5f898, svn_ra_session_t * ra_session=0x000000d5cb21b691, const char * path_or_url=0x0000000000000000, const svn_opt_revision_t * peg_revision=0x000007f700000001, const svn_opt_revision_t * revision=0x000000d5ffffffff, svn_client_ctx_t * ctx=0x000000d5cb485170, apr_pool_t * pool=0x000000d5cb4849d8) Line 474 C
libsvn_tsvn.dll!svn_client_info3(const char * abspath_or_url=0x000000d5cb21b8d0, const svn_opt_revision_t * peg_revision=0x000000d5cdb5f898, const svn_opt_revision_t * revision=0x000000d5cb21b8a0, svn_depth_t depth=-886982448, int fetch_excluded=1, int fetch_actual_only=1, const apr_array_header_t * changelists=0x0000000000000000, svn_error_t * (void *, const char *, const svn_client_info2_t *, apr_pool_t *) * receiver=0x000007f79bde09e0, void * receiver_baton=0x000000d5cb21b8d0, svn_client_ctx_t * ctx=0x000000d5cb485170, apr_pool_t * pool=0x000000d5cb4849d8) Line 300 C
TortoiseProc.exe!SVNInfo::GetFirstFileInfo(const CTSVNPath & path={...}, SVNRev pegrev={...}, SVNRev revision={...}, svn_depth_t depth=svn_depth_empty, bool fetchExcluded=208, bool fetchActualOnly=208) Line 136 C++
TortoiseProc.exe!SVNInfo::IsFile(const CTSVNPath & path={...}, const SVNRev & revision={...}) Line 296 C++
TortoiseProc.exe!CCheckoutDlg::OnOK() Line 347 C++
The revision passed to svn_client_info3 as the peg revision is actually
HEAD.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
Re: error checking out in TortoiseSVN
Posted by Bart van Oerle <ba...@gmail.com>.
I created and uploaded a dump file (damn it's big), I hope this will help
you guys solving the problem.
http://www.sendspace.com/file/8m1osy
2013/6/20 Tobias Bading <tb...@web.de>
> On 20.06.2013 16:05, Daniel Shahaf wrote:
>
>> Tobias Bading wrote on Thu, Jun 20, 2013 at 16:01:45 +0200:
>>
>>> On 20.06.2013 15:54, Daniel Shahaf wrote:
>>>
>>>> On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
>>>>
>>>>> In file
>>>>> 'D:\Development\SVN\Releases\**TortoiseSVN-1.8.0\ext\**
>>>>> subversion\subversion\libsvn_**client\ra.c'
>>>>> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
>>>>>
>>>> Is there any way we can get the tortoise assertion reports to include a
>>>> stack
>>>> trace?
>>>>
>>> If the assert() (or similar) itself creates a dialog to show what went
>>> wrong, you could use the Windows Task Manager or the SysInternal Process
>>> Explorer to create a mini-dump of the process while this dialog is
>>> displayed.
>>>
>> SysInternal is not an option, our users can't be assumed to have that
>> installed.
>>
>
> At least in Windows 7, the Task Manager can create full dumps including
> the heap. Every Windows 7 user should at least have heard of the Task
> Manager, right? ;-) If the process is waiting for the user to dismiss the
> error dialog, the dump should contain more than enough to see what happened.
>
>
--
- Do not seek the truth
Only cease to cherish your opinions.
Re: error checking out in TortoiseSVN
Posted by Daniel Shahaf <da...@apache.org>.
On Thu, Jun 20, 2013 at 04:09:25PM +0200, Tobias Bading wrote:
> On 20.06.2013 16:05, Daniel Shahaf wrote:
> >Tobias Bading wrote on Thu, Jun 20, 2013 at 16:01:45 +0200:
> >>On 20.06.2013 15:54, Daniel Shahaf wrote:
> >>>On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
> >>>>In file
> >>>> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
> >>>> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
> >>>Is there any way we can get the tortoise assertion reports to include a stack
> >>>trace?
> >>If the assert() (or similar) itself creates a dialog to show what went
> >>wrong, you could use the Windows Task Manager or the SysInternal Process
> >>Explorer to create a mini-dump of the process while this dialog is
> >>displayed.
> >SysInternal is not an option, our users can't be assumed to have that
> >installed.
>
> At least in Windows 7, the Task Manager can create full dumps
> including the heap. Every Windows 7 user should at least have heard
> of the Task Manager, right? ;-) If the process is waiting for the
> user to dismiss the error dialog, the dump should contain more than
> enough to see what happened.
Non-starter, sorry. People don't read the error message (it asks to explain in
the email what you were doing when the assertion triggered; many reports on
users@ are just a verbatim copy-paste of the error with no other text
whatsoever), so asking the user to collect information for us from here or
there won't help much.
Granted, we could have a page in our docs explaining how to get a stack trace
on windows (from svn.exe too), but it's simply not what I was looking for.
Thanks for your input!
Daniel
Re: error checking out in TortoiseSVN
Posted by Tobias Bading <tb...@web.de>.
On 20.06.2013 16:05, Daniel Shahaf wrote:
> Tobias Bading wrote on Thu, Jun 20, 2013 at 16:01:45 +0200:
>> On 20.06.2013 15:54, Daniel Shahaf wrote:
>>> On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
>>>> In file
>>>> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
>>>> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
>>> Is there any way we can get the tortoise assertion reports to include a stack
>>> trace?
>> If the assert() (or similar) itself creates a dialog to show what went
>> wrong, you could use the Windows Task Manager or the SysInternal Process
>> Explorer to create a mini-dump of the process while this dialog is
>> displayed.
> SysInternal is not an option, our users can't be assumed to have that
> installed.
At least in Windows 7, the Task Manager can create full dumps including
the heap. Every Windows 7 user should at least have heard of the Task
Manager, right? ;-) If the process is waiting for the user to dismiss
the error dialog, the dump should contain more than enough to see what
happened.
Re: error checking out in TortoiseSVN
Posted by Daniel Shahaf <da...@elego.de>.
Tobias Bading wrote on Thu, Jun 20, 2013 at 16:01:45 +0200:
> On 20.06.2013 15:54, Daniel Shahaf wrote:
>> On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
>>> In file
>>> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
>>> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
>> Is there any way we can get the tortoise assertion reports to include a stack
>> trace?
>
> If the assert() (or similar) itself creates a dialog to show what went
> wrong, you could use the Windows Task Manager or the SysInternal Process
> Explorer to create a mini-dump of the process while this dialog is
> displayed.
SysInternal is not an option, our users can't be assumed to have that
installed.
I hoped for something that prints the stack trace directly into the
error dialog, so that we'll get it when people Ctrl+C that into an
email.
I'm not sure if you're familiar with the maintainer-mode error chains:
% svnadmin upgrade /
subversion/svnadmin/svnadmin.c:2125,
subversion/libsvn_repos/repos.c:1555,
subversion/libsvn_repos/repos.c:1461,
subversion/libsvn_repos/repos.c:1423,
subversion/libsvn_subr/io.c:4208,
subversion/libsvn_subr/io.c:3293: (apr_err=ENOENT)
svnadmin: E000002: Can't open file '/format': No such file or directory
Re: error checking out in TortoiseSVN
Posted by Mark Phippard <ma...@gmail.com>.
On Thu, Jun 20, 2013 at 10:01 AM, Tobias Bading <tb...@web.de> wrote:
> On 20.06.2013 15:54, Daniel Shahaf wrote:
>>
>> On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
>>>
>>> In file
>>>
>>> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
>>> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
>>
>> Is there any way we can get the tortoise assertion reports to include a
>> stack
>> trace?
>
>
> If the assert() (or similar) itself creates a dialog to show what went
> wrong, you could use the Windows Task Manager or the SysInternal Process
> Explorer to create a mini-dump of the process while this dialog is
> displayed.
Is anyone getting this error when checking out from a publicly
accessible repository? That would make it easier for others to
replicate and debug.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Re: error checking out in TortoiseSVN
Posted by Tobias Bading <tb...@web.de>.
On 20.06.2013 15:54, Daniel Shahaf wrote:
> On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
>> In file
>> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
>> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
> Is there any way we can get the tortoise assertion reports to include a stack
> trace?
If the assert() (or similar) itself creates a dialog to show what went
wrong, you could use the Windows Task Manager or the SysInternal Process
Explorer to create a mini-dump of the process while this dialog is
displayed.
Re: error checking out in TortoiseSVN
Posted by Daniel Shahaf <da...@apache.org>.
On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
Is there any way we can get the tortoise assertion reports to include a stack
trace?
I don't know whether that's via svn_error_trace() or via some custom
Windows-only stuff, but I suspect it might save us a lot of time trying to
reproduce these.
Re: error checking out in TortoiseSVN
Posted by Stefan Küng <to...@gmail.com>.
On 20.06.2013 16:20, Daniel Shahaf wrote:
> Does Tortoise apply any patches to its binaries? That is, the svn.exe Bart
> used contain any code not in our tag?
No, it's a plain svn.exe without any patches.
The only difference is how it's built: instead of a dll for each lib
there's only one dll containing all the svn libs.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
Re: error checking out in TortoiseSVN
Posted by Daniel Shahaf <da...@apache.org>.
Does Tortoise apply any patches to its binaries? That is, the svn.exe Bart
used contain any code not in our tag?
On Thu, Jun 20, 2013 at 04:18:00PM +0200, Bart van Oerle wrote:
> I tried a checkout from the command line and got the same error:
> svn: E235000: In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subvers
> ion\subversion\libsvn_client\ra.c' line 647: assertion failed (peg_revnum
> != SVN
> _INVALID_REVNUM)
>
> Sorry, hadn't seen this error was already posted, searched for it, but no
> result.
>
>
>
> 2013/6/20 Stefan Sperling <st...@elego.de>
>
> > On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
> > > Hello,
> > >
> > > I got the following error when doing a Check out with a freshly installed
> > > TortoiseSVN:
> > >
> > > In file
> > >
> > 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
> > > line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
> > >
> > >
> > > I downloaded the 'TortoiseSVN-1.8.0.24401-x64-svn-1.8.0.msi' file and
> > > installed it on a Windows 8, 64 bit laptop.
> > >
> > > I hope this information is sufficient to solve this bug.
> > >
> > > Greetz,
> > > Bart
> > >
> >
> > Hi Bart,
> >
> > This problem has been reported to this mailing list before today:
> > http://svn.haxx.se/users/archive-2013-06/0171.shtml
> >
> > Have you ruled out whether this problem is specific to TortoiseSVN?
> > Can you check out the repository with the 'svn.exe' binary which
> > can be optionally installed along with TortoiseSVN? (
> > http://gaurangpatel.net/posted_images/SVN-checkout-using-BATCH-and-Powershell_A0FD/SVNInstall.png
> > )
> >
>
>
>
> --
>
> - Do not seek the truth
> Only cease to cherish your opinions.
Re: error checking out in TortoiseSVN
Posted by Bart van Oerle <ba...@gmail.com>.
I tried a checkout from the command line and got the same error:
svn: E235000: In file
'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subvers
ion\subversion\libsvn_client\ra.c' line 647: assertion failed (peg_revnum
!= SVN
_INVALID_REVNUM)
Sorry, hadn't seen this error was already posted, searched for it, but no
result.
2013/6/20 Stefan Sperling <st...@elego.de>
> On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
> > Hello,
> >
> > I got the following error when doing a Check out with a freshly installed
> > TortoiseSVN:
> >
> > In file
> >
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
> > line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
> >
> >
> > I downloaded the 'TortoiseSVN-1.8.0.24401-x64-svn-1.8.0.msi' file and
> > installed it on a Windows 8, 64 bit laptop.
> >
> > I hope this information is sufficient to solve this bug.
> >
> > Greetz,
> > Bart
> >
>
> Hi Bart,
>
> This problem has been reported to this mailing list before today:
> http://svn.haxx.se/users/archive-2013-06/0171.shtml
>
> Have you ruled out whether this problem is specific to TortoiseSVN?
> Can you check out the repository with the 'svn.exe' binary which
> can be optionally installed along with TortoiseSVN? (
> http://gaurangpatel.net/posted_images/SVN-checkout-using-BATCH-and-Powershell_A0FD/SVNInstall.png
> )
>
--
- Do not seek the truth
Only cease to cherish your opinions.
Re: error checking out in TortoiseSVN
Posted by "Chris T." <ch...@gmail.com>.
Adding to the list of people experiencing this issue.
Using Windows 7 x64 trying to connect to a repo on unfuddle.com.
Re: error checking out in TortoiseSVN
Posted by Crayon <cr...@rocketmail.com>.
Vitaly <v.ketsenko <at> gmail.com> writes:
>
> Hi All!
> I got exactly the same error with 1.8.0 on Windows 7 x64.
> I have already reverted back to 1.7.9, but here's what I've noticed:
> 1. I work with 2 different svn repositaries, one is private, I don't know
> what version of SVN is installed, but it works fine. The other one is https://
> xp-dev.com/, and here I couldn't do anything - neither update\commit, nor
> checkout\show log.
I'm having the same problem with https://xp-dev.com and TortoiseSVN 1.8.0 on
Windows 7 64-bit.
Re: error checking out in TortoiseSVN
Posted by Vitaly <v....@gmail.com>.
Hi All!
I got exactly the same error with 1.8.0 on Windows 7 x64.
I have already reverted back to 1.7.9, but here's what I've noticed:
1. I work with 2 different svn repositaries, one is private, I don't know
what version of SVN is installed, but it works fine. The other one is https://
xp-dev.com/, and here I couldn't do anything - neither update\commit, nor
checkout\show log.
2. I got different errors. I got error above when I tried to checkout. I got
message that I'm in offline mode when I tried to update\commit. And when I
tried to open repository browser, first I had to enter my login\pass (though
they are stored), then I got also error above.
AFter I uninstalled 1.8.0 and installed 1.7.9, I didn't have to enter my login
\pass.
Worst thing is that new Visual SVN works only with 1.8.0, so I had to revert
it back either.
Re: error checking out in TortoiseSVN
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Jun 20, 2013 at 02:59:26PM +0200, Bart van Oerle wrote:
> Hello,
>
> I got the following error when doing a Check out with a freshly installed
> TortoiseSVN:
>
> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
> line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
>
>
> I downloaded the 'TortoiseSVN-1.8.0.24401-x64-svn-1.8.0.msi' file and
> installed it on a Windows 8, 64 bit laptop.
>
> I hope this information is sufficient to solve this bug.
>
> Greetz,
> Bart
>
Hi Bart,
This problem has been reported to this mailing list before today:
http://svn.haxx.se/users/archive-2013-06/0171.shtml
Have you ruled out whether this problem is specific to TortoiseSVN?
Can you check out the repository with the 'svn.exe' binary which
can be optionally installed along with TortoiseSVN? (http://gaurangpatel.net/posted_images/SVN-checkout-using-BATCH-and-Powershell_A0FD/SVNInstall.png)