forum for navit navigation tool
It is currently 15 Oct 2021, 20:49
View unanswered posts | View active topics

All times are UTC

Forum rules

Feel free to ask anything here related to the development process - coding, creating new features, fixing bugs and custom changes of Navit.

Note: For reporting bugs, use the bug tracker.

Post new topic Reply to topic  [ 2 posts ] 
Author Message
 Post subject: SourceForge outage and lost Subversion commit
PostPosted: 29 Jul 2015, 21:28 

Joined: 23 Jun 2013, 20:15
Posts: 65
Location: Essen, Germany
As most of you probably noticed, SourceForge, which still hosts our Subversion repository had a major outage, lasting from 16 to 28 July. While everything is back up now (see ), I received a mail from SourceForge telling me one Subversion commit was lost (see below for full mail).

The lost commit is (was) revision 6128, "Update:Vehicle:handle gpsd >= 3.11, thanks greg..."

The question is: How do we restore this? The commit is still present in the GitHub repo at , however the SourceForge SVN repo received another commit in the meantime (see ), meaning the SVN repo and GitHub have now diverged.

Should we just add the missing commit to the SVN repo (as a new commit)? How will the GitHub repo be re-synchronized?

Mail from SourceForge

Date: Sun, 26 Jul 2015 22:41:54 +0000
From: SourceForge Support <>
Subject: SourceForge SVN repository data gap notification for project navit

SourceForge experienced a storage fault on 2015-07-16. Service restoration
has been in-progress since that time, and our latest full status update is online at: ... e-for-724/

Subversion data has generally been restored to the 2015-07-14 backup. We have identified
497 Subversion repositories which received commits after 2015-07-13 and before the storage fault.
Your project, navit, is one of those repositories.

To determine which repositories are missing recent commits, we compared the
revision count currently in your repository on disk (Current revision on disk)
to the revision count seen by our repository tracking (Current revision in database).
The repository tracking database does not house a full copy of your commit data.
We determined data needed to be committed again because the Current revision
on disk is less than the Current revision in database.

Analysis of your repository compared to our SCM repository tracking data shows:
Current revision on disk: 6127
Current revision in database: 6128

Recent commit events tracked in database:
r6127 userid-1700563 Tue Jul 14 2015 23:04:07 GMT+0000 (UTC) Fix:Core:Merge Robotaxi's PR for imperial units
r6128 userid-1700563 Thu Jul 16 2015 01:46:09 GMT+0000 (UTC) Update:Vehicle:handle gpsd >= 3.11, thanks greg...

Since commits were made to your repository after our restore point, it will be necessary
for you to coordinate within your team to ensure these changes are recommitted.

We recommend you make a backup of your existing repository checkout, then make
a fresh checkout of the repository in another directory, copy over any changes
and commit. Depending on the number of developers on your team and the granularity
of change tracking you need for these uncommitted changes, you may need to tune
this process for your project. Please coordinate with the other developers on
your project team before committing.

 Post subject: Re: SourceForge outage and lost Subversion commit
PostPosted: 29 Jul 2015, 22:43 
User avatar

Joined: 07 Jun 2013, 17:13
Posts: 146
Location: Tartu, Estonia
I think we should use this opportunity to finally discard the SVN repository and switch to GitHub, as Kazer proposed. I guess this would be easier that fiddling around with some sort of synchronization.

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Silver Orange 2.0.6 for IPB Designed by Skins and Hosting
Converted for phpBB3, based on Royal Blue template by BigB © 2007 2008 AEON KINGS