From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Gnu Elpa broken
Date: Tue, 05 Sep 2017 08:39:55 -0700 [thread overview]
Message-ID: <87vakx17ec.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87efrljjby.fsf@drachen
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> 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
> | GNUmakefile:178: recipe for target 'packages/counsel-ebdb/counsel-ebdb.elc' failed
> | make: *** [packages/counsel-ebdb/counsel-ebdb.elc] Error 1
There are three ebdb-* packages in elpa that depend on external packages
that are only found in melpa. I didn't realize that elpa packages
couldn't require melpa packages, though I suppose that makes sense.
I can push patches to all three packages using Stefan's (when t ...)
trick right now.
> BTW, does "use [...] locally" mean the server still successfully builds
> all packages?
I'm also curious why this didn't break right away.
Sorry for making a mess.
Eric
next prev parent reply other threads:[~2017-09-05 15:39 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 [this message]
2017-09-05 16:12 ` Eric Abrahamsen
2017-09-05 21:57 ` Stefan Monnier
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=87vakx17ec.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@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.
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.