[Scst-devel] How to update SCST after the SourceForge outage

[Bart V. A. <bar...@sa...>]

Hello,

If an the error message "no such revision" appears when running "svn 
update" then you will have to delete and re-checkout the SCST source 
tree. This is a consequence of the recent SourceForge outage. Regarding 
the missing revisions mentioned in the e-mail below: I have checked the 
Subversion log but I think these revisions were restored correctly. The 
diff tool tells me that the source code present in the SourceForge SCST 
repository is identical to what was present before the outage.

Best regards,

Bart.


-------- Forwarded Message --------
Subject: SourceForge SVN repository data gap notification for project scst
Date: 07/26/2015 03:46 PM
From: SourceForge Support <no...@so...>
To: bva...@ac... <bva...@ac...>

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:
http://sourceforge.net/blog/sourceforge-infrastructure-and-service-restoration-update-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, scst, 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: 6427
Current revision in database: 6428

Recent commit events tracked in database:
r6420	bvassche	Tue Jul 14 2015 18:26:39 GMT+0000 (UTC)	/etc/init.d/scst: 
Avoid that starting SCST fail...
r6421	bvassche	Tue Jul 14 2015 21:50:54 GMT+0000 (UTC)	iscsi-scst: Fix 
parameter order in a debug stat...
r6422	bvassche	Tue Jul 14 2015 21:52:43 GMT+0000 (UTC)	scst_targ: Kernel 
4.2 build fix
r6423	bvassche	Tue Jul 14 2015 22:50:27 GMT+0000 (UTC)	ib_srpt: Linux 
kernel v4.2 build fix
r6424	bvassche	Tue Jul 14 2015 23:24:28 GMT+0000 (UTC)	ib_srpt: Test 
whether ib_create_send_mad() need...
r6425	bvassche	Tue Jul 14 2015 23:47:52 GMT+0000 (UTC)	isert-scst: 
Kernel v4.2 build fix
r6426	bvassche	Tue Jul 14 2015 23:49:52 GMT+0000 (UTC)	ib_srpt: Linux 
kernel v4.2 ib_create_cq() build...
r6427	bvassche	Tue Jul 14 2015 23:57:43 GMT+0000 (UTC)	isert-scst: Linux 
kernel v4.2 ib_create_cq() bu...
r6428	bvassche	Wed Jul 15 2015 16:42:36 GMT+0000 (UTC) 
scripts/specialize-patch: Handle #if 0 / #elif ...


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.

If you have any follow-up questions or concerns, please contact the
SourceForge Support team by submitting a ticket at:
https://sourceforge.net/p/forge/site-support/new/

Thank you,

SourceForge Support