Hello,
Below are some changes to the XEmacs Web Site that explain problems in
package updates.
-- When one has still EFS 1.32 installed, fetching the package index
aborts due to EFS not knowing about Extended Passive Mode used by
ftp.xemacs.org and others.
-- When one has GPG installed, one needs to either get Norbert's key
or to manually unset package index verification. The change below
explains it.
I did make validate, FYI.
Cheers,
Joachim
PS: I used Patcher to create this email. It was my first time to use
it; hope it's like you want. E.g., do you really want
:change-logs-appearance as 'verbatim and not as 'patch?
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: jschrod(a)acm.org
Kranichweg 1 Tel.: +49-6074-861532
63322 Rödermark, Germany Fax: +49-6074-861531
Documentation/ChangeLog addition:
2005-01-29 Joachim Schrod <jschrod(a)acm.org>
* packageGuide.content: Describe EFS problem with Extended Passive
Mode (solved in efs-1.33). Describe how to handle package index
verification if Norbert's key is not installed.
Install/ChangeLog addition:
2005-01-29 Joachim Schrod <jschrod(a)acm.org>
* index.content: Refer to packageGuide in case of GPG problems.
XEmacs Web Site source patch:
Diff command: cvs -q diff -u
Files affected: Install/index.content Documentation/packageGuide.content
Index: Documentation/packageGuide.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Documentation/packageGuide.content,v
retrieving revision 1.29
diff -c -1 -u -r1.29 packageGuide.content
cvs server: conflicting specifications of output style
--- Documentation/packageGuide.content 2004/12/10 00:25:47 1.29
+++ Documentation/packageGuide.content 2005/01/29 18:02:35
@@ -413,2 +413,3 @@
a corresponding copy of the package index there.</li>
+
<li>Invoke <strong>Tools->Packages->List and
Install</strong>
@@ -418,8 +419,70 @@
XEmacs will now first try to fetch a new version of
- the package index from the FTP site. Depending on whether you
- are using <strong>mailcrypt/PGP</strong>, you will get some question
- about keys to fetch or whether to use the index without
- verifying the signature. If the new index was different from the
- one already on disk, XEmacs will offer you to overwrite the old
- index.</li>
+ the package index from the FTP site.
+ <ul>
+ <li>If you get the error message <code>Error in process
+ filter: (ftp-error FTP Error: ... 229 Entering Extended
+ Passive Mode ...</code>, your efs is too old. You need to set
+ <code>efs-use-passive-mode</code> to <code>t</code>, or use
+ the menu <strong>Options -> Customize -> Emacs ->
+ Files -> Efs -> Parameters -> Efs Use Passive
+ Mode</strong>, turn the option on, click on
+ <code>Set</code> and <code>Done</code>.
+ <br/>
+ Now you need to terminate the current ftp connection; do
+ that with <code>C-x k *ftp TAB RET</code>. Start
+ <strong>List and Install</strong> again.</li>
+ <li>You might be asked if an old package index shall be
+ overwritten, or if an index shall be created in
+ <code>~/.xemacs</code>, maybe it will ask to create this
+ directory. You will also be asked if you want to load the
+ package database. Confirm all those questions.</li>
+ <li>When you have <strong>mailcrypt</strong> and GPG or PGP
+ installed, XEmacs will try to verify the downloaded package
+ index.
+ <ul>
+ <li>If you have GPG installed, you might get the error
+ message <code>Can't check signature: Public key
+ 82EDF2C1D1DD84CD not found</code>. (The key id might be
+ different.) Then you don't have the public key of the
+ person who signed the package index - at time of this
+ writing, Norbert Koch.
+ <br/>
+ Enter the following command on the command line:
+ <pre>gpg --keyserver
hkp://wwwkeys.pgp.net --recv-key
82EDF2C1D1DD84CD</pre>
+ (Of course, you need to use the public key id
+ from XEmacs' error message in the gpg command.) You will
+ get a warning that the HKP interface is experimental -
+ don't worry, it works. Then comes the message that a
+ public key got imported.
+ <br/>
+ If your command hangs, there might be several
+ possibilites. One of the key servers might not be
+ reachable; stop the command with Ctrl-C and issue it
+ again. If it still hangs, your firewall might forbid
+ outbound connections to the key servers. Then fetch <a
+
href="http://ftp.xemacs.org/pgp-keys/norbert_koch.asc">http:...;,
+ save it to a file, and call <code>gpg --import</code>
+ with that file.
+ <br/>
+ Update your package index again; this time it'll
+ finish with the message `<code>Updated package
+ database</code>'.
+ <br/>
+ If you get the message `<code>The message was
+ corrupt</code>', try again updating the package index.
+ </li>
+ <li>If you have PGP installed, confirm the question that
+ keys shall be fetched.</li>
+ <li>If you still have problems with package index
+ verification, use Customize to turn off
+ <code>package-get-require-signed-base-updates</code>.
+ (By menu, that's <strong>Options -> Customize ->
+ Emacs -> Package Tools -> Package Get ->
+ Require Signed Base Updates</strong>.) But this should
+ be the last resort, as verifying downloads is an
+ important security measure.</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
Index: Install/index.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Install/index.content,v
retrieving revision 1.32
diff -c -1 -u -r1.32 index.content
cvs server: conflicting specifications of output style
--- Install/index.content 2004/12/10 00:25:10 1.32
+++ Install/index.content 2005/01/29 18:02:36
@@ -239,5 +239,8 @@
-> List and Install</strong>. This will download the
- most recent package index (PGP errors may occur and can be
- ignored) and list the packages available for
- install. Instructions and key bindings for this buffer are at
+ most recent package index and list the packages available for
+ install. If you get PGP or GPG errors (``<code>Can't check
+ signature...</code>''), refer to the description in the <a
+ href="<!-- _GP_ relPath(qq{Documentation/packageGuide.html})
+ -->">package guide</a> how to resolve them.
+ Instructions and key bindings for this buffer are at
the bottom; use the scroll bar to view them. If in doubt about a