Thanks very much for your efforts! Very much appreciated.

J.

On Oct 8, 2009 1:54 PM, "FND" <f...@gmx.net> wrote:

> The proper recovery is in progress: >
http://support.unamesa.org/message/view/TiddlyWiki.org/1495...
We have been working hard to restore everything back to normal. I'll
elaborate below. UnaMesa will follow up with more details, including the
steps they are taking to prevent similar incidents in the future.

In short:
* No code was lost.
* A few minor commit messages were lost.
* Some Trac data (ticket changes, wiki edits) might remain lost.

The most recent backups had been corrupted. The latest valid backups
were taken on Sept. 6. Luckily, I had a local Git clone of the
Subversion repository containing all files' latest state as of Oct. 3
and including the commit history starting from Sept. 11.

Thus about 50 commits (between Sept. 7-10) had to be combined into one a
single commit:
    http://trac.tiddlywiki.org/changeset/10612
The files listed in that commit suggest that there were no important
commit messages during that period.

The remaining commits (Sept. 11 to Oct. 3) were then reapplied.

As for Trac, unfortunately we'll have to manually restore the tickets
and wiki edits from that four-week period.
For that we're resorting to using Google's cache and our feed readers'
archives of the Trac timeline feed. This record is not complete (e.g.
new and closed tickets are covered, but not all ticket changes), so any
suggestions on alternative avenues would be most welcome.

-- F. --~--~---------~--~----~------------~-------~--~----~ This message is
part of the topic "s...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to tiddlywikidev@googlegroups.com
To unsubscribe from this group, send email to 
tiddlywikidev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to