From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, emacs-devel@gnu.org
Subject: Re: Gnu Elpa broken
Date: Tue, 05 Sep 2017 17:57:57 -0400 [thread overview]
Message-ID: <jwva828n76h.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <87efrljjby.fsf@drachen> (Michael Heerdegen's message of "Tue, 05 Sep 2017 16:44:49 +0200")
>> I use the patch below locally for now.
> FWIW that still gives me
> | In toplevel form:
> | packages/counsel-ebdb/counsel-ebdb.el:29:1:Error: Cannot open load file:
> | No such file or directory, ebdb
That's odd: ebdb *is* in elpa.git, so your Emacs should be able to find
it (assuming you configured package.el to look for packages there, of
course).
> BTW, does "use [...] locally" mean the server still successfully builds
> all packages?
ELPA packages are distributed in source form and compiled on the
end-user's system, where package.el's dependency management should
ensure that pyim and helm are installed before he can install
ebdb-i18n-chn and helm-ebdb.
So, those compilation failures don't affect GNU ELPA.
Stefan
next prev parent reply other threads:[~2017-09-05 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170815220620.32748.5399@vcs0.savannah.gnu.org>
[not found] ` <20170815220621.13CA220C81@vcs0.savannah.gnu.org>
2017-08-15 22:23 ` [elpa] master 31e41ab: Fix up headers for ebdb-i18n-chn Stefan Monnier
2017-08-15 22:29 ` Eric Abrahamsen
2017-08-21 18:04 ` João Távora
2017-08-22 22:57 ` Eric Abrahamsen
2017-09-05 9:11 ` Gnu Elpa broken (was: [elpa] master 31e41ab: Fix up headers for ebdb-i18n-chn) Michael Heerdegen
2017-09-05 13:14 ` Gnu Elpa broken Stefan Monnier
2017-09-05 13:28 ` John Wiegley
2017-09-05 14:44 ` Michael Heerdegen
2017-09-05 15:39 ` Eric Abrahamsen
2017-09-05 16:12 ` Eric Abrahamsen
2017-09-05 21:57 ` Stefan Monnier [this message]
2017-09-05 22:18 ` Eric Abrahamsen
2017-09-05 22:28 ` Stefan Monnier
2017-09-06 11:27 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwva828n76h.fsf-monnier+Inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=michael_heerdegen@web.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.