e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
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 """
|
|
user@system:/path/to/repository$ 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 """
|
|
user@system:/path/to/repository$ git version
|
|
git version 1.7.10.4
|
|
user@system:/path/to/repository$ 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.
|