diff options
| -rw-r--r-- | doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn | 5 | ||||
| -rw-r--r-- | doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn | 35 | ||||
| -rw-r--r-- | doc/install/Debian.mdwn | 6 |
3 files changed, 46 insertions, 0 deletions
diff --git a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn new file mode 100644 index 000000000..7874ea696 --- /dev/null +++ b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed.mdwn @@ -0,0 +1,5 @@ +All builds of git-annex should be cryptographically signed. Especially the automatic upgrades. + +Signing doesn't minimise the likelihood of unwanted software being installed, but it helps reduce it. + +*Please* Joey... diff --git a/doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn b/doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn new file mode 100644 index 000000000..3e917cc41 --- /dev/null +++ b/doc/bugs/Backup_repository_doesn__39__t_get_all_files.mdwn @@ -0,0 +1,35 @@ +### Please describe the problem. +Backup group repositories don't download all "unused" files when running the webapp. + + +### What steps will reproduce the problem? +Run the webapp, set up two local repositories: + +1 - Use this for testing, set to manual type + +2 - Use for backups, set to full backup type + +Create some files, change them, etc. See that files and history get transferred from #1 --> #2 + +Change #2 to being "don't sync". For example, you are running out of disk space, or are off the network. + +Edit a file in #1 a couple of times. Now change #2 to synchronise. + +Now, #2 will reflect #1 in the current state. + +Stop the annex assistant. + +Change #2 to being indirect mode. Try to checkout a previous revision. There will be broken symlinks. git annex get will fail with "no copies of this file" type errors. + + +My expectation (incorrectly?) was that all the "history" of my files would be automatically transferred to the backup group repos. It seems only the git commits are transferred, but the "unused" file content isn't. + +--- + +What this tells me is that any changes that occur whilst I am not networked are entirely localised to my machine. If this is the design expectation, can we squash commits before sending them? There seems to be no point in having commits pointing to file content that has no chance of being accessed. + + +### What version of git-annex are you using? On what operating system? +git-annex version: 5.20131130-gc25be33 + + diff --git a/doc/install/Debian.mdwn b/doc/install/Debian.mdwn index c71d4d244..f51640e4d 100644 --- a/doc/install/Debian.mdwn +++ b/doc/install/Debian.mdwn @@ -13,6 +13,12 @@ Follow the instructions to [enable backports](http://backports.debian.org/Instru sudo apt-get -t wheezy-backports install git-annex +For the latest version [download the prebuilt linux tarball](http://downloads.kitenet.net/git-annex/linux/current/), extract it and add it to your path. +Please note that you might need to run this first: + + sudo apt-get install libgsasl7 + + ## Debian 6.0 "squeeze" Follow the instructions to [enable backports](http://backports.debian.org/Instructions/). |