From: Juanma Barranquero <lekktu@gmail.com>
To: 16222@debbugs.gnu.org
Subject: bug#16222: Installing ELPA packages complains about :keywords in define-package
Date: Mon, 23 Dec 2013 02:42:57 +0100 [thread overview]
Message-ID: <CAAeL0SSPc8WwkBpZUonh2nMo9OpLj+3BiUd4Q4eU=S2g=zG1cw@mail.gmail.com> (raw)
On Tue, Dec 17, 2013 at 10:06 PM, Stephen Berman <stephen.berman@gmx.net> wrote:
> Leaving directory `/home/steve/.emacs.d/elpa/nlinum-1.1'
> Compiling file /home/steve/.emacs.d/elpa/nlinum-1.1/nlinum-pkg.el at Tue Dec
> 17 13:33:54 2013
> Entering directory `/home/steve/.emacs.d/elpa/nlinum-1.1/'
> nlinum-pkg.el:1:1:Warning: `"convenience"' is a malformed function
> Compiling file /home/steve/.emacs.d/elpa/nlinum-1.1/nlinum.el at Tue Dec 17
> 13:33:54 2013
> Compiling no file at Tue Dec 17 13:36:31 2013
The problem is not nlinum-specific. Installing anything from ELPA
complains about the :keywords in the define-package:
In toplevel form:
debbugs-pkg.el:1:1:Warning: `"comm"' is a malformed function
In toplevel form:
rainbow-mode-pkg.el:1:1:Warning: `"faces"' is a malformed function
etc.
next reply other threads:[~2013-12-23 1:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 1:42 Juanma Barranquero [this message]
2013-12-23 15:02 ` bug#16222: Installing ELPA packages complains about :keywords in define-package Ted Zlatanov
2013-12-23 15:13 ` Juanma Barranquero
2013-12-23 22:57 ` Ted Zlatanov
2013-12-24 0:01 ` Juanma Barranquero
2013-12-24 3:43 ` Stefan Monnier
2013-12-24 13:37 ` Ted Zlatanov
2013-12-24 14:55 ` Stefan Monnier
2013-12-24 15:23 ` Ted Zlatanov
2013-12-24 16:23 ` Stefan Monnier
2014-01-15 5:02 ` Dmitry Gutov
2014-01-15 15:29 ` Stefan Monnier
2014-01-16 12:58 ` Dmitry Gutov
2014-01-16 16:18 ` Stefan Monnier
2014-01-16 17:04 ` Dmitry Gutov
2014-01-20 16:16 ` Ted Zlatanov
2014-01-21 1:58 ` Dmitry Gutov
2014-01-21 13:48 ` Stefan Monnier
2014-01-14 18:16 ` bug#16222: latest js2-mode from elpa causes backtrace during emacs initialization Tom Willis
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='CAAeL0SSPc8WwkBpZUonh2nMo9OpLj+3BiUd4Q4eU=S2g=zG1cw@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=16222@debbugs.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.