diff options
| author |  gjost <gjost@web> | 2014-06-03 20:18:40 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-06-03 20:18:40 +0000 |
| commit | 9c5dc98e13b739e703869baaaaf275f27835e371 (patch) | |
| tree | e26434ebed0fd1d9aeb95a3f3ef5e910f3acfcc0 | |
| parent | f7e2192e65ee777886a8d72e767e7105cf32448a (diff) | |
removed
| -rw-r--r-- | doc/bugs/Possible_to_peg_repositories_to_annex_version__63__.mdwn | 25 |
1 files changed, 0 insertions, 25 deletions
diff --git a/doc/bugs/Possible_to_peg_repositories_to_annex_version__63__.mdwn b/doc/bugs/Possible_to_peg_repositories_to_annex_version__63__.mdwn deleted file mode 100644 index b566fe7d7..000000000 --- a/doc/bugs/Possible_to_peg_repositories_to_annex_version__63__.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -Is it possible to freeze or peg repositories at a particular version, or at least require confirmation before being upgraded? Is it possible to "downgrade" a repository? - -### Please describe the problem. - -We have a number of repositories on a shared file server. These repositories are accessed by multiple machines. Some of these repositories appear to have gotten upgraded and are now unusable on machines running older versions of git-annex. - -We're getting this message: -[[!format sh """ -densho@kinkura:/media/qnfs/kinkura/gold/ddr-janm-1$ git annex status -git-annex: Repository version 5 is not supported. Upgrade git-annex. -"""]] - -The machine experiencing the problem is running Debian Wheezy (Stable). -[[!format sh """ -densho@kinkura:/media/qnfs/kinkura/gold/ddr-janm-1$ git version -git version 1.7.10.4 -densho@kinkura:/media/qnfs/kinkura/gold/ddr-janm-1$ git annex version -git-annex version: 3.20120629 -local repository version: 5 -default repository version: 3 -supported repository versions: 3 -upgrade supported from repository versions: 0 1 2 -"""]] - -I'm guessing that one of the machines with access to this repository was running a newer version of git-annex, and that the repository was upgraded in the course of some action. |