From users-return-16671-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Wed Nov 14 05:42:57 2012 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9605AD6FE for ; Wed, 14 Nov 2012 05:42:57 +0000 (UTC) Received: (qmail 38416 invoked by uid 500); 14 Nov 2012 05:42:56 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 38332 invoked by uid 500); 14 Nov 2012 05:42:55 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Delivered-To: moderator for users@subversion.apache.org Received: (qmail 21192 invoked by uid 99); 14 Nov 2012 03:55:29 -0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kessler@cs.utah.edu designates 155.98.64.241 as permitted sender) X-Virus-Scanned: amavisd-new at cs.utah.edu From: "Robert R. Kessler" Content-Type: multipart/alternative; boundary="Apple-Mail=_E367E53D-1ACD-452E-A473-656C0D1FE18D" Subject: Problem with an archive Message-Id: Date: Tue, 13 Nov 2012 20:54:56 -0700 To: users@subversion.apache.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_E367E53D-1ACD-452E-A473-656C0D1FE18D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I am not a subscriber so please cc: me on any responses. I appreciate = it=85. Now to the issue: I have an svn archive that a student of mine was using in March. I am = trying to access the files in the archive, however, when I try to access = it, I get the following error: Found format '5', only created by unreleased dev builds. The release notes say that it is because I am using an archive that was = created with the 1.7 alpha3 version. I tried going back to previous versions of tortoisesvn to see if I might = find one that has the 1.7 alpha3 version so I could unpack the svn and = get the files back. Unfortunately, their various beta and rc versions = did not have the correct subversion version. The suggestion from the tortoisesvn mailing list is that if I get the = 1.7 alpha3 version, I can use svnadmin to extract the files and then = reload them into a valid system. Unfortunately, I have not been able to find an archived download of the = 1.7 alpha3 version in order to try to see if the svnadmin extraction = will work. Does anyone have a copy of that version so I can give this a shot. We have not been able to find any other way to get access to the files = in there and they are very important. =20 BTW - I am not convinced that this will solve our problem, but it is the = next step to try. It doesn't make sense that he was using the latest = svn version and was using the alpha3 release in March of this year when = it was out in mid 2011. It feels like something else is goofed up with = this archive. Thanks for anyone that can help us. Bob. --Apple-Mail=_E367E53D-1ACD-452E-A473-656C0D1FE18D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Found format '5', only created = by unreleased dev builds.

The release notes say that it is because I am = using an archive that was created with the 1.7 alpha3 = version.

I tried going back to previous = versions of tortoisesvn to see if I might find one that has the 1.7 = alpha3 version so I could unpack the svn and get the files back. = Unfortunately, their various beta and rc versions did not have the = correct subversion version.

The = suggestion from the tortoisesvn mailing list is that if I get the 1.7 = alpha3 version, I can use svnadmin to extract the files and then reload = them into a valid system.

Does anyone have a copy of that = version so I can give this a shot.

We have not been able to find any other way to get = access to the files in there and they are very important. =

BTW - I am not convinced that = this will solve our problem, but it is the next step to try. It doesn't = make sense that he was using the latest svn version and was using the = alpha3 release in March of this year when it was out in mid 2011. It = feels like something else is goofed up with this = archive.

Thanks for anyone that can help = us.

Bob.