From: mf_tech <mf_tech@mathiasfoehr.lu>
To: <help-gnu-emacs@gnu.org>
Subject: difficulties to use ELPA while MELPA working as expected
Date: Mon, 13 Apr 2020 21:08:57 +0200 [thread overview]
Message-ID: <051DAC03-30E6-4A48-A7B3-9FFB7731B55C@mathiasfoehr.lu> (raw)
Dear Emacs Helper Team,
**Summary** On a **Debian "Stable"** installation, it is possible
without difficulty to **install packages from Melpa but not from Elpa**.
Furthermore, the command **package-list works with ELPA**, an
installation request can be submitted.
It does not seem to be related to communication difficulties.
This is the recurring answer; I want to install **delight** which I
unfortunately I need to use.
**Contacting host: elpa.gnu.org:443**
**package-install-from-archive:
https://elpa.gnu.org/packages/auto-correct-1.1.4.el: Bad Request**
The Melpa installation works after .emacs has been minimally adapted as
suggested by https://melpa.org/#/getting-started
Elpa installation does not work, neither via package-install nor via
package-list. This happens even without the .emacs file
This problem is reproducible on two logically nearly identical machines.
There are some complains on the Web about this problem, but I have not
seen any solution.
**Installation**
uname -a
**Linux hercules 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26)
x86_64 GNU/Linux**
emacs starting page
**This is GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version
3.24.5)
of 2019-09-23, modified by Debian**
Could it be that this is a Debian bug ? It looks unprobable, but I
cannot appreciate.
Thanks for your help and best regards
Mathias
next reply other threads:[~2020-04-13 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 19:08 mf_tech [this message]
2020-04-13 21:12 ` difficulties to use ELPA while MELPA working as expected Noam Postavsky
2020-04-19 14:24 ` mf_tech
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=051DAC03-30E6-4A48-A7B3-9FFB7731B55C@mathiasfoehr.lu \
--to=mf_tech@mathiasfoehr.lu \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).