aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar gjost <gjost@web>2014-06-03 20:20:33 +0000
committerGravatar admin <admin@branchable.com>2014-06-03 20:20:33 +0000
commitd34dce0720c1be5a105a85ee1b9335c6ec3dbf16 (patch)
tree8869ccfbf38cfbbce1ea315c365f2dd0aec9ae3d
parent9c5dc98e13b739e703869baaaaf275f27835e371 (diff)
-rw-r--r--doc/bugs/unwanted_repository_version_upgrades.mdwn25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/bugs/unwanted_repository_version_upgrades.mdwn b/doc/bugs/unwanted_repository_version_upgrades.mdwn
new file mode 100644
index 000000000..566a94192
--- /dev/null
+++ b/doc/bugs/unwanted_repository_version_upgrades.mdwn
@@ -0,0 +1,25 @@
+Is it possible to freeze or peg repositories at a particular version, or to prevent automatic repository version upgrades? 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.