Guten Tag Johan Corveleyn,
am Donnerstag, 25. Januar 2018 um 20:40 schrieben Sie:
> But I don't understand what you're trying to do. You want to include
> the WC-root-relative path to *another dir* inside some config file,
> while you're checking out or updating that config file? That's weird.
On
On Thu, Jan 25, 2018 at 10:40 AM, Santosh Kondapuram
wrote:
> Hi Johan,
>
> I have tried reloading the dump as you suggested with -M 0 option but still
> I am running in to the same issue.
> Seems like the svn admin could not load the dump due to sha1 collision files.
> So the question is how d
On 2018-01-25 20:40, Johan Corveleyn wrote:
On Thu, Jan 25, 2018 at 4:55 PM, Thorsten Schöning
wrote:
Hi all,
I'm distributing software directly using SVN and the working copy
contians a configuration file which needs to contain some absolute
path to a special dir in that working copy. The g
On Thu, Jan 25, 2018 at 4:55 PM, Thorsten Schöning
wrote:
> Hi all,
>
> I'm distributing software directly using SVN and the working copy
> contians a configuration file which needs to contain some absolute
> path to a special dir in that working copy. The goal is to not need to
> commit that path
On Thu, Jan 25, 2018 at 11:14 AM, Bill Huang-黃靖翔
wrote:
I (Johan Corveleyn) wrote:
>> Since you mentioned that the error only occurs if the total size of the
>> commit gets large, the first suspect is the back-end filesystem. I think SVN
>> internally has no (practical) limit on the total size
Hi all,
I'm distributing software directly using SVN and the working copy
contians a configuration file which needs to contain some absolute
path to a special dir in that working copy. The goal is to not need to
commit that path of course, but automatically generate it during a
checkout/update. I
I've fixed it. I was mistaken, a mergeinfo property was set on the offending,
lower-level folder. Deleting that resulted in a complete merge.
From: David Aldrich [mailto:david.aldr...@emea.nec.com]
Sent: 25 January 2018 10:16
To: 'users@subversion.apache.org' (users@subversion.apache.org)
Subje
Hi
The merging of one our branches is broken and I would welcome some help to fix
it please.
One of our developers merged to the branch from trunk, but failed to commit the
changes to the top of the branch so the mergeinfo was lost. He also
cherry-picked the files, so it was a bit of a mess.
Dear Sir:
Thanks for your reply
1.
Good thing that you reproduced it on a new, clean repository. This new
repository is on a similar environment, with the same SVN server version?
Yes , same SVN server version .
2.
Since you mentioned that the error only occurs if the total size of the commit
Hi Johan,
I have tried reloading the dump as you suggested with -M 0 option but still I
am running in to the same issue.
Seems like the svn admin could not load the dump due to sha1 collision files.
So the question is how do I identify the sha1 colliding files ? does the error
stack trace say
Hi Bill,
Please use "reply all" to keep the mailinglist in cc, so others can
help as well.
And as I said before, we prefer "bottom-posting" on this list, or
inline replying (if at all possible). Anyway, some more info below ...
On Thu, Jan 25, 2018 at 3:10 AM, Bill Huang-黃靖翔
wrote:
> Dear Johan
11 matches
Mail list logo