branch: elpa-admin
commit 63888f319c5597226e506bbe1c615f506ad09f77
Author: Paul Eggert <egg...@cs.ucla.edu>
Commit: Paul Eggert <egg...@cs.ucla.edu>
Warn about transfer.fsckObjects
---
README | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/README b/README
index a1d6fd3..4318bad 100644
--- a/README
+++ b/README
@@ -267,7 +267,7 @@ packages/ directory. You can then add that directory, e.g.
with:
** To deploy the package repository as a remotely-accessible archive:
- git clone .../elpa
+ git -c fetch.fsckObjects=false clone .../elpa
(cd elpa; git clone .../emacs) #If you want to generate :core packages.
mkdir build
cd build
@@ -278,7 +278,9 @@ packages/ directory. You can then add that directory, e.g.
with:
This deploys the packages to the staging/ directory (sibling of "build").
Unlike "make", this makes a full copy of the packages, tars up
-multi-file packages, and doesn't byte-compile any files.
+multi-file packages, and doesn't byte-compile any files. The
+fetch.fsckObjects setting works around a glitch in the ELPA repository
+<https://debbugs.gnu.org/22690>.
** To access a deployed archive
