From users-return-27034-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Tue Apr 10 22:09:23 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 582E818064C for ; Tue, 10 Apr 2018 22:09:23 +0200 (CEST) Received: (qmail 77476 invoked by uid 500); 10 Apr 2018 20:09:22 -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 Received: (qmail 77460 invoked by uid 99); 10 Apr 2018 20:09:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2018 20:09:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CF33518051A for ; Tue, 10 Apr 2018 20:09:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.121 X-Spam-Level: X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=visualsvn.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id t6kWKJlr9bA9 for ; Tue, 10 Apr 2018 20:09:20 +0000 (UTC) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9AAB45F666 for ; Tue, 10 Apr 2018 20:09:19 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id b127so28747620wmf.5 for ; Tue, 10 Apr 2018 13:09:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=visualsvn.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YMmgyC91plblFfn7QiAwvixL9S1fV7UTojWoGgtlHpA=; b=QOMeQbTQ22rDbfEV+3niQR8F0Vq8kzbtzhLAy+ZV4xAv9wSNJyz+sQ3W0Gq9oANzCc nLx0FOBtE6dI/CeAU5ZPMz54ZljOe05/Gh9EMIJQZokyev4xtdhf3mqwIaTmwPeyuGy0 1GGtpxM/4CuigTxPsIQ6no6uovVNYWguyOq00= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YMmgyC91plblFfn7QiAwvixL9S1fV7UTojWoGgtlHpA=; b=ObwT/DMhEaZ6FmgaqJ3WyN++cDZtl5hLjFs3WvXelOis7t991T+rqb31JcMyFDHlLW HfOC910v2DQ7oBohdW4ucfqWuiUBdFFlSL7sslkcZsh6U8PYWvylv9TCLkFku8IsxWtV 5b7zAW/W4+6BIwc3VjN3Golio6/7NGY5jwfPn14aWfWUE3TeQ4wN/N7c0zi4Uxde4xBJ TRub891doP89aJ5IOe2JIqCuUIRUDmrRQaDOItmWWciTx06xpwA0d7j3v2IvWC9SRcAm aqUC3OGixEIkzNhNkp9qAIMsdB0j4d8sgNbAAU3XJ99k1mCnlsT+3kiQOoNnPl8Ca7Li LFEA== X-Gm-Message-State: ALQs6tAlqjL0cZhkmbUI47B7j4/ZvygIw9GCT1an5Tg6IRBGAQtXv1CS ceAAbCrXJCEcaihZmauewC+5j0kmYDYpecl+RQjbsg== X-Google-Smtp-Source: AIpwx4/J1VQeg4IKgqsrhtFzku7yU9NKtuzqoKG+ZW95hMyu9+lLpVxg08MASu8XYMIvALowVjGr+1bV45nJ0bB+WAs= X-Received: by 10.28.23.21 with SMTP id 21mr562898wmx.49.1523390958451; Tue, 10 Apr 2018 13:09:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.192.8 with HTTP; Tue, 10 Apr 2018 13:08:57 -0700 (PDT) In-Reply-To: References: From: Evgeny Kotkov Date: Tue, 10 Apr 2018 23:08:57 +0300 Message-ID: Subject: Re: Accessing really old SVN repo To: Zow Terry Brugger Cc: users@subversion.apache.org Content-Type: text/plain; charset="UTF-8" Terry Brugger writes: > Any thoughts on how I can access this repo? If it looks like something > broken, how about at least accessing the HEAD? Subversion 1.9.3 had a bug where it made incorrect assumptions about old repositories without a "db/format" file. This is the most likely cause for the errors you're seeing. This bug has been fixed starting from version 1.9.5, so you might want to try accessing the repository with a more recent version. Alternatively, you should be able to use any of the 1.8.x versions, as they didn't have this bug. If using a different version is unfeasible for any reason, you can try a workaround by manually creating a "db/format" file containing "1\n" within your repository. Also, please note that dump and load is not required to access your data (even for old repositories) with newer versions of Subversion, as these newer versions are fully compatible with all previous repository formats and can both read and write to them. Hope this helps! Regards, Evgeny Kotkov