On Mon, Mar 3, 2008 at 12:18 PM, David Glasser <glasser_at_davidglasser.net> wrote:
>
> On Mon, Mar 3, 2008 at 3:33 AM, <Stefan.Fuhrmann_at_etas.com> wrote:
> > "Norbert Schulze" <nosch.tsvn_at_online.de> wrote on 02.03.2008 21:49:36:
> >
> > > I have tried some of the latest TortoiseSVN 1.5 builds, but all have the
> > same error. I can
> > > checkout and update <svn://rubyforge.org/var/svn/ironruby/trunk>. But
> > if I try to "show log"
> > > there is a problem connecting to server.
> >
> > Thanks for the report. This seems to be a SVN problem:
> > Using the SVN 1.5-alpha2 (built by TSVN nightly), it also fails with
> > "Connection closed unexpectedly" when I try
> >
> > svn log svn://rubyforge.org/var/svn/ironruby/trunk
> >
> > > After going offline, also no log entries are shown, and
> > > the "From" field has a higher date (2106-02-07) than the "To" field
> > (1970-01-01).
> >
> > Since no log data is received at all (and there is no cache to fetch from)
> > the log dialog will be empty. The confusing date range should be fixed
> > soon.
>
> I can reproduce that. Thanks for the report.
... or maybe I can't. A bit ago, it worked with 1.4.x but not trunk;
right now it doesn't work with 1.4.x either, and in fact just
connecting to rubyforge.org:3690 fails. There's something odd going
on at their server (or servers?).
The specific failure in trunk is inside epg's log-with-revprops
backwards-compatibility code, by the way.
--dave
--
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-03 21:32:01 CET