On Wed, Apr 29, 2015 at 12:03 AM, Branko Čibej wrote:
> On 29.04.2015 05:09, Nico Kadel-Garcia wrote:
>> On Tue, Apr 28, 2015 at 5:03 PM, Andrew Reedick wrote:
>>> Does anyone have any tips on how to upgrade a very old repo? The db/format
>>> lists "1". A 1.8 svn client cannot hotcopy, dump or
On 29.04.2015 07:14, Nico Kadel-Garcia wrote:
> On Wed, Apr 29, 2015 at 12:03 AM, Branko Čibej wrote:
>> On 29.04.2015 05:09, Nico Kadel-Garcia wrote:
>>> On Tue, Apr 28, 2015 at 5:03 PM, Andrew Reedick wrote:
Does anyone have any tips on how to upgrade a very old repo? The
db/format
Branko Čibej writes:
> In any case, 1.8 /should/ be able to dump an FSFSv1 repository, and the
> /db/current file should exists; it's been around since FSFSv1.
> You can try recreating it; the format is described here:
>
> https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/
On Wed, Apr 29, 2015 at 1:32 AM, Branko Čibej wrote:
> On 29.04.2015 07:14, Nico Kadel-Garcia wrote:
>> On Wed, Apr 29, 2015 at 12:03 AM, Branko Čibej wrote:
>>> On 29.04.2015 05:09, Nico Kadel-Garcia wrote:
On Tue, Apr 28, 2015 at 5:03 PM, Andrew Reedick
wrote:
> Does anyone have
> -Original Message-
> From: Branko Čibej [mailto:br...@wandisco.com]
> Are we talking about the repository format or the FSFS format here? If
> /db/fs-type says "fsfs" then the repository format
> (/format) is probably 3 and you're talking about /db/format,
> yes? The distinction is i
Andrew Reedick writes:
> Bad News: However, it seems that I have bigger issues:
> * Dumped revision 109662.
> svnadmin: E720002: Can't open file
> 'devel_copy\db\revprops\109663': The system cannot find the file
> specified.
>
> When I sort the files in db/revs numerically, I see gap
I’m not sure if the \\?\ format is supported in the new rename api(as this is
an option in certain publi apis and not a low level supported format), but it
should certainly be used in the fallback codepath where the normal rename is
tried, like hiw it is in apr.
But if the new api fails with t
On 29.04.2015 21:28, Bert Huijben wrote:
> I’m not sure if the \\?\ format is supported in
> the new rename api(as this is an option in certain publi apis and not
> a low level supported format), but it should certainly be used in the
> fallback codepath where the normal rename is tried, like hiw
Hi,
We use some custom properties for tracking (e.g. my_prop:trace_to
req_12345) and have noticed that svn renames do not copy these across the
delete/add operation. I've tried searching the archives to see if I could
find a rationale as to why, but haven't come across any.
I'm guessing this cou
Dan Ellis wrote on Wed, Apr 29, 2015 at 15:43:00 -0700:
> Hi,
>
> We use some custom properties for tracking (e.g. my_prop:trace_to
> req_12345) and have noticed that svn renames do not copy these across the
> delete/add operation. I've tried searching the archives to see if I could
> find a rati
[snipping the part about db/revs, this is only about db/revprops]
Philip Martin wrote on Wed, Apr 29, 2015 at 18:53:04 +0100:
> Andrew Reedick writes:
>
> > Bad News: However, it seems that I have bigger issues:
> > * Dumped revision 109662.
> > svnadmin: E720002: Can't open file
> > 'd
For future reference: if svnadmin is version 1.9 or newer, it should
have the 'info' subcommand, which will display both the repository
format and the FS format.
http://subversion.apache.org/docs/release-notes/1.9#svnadmin-info
Daniel
(1.9 hasn't been released yet, as of this writing)
Andrew Ree
On Wed, Apr 29, 2015 at 4:01 PM, Daniel Shahaf
wrote:
> Dan Ellis wrote on Wed, Apr 29, 2015 at 15:43:00 -0700:
> > Hi,
> >
> > We use some custom properties for tracking (e.g. my_prop:trace_to
> > req_12345) and have noticed that svn renames do not copy these across the
> > delete/add operation.
> On Apr 29, 2015, at 4:13 PM, Dan Ellis wrote:
>
> This is specific to the rename operation (svn 1.8.9, win7):
>
> c:\Project_files\sandbox>svn pl -v .txt
> Properties on '.txt':
> myprop:trace_to
> req12345
>
> c:\Project_files\sandbox>svn rename .txt .txt
> A T
OK, so it gets stranger...
I admit I changed the property names a bit to simplify them. When I ran
the simplified names, it does work.
Here's the exact example that does not work:
c:\Project_files\sandbox_v2>svn pl -v A.txt
Properties on 'A.txt':
pebls:plcm
Test@4575
pebls:sha1
15 matches
Mail list logo