Guess what happened... Yes, I again had the problem which I mentioned two
days ago.
I have the problem with version 1.2.1 as well as with 1.1.4. But when I
apply my stuporous
little patch I can do the commit without any problem.
Next I stepped back to the problematic state of the repository / working
copy and tried
it with yesterday morning's trunk (release 15801) and had the same problem
again.
Please don't hesitate to ask me for any additional information you need to
find a solution for the problem.
Thank you!
Mathias Weinert wrote:
> Hi Karl,
>
> again sorry for this. I had this problem several times in the past
> but at the moment I can't reproduce it.
> As soon as I will get it again I will first make a copy of the
> repository and the working copy in
> order to preserve this environment and then I will try it with a
> current subversion trunk version and
> tell you the result.
>
> Mathias
>
> kfogel@newton.ch.collab.net schrieb am 19.08.2005 04:59:33:
>
> > Mathias.Weinert@gfa-net.de writes:
> > > Unfortunately I even can't reproduce it with my subversion 1.2.1...
> > > The repository I used yesterday is now in a state where I don't get
this
> > > problem although I think that I do just the same as yesterday.
> > > Can you tell me in which situation I will get the error again? Sorry
for
> > > this.
> > > (If I can reproduce it again I will test with today's trunk version
which
> > > I have already built)
> >
> > No, I don't know how to reproduce it either. If you can't, we'll just
> > have to either hope it's gone, or wait for it to come back someday.
> >
> > -Karl
> >
Received on Fri Aug 19 11:11:31 2005