Hey Max,
it worked! I've changed the path, created a new repository, and can now
commit as often as I want. Beautiful! How come that such a small issue
hasn't been patched for 4 months? Especially if it causes such ...
trouble. Anyway, thanks a lot! You're the man!
Daniel
Max Bowsher wrote:
> daniel wrote:
>
>> I apologize.
>>
>> The output of "svn info bla.tex" is unchanged.
>>
>> A subsequent "more .svn\wcprops\bla.tex.svn-work" (windows..) outputs:
>> K 25
>> svn:wc:ra_dav:version-url
>> V 25
>> /!svn/ver/1/bla.tex
>> END
>
>
> Aha! It is what I though.
> Bug: http://subversion.tigris.org/issues/show_bug.cgi?id=1851
> Workaround:
> Do not put your repository at <Location />
> i.e. https://svn.myhost.cno/repos/
> not https://svn.myhost.cno/
>
> Max.
>
>
>> Max Bowsher wrote:
>>
>>> daniel wrote:
>>>
>>>> Alright, I've now downloaded and installed the command line client,
>>>> version 1.0.6 / win32.
>>>> Hadn't expected it to be so easy to use..
>>>>
>>>> Here is the output you asked for ("svn info bla.tex" from the main
>>>> folder of the working directory):
>>>> Path: bla.tex
>>>> Name: bla.tex
>>>> URL: https://svn.myhost.cno/bla.tex
>>>> Repository UUID: (...)
>>>> Revision: 3
>>>> Node kind: file
>>>> Schedule: normal
>>>> Last Changed Author: daniel
>>>> Last Changed Rev: 2
>>>> Last Changed Date: 2004-09-04 01:13:04 +0200 (Sat, 04 Sep 2004)
>>>> Text Last Updated: 2004-09-04 01:13:20 +0200 (Sat, 04 Sep 2004)
>>>> Checksum: (...)
>>>>
>>>> Then, I couldn't resist to try a manual commit. Here is the output
>>>> ("svn
>>>> commit --message --force-log bla.tex"):
>>>> Sending bla.tex
>>>> svn: Commit failed (details follow)
>>>> svn: Your file or directory 'bla.tex' is probably out of date
>>>> svn:
>>>> The version resource does not correspond to the resource within the
>>>> transaction. Either the requested version resource is out of date
>>>> (needs
>>>> to be updated), or the requested version resource is newer than the
>>>> transaction root (restart the commit).
>>>>
>>>> Executing "svn status" returns:
>>>> M bla.tex
>>>>
>>>> And "svn update bla.tex" outputs:
>>>> At revision 3.
>>>>
>>>> I also tried "svn cleanup .". It finished without problems, but didn't
>>>> change anything.
>>>>
>>>> Hope this helps?
>>>
>>>
>>>
>>> You didn't provide the critical piece of information - I need the
>>> contents of .svn/wcprops/bla.tex.svn-work
>>>
>>> Please also re-do the "svn info" output, because I need a matched set
>>> of "svn info" and wcprops file contents to see if the problem is what
>>> I think it might be.
>>>
>>> Max.
>>>
>>>> Max Bowsher wrote:
>>>>
>>>>> daniel wrote:
>>>>>
>>>>>> Hi folks.
>>>>>>
>>>>>> This problem I've already described on the irc channel, but it
>>>>>> couldn't
>>>>>> be solved it yet. First, let me say that this _might_ have to do
>>>>>> with
>>>>>> TortoiseSVN, but it doesn't necessarily _have_to_be_ that. So
>>>>>> before you
>>>>>> start dizzing me now, yes, I _have_ asked them, and they sent me to
>>>>>> you.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> It's usually helpful if you can replicate the problem with the svn
>>>>> commandline client. Because we know more about that here than about
>>>>> TSVN.
>>>>>
>>>>>> The thing thing is, I can commit a file, but I can't commit it
>>>>>> twice. At
>>>>>> least, not unless somebody else has commited this file in the
>>>>>> meantime.
>>>>>> Example:
>>>>>> - The repository contains a file bla.tex
>>>>>> - I'm the only one who's actually working on this file
>>>>>> - I commit it once after changing it
>>>>>> - Everything's fine
>>>>>> - I modify it again
>>>>>> - Commit fails, error message "Commit failed (details follow): Your
>>>>>> file
>>>>>> or directory 'bla.tex' is probably out of date; The version resource
>>>>>> does not correspond to the resource within the transaction.
>>>>>> Either the
>>>>>> requested version resource is out of date (needs to be updated), or
>>>>>> the
>>>>>> requested version resource is newer than the transaction root
>>>>>> (restart
>>>>>> the commit)."
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I wonder if this is a wcprops-out-of-date bug.
>>>>>
>>>>> Please show the output of:
>>>>> $ svn info bla.tex
>>>>> $ cat .svn/wcprops/bla.tex.svn-work
>>>>>
>>>>> If you don't have a commandline client with which to run svn info,
>>>>> then please consider downloading one, but for now, cut-n-paste the
>>>>> <entry ... /> tag which refers to bla.tex from .svn/entries.
>>>>>
>>>>>> No, please don't say it. I _am_ aware that I have to check for
>>>>>> updates,
>>>>>> and that an update would usually help to solve this problem, but in
>>>>>> this
>>>>>> case it doesn't. Neither an update of the entire folder, nor the
>>>>>> file
>>>>>> itselt, nor another commit of any of these files change anything.
>>>>>> What
>>>>>> does surprisingly work is that, after somebody else makes a dummy
>>>>>> change
>>>>>> (e.g. inserting a blank line in bla.tex) and commits it, the
>>>>>> update on
>>>>>> my copy passes the regular update with a successful merge, and I can
>>>>>> commit again.
>>>>>
>>>>>
>>>>>
>>>>> ...
>>>>>
>>>>>> I've checked the version numbers of svn and all software that
>>>>>> could be
>>>>>> involved in the communication. We have a Suse 9.1 server running
>>>>>> with
>>>>>> the latest patches installed for this release. Subversion is
>>>>>> 1.0.0, as
>>>>>> of August 4, 2004. So is the Apache2 subversion module. Tortoise
>>>>>> has the
>>>>>> latest version as well.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 1.0.0 ? That's rather old. You do know there have been security
>>>>> releases since then? And quite a lot of bugfixes too?
>>>>>
>>>>> BTW, I'm on IRC in #svn quite a lot - you may want to respond that
>>>>> way.
>>>>>
>>>>> Max.
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 4 16:22:59 2004