node unique id

2016-01-21 Thread Ren Wang
Can I assume the node revision id is unique in subversion? If so, is there
an API to get it by repository root, path and revision number parameters?

 

Regards,

 

Ren



Re: node unique id

2016-01-21 Thread Stefan Sperling
On Thu, Jan 21, 2016 at 10:25:09AM -0500, Ren Wang wrote:
> Can I assume the node revision id is unique in subversion?

Yes, but it is specific to a particular filesystem instance.
If you dump/load the repository all IDs will change.

> If so, is there
> an API to get it by repository root, path and revision number parameters?

svn_fs_paths_changed2() declared in include/subversion/svn_fs.h
provides the IDs for changed paths in a particular revision.

An ID is represented as an opaque object svn_fs_id_t.
The contents of this object depend on the filesystem backend used.
There are a few functions to operate on svn_fs_id_t, such as
svn_fs_unparse_id(). 

It's unclear what purpose you'd like to use these for so it's hard
to give more specific advice.


RE: node unique id

2016-01-21 Thread Ren Wang
Hi Stefan,

Thank you very much for the response. The purpose is to the uniquely
identify a file for a specific revision or the latest revision. 

What can I do if the file didn't change for a specified revision, then I
will need to get the latest revision number for the file, is there a API to
get the latest  revision for a node?

Regards,

Ren

-Original Message-
From: Stefan Sperling [mailto:s...@elego.de] 
Sent: Thursday, January 21, 2016 11:01 AM
To: Ren Wang 
Cc: 'Subversion Users' 
Subject: Re: node unique id

On Thu, Jan 21, 2016 at 10:25:09AM -0500, Ren Wang wrote:
> Can I assume the node revision id is unique in subversion?

Yes, but it is specific to a particular filesystem instance.
If you dump/load the repository all IDs will change.

> If so, is there
> an API to get it by repository root, path and revision number parameters?

svn_fs_paths_changed2() declared in include/subversion/svn_fs.h provides the
IDs for changed paths in a particular revision.

An ID is represented as an opaque object svn_fs_id_t.
The contents of this object depend on the filesystem backend used.
There are a few functions to operate on svn_fs_id_t, such as
svn_fs_unparse_id(). 

It's unclear what purpose you'd like to use these for so it's hard to give
more specific advice.



svn: E125012: Invalid character in hex checksum

2016-01-21 Thread Matthew Jurgens
I was recently running Fedora 22 x64 with svn version 
subversion-1.8.13-7.fc22.x86_64 (possibly but unlikely as low as 
subversion-1.8.13-2.fc22.x86_64). svn was functioning just fine in all 
regards. Everything was installed all on a single server, code, svn 
service, the lot.

My format is version 3.

I then did an upgrade to Fedora 23 which installed 
subversion-1.9.3-1.fc23.x86_64


Now, commands like svn checkout, svn commit, svn list (anything that 
needs to talk to the svn service) all return "svn: E125012: Invalid 
character in hex checksum" immediately.


I have rolled the /var/svn files (the subversion database) back to 
multiple versions in the past but all with exactly the same outcome. 
This problem does not appear to be corruption in my database. It appears 
to be something that changed in the upgrade from 1.8.13 to 1.9.3.


I can install a Fedora 22 VM with the old svn version and try and access 
the database, but that will still not allow me to access it from the 
newer svn version.


Is there something I need to do to upgrade the database between these 
versions?