SVNDUMP error

[Manjunath Kashyap]

Hi All,

We have a svn repo up and running, version svn, version 1.4.2 .
The svnadmin dump command fails at a particular revision with the below
error message,

svnadmin: File not found: revision 219, path
'/qa/trunk/WsV/42TC/Reporting/R_M.js'

I viewed the log for this revision and i see that this file was created in
the 220 revision,
This was confirmed by below commands,

svn log -r 219 -v -v -v file:///svn/repo/qa/trunk/WsV/42TC/Reporting/R_M.js
svn: Unable to find repository location for
'file:///svn/repo/qa/trunk/WsV/42TC/Reporting/R_M.js' in revision 219


I even tried to skip the 219 revision from the dump but unable to do so,
Getting the below error when skipped the 219 revision and continue with the
next revision,

svnadmin dump /svn/repo --revision 220:HEAD --incremental >
repo_220-head.dmp
svnadmin: File not found: revision 219, path
'/qa/trunk/WsV/42TC/Reporting/R_M.js'


I am really confused as to why svn dump is looking to this file in 219th
revision,because this file was created in revision 220.
Can someone guide me through this error so that i can complete my dump
process?

Thanks,
Sunil.

Re: SVNDUMP error

[Andreas Stieger]

Hi,

> On 13 Nov 2014, at 11:10, Manjunath Kashyap  
> wrote:
> I am really confused as to why svn dump is looking to this file in 219th 
> revision,because this file was created in revision 220.

Because of delta encoding for changes and copies referencing a previous source 
which is not found in the previous revision although it should be.

Andreas

Re: SVNDUMP error

[Nico Kadel-Garcia]

On Thu, Nov 13, 2014 at 6:10 AM, Manjunath Kashyap
 wrote:
> Hi All,
>
> We have a svn repo up and running, version svn, version 1.4.2 .
> The svnadmin dump command fails at a particular revision with the below
> error message,

I strongly urge you to prepare to do a forced upgrade. Lock access to
the old repo, it, make a tarball of the old SVN repository, and bring
it over to a system with at least Subverion 1.6, preferably 1.8. 1.4.2
is at least 8 years old, and, and *really* needs an update.

Leave the old one locked and available for legacy, but for
supportability, upgrade ASAP.

Regarding file locking

[Gaurav Singla]

Hi,

I am using TortoiseSVN-1.8.8 as SVN client and VisualSVN-Server-2.7.9 as
server.

I need you help in suggesting a process to get an alert or intimation
whenever any user lock any project file and if another user start working
on the same file he should get an alert/message that this file is already
opened and work is in progress. The aim is to stop the work loss by giving
a warning to the user.

If the user can get any sort of message or alert that partricular file is
already locked, or someone is working on the file, it will help to avoid
the working on same file simultaneously. Please suggest how we can achieve
this.

I understand one of the features is user can lock the file and when any
other user try to commit the same file, sever throw an error message. But
this happens when second user has already make the changes. My aim is to
notify the user at the start not at the time of commit. How we can achieve
this using SVN? Please suggest.

I will appreciate your help on this.

Regards,
Gaurav

Re: Regarding file locking

[Mark Phippard]

See: 

http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html#svn.advanced.locking.lock-communication



> On Nov 13, 2014, at 7:50 AM, Gaurav Singla  wrote:
> 
> Hi,
> 
> I am using TortoiseSVN-1.8.8 as SVN client and VisualSVN-Server-2.7.9 as 
> server. 
> 
> I need you help in suggesting a process to get an alert or intimation 
> whenever any user lock any project file and if another user start working on 
> the same file he should get an alert/message that this file is already opened 
> and work is in progress. The aim is to stop the work loss by giving a warning 
> to the user.
> 
> If the user can get any sort of message or alert that partricular file is 
> already locked, or someone is working on the file, it will help to avoid the 
> working on same file simultaneously. Please suggest how we can achieve this.
> 
> I understand one of the features is user can lock the file and when any other 
> user try to commit the same file, sever throw an error message. But this 
> happens when second user has already make the changes. My aim is to notify 
> the user at the start not at the time of commit. How we can achieve this 
> using SVN? Please suggest.
> 
> I will appreciate your help on this.
> 
> Regards,
> Gaurav 

Tortoise SVN (GPL) & Apache Ant 1.8.x freeware software

[TCO IT Software Mgmt Team]

Dear Team,

Our company users would like to use Tortoise SVN (GPL) & Apache Ant 1.8.x 
freeware software for work related issues.

Do you have any restrictions to use  Tortoise SVN (GPL) & Apache Ant 1.8.x on 
corporate computers.

Could you please advise if you have to buy your products?

Regards,
Zukhra Khamidullina
IT Analyst
Software License management team
TCO IT Planning & PMO
Kazakhstan, Atyrau, 060011,
ATYHQ-234K
*Personal Email: k...@tengizchevroil.com
*Office +7-712-302-1577

Re: Tortoise SVN (GPL) & Apache Ant 1.8.x freeware software

[Ryan Schmidt]

On Nov 13, 2014, at 10:49 PM, TCO IT Software Mgmt Team wrote:
 
> Our company users would like to use Tortoise SVN (GPL) & Apache Ant 1.8.x 
> freeware software for work related issues.
>  
> Do you have any restrictions to use  Tortoise SVN (GPL) & Apache Ant 1.8.x on 
> corporate computers.
>  
> Could you please advise if you have to buy your products?

This mailing list is for Subversion, not Tortoise SVN nor Apache Ant. However, 
I think you'll find that Subversion, Tortoise SVN and Apache Ant are released 
under free software licenses and are thus free and not for sale. Please do 
review each program's license carefully to understand what's permitted. Third 
parties may offer paid support for these products, if that's something you need.

SVN crash

[Helger, Philip]

Dear all!

Please see the attached crash.

// Philip



svn-crash-log20141113103151.dmp
Description: svn-crash-log20141113103151.dmp


svn-crash-log20141113103151.log
Description: svn-crash-log20141113103151.log