No, because so far there's zero evidence so far to believe that there's
a bug in Subversion. In fact, you even *proved* that Subversion isn't
corrupting the data... it's exactly correc.t Meanwhile, there are
1000 reasons for Jboss not to start up. I already replied and gave you
a suggestion: what happens when you simply unpack the jbass tarball
into /tmp and try starting it?
I certainly don't mean to offend here. But the probability of a
Subversion bug this fundamental going undiscovered for 4 years is
ridiculously small. The probability of something in your environment
preventing jboss from starting is very high. This is a matter of
applying Occam's Razor.
On Feb 25, 2005, at 2:43 AM, Thomas Quas wrote:
> Hmm, does anybody of the development team care about this issue?
> Should I file a defect report?
>
>
> -tom
>
> Thomas Quas wrote:
>> I just had this idea: instead of doing the remote
>> import(svn+ssh://box/repo), I tried importing JBoss on the server
>> machine (file://repo).
>> Checking out on the server (file://), starting JBoss: voila, it works!
>> Checking out on a remote client (svn+ssh://), starting JBoss: voila,
>> it works!
>> Does that mean import and add of large binary packages over svn+ssh
>> is broken?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 25 14:14:49 2005