From: Eli Zaretskii <eliz@gnu.org>
To: Live System User <nyc4bos@aol.com>
Cc: 23927@debbugs.gnu.org
Subject: bug#23927: 25.0.94; Errors when updating using package.el
Date: Sat, 09 Jul 2016 10:19:33 +0300 [thread overview]
Message-ID: <83twfzgtx6.fsf@gnu.org> (raw)
In-Reply-To: <87mvlrphs0.fsf@aol.com> (message from Live System User on Sat, 09 Jul 2016 00:17:03 -0400)
> From: Live System User <nyc4bos@aol.com>
> Date: Sat, 09 Jul 2016 00:17:03 -0400
>
> When updating a package `(package-menu-mark-upgrades)',
> I got the following errors/warnings:
>
> package-activate-1: Required feature ‘info’ was not provided
A recipe to reproduce this will be appreciated. The 'info' feature
comes with Emacs, so the only way I could understand how this can
happen is that somehow load-path doesn't include the standard
directories when this code is run. But why and how could that happen?
> Invalid face reference: package-status-builtin-face
> Invalid face reference: package-status-builtin-face [3 times]
A typo? From package.el:
(defface package-status-built-in
^^^^^^^^^^^^^^^^^^^^^^^
'((t :inherit font-lock-builtin-face))
"Face used on the status and version of built-in packages."
:version "25.1")
(defface package-status-external
'((t :inherit package-status-builtin-face))
^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Face used on the status and version of external packages."
:version "25.1")
Would package.el gurus please take a look at this? These sound like
very basic problems in package.el, so I'd hate to release 25.1 with
them.
next prev parent reply other threads:[~2016-07-09 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 4:17 bug#23927: 25.0.94; Errors when updating using package.el Live System User
2016-07-09 7:19 ` Eli Zaretskii [this message]
2016-07-10 0:51 ` Glenn Morris
2016-07-12 21:52 ` Live System User
2016-07-13 17:14 ` Glenn Morris
2016-07-13 20:49 ` Clément Pit--Claudel
2016-07-13 20:57 ` Glenn Morris
2016-07-13 21:53 ` Clément Pit--Claudel
2016-07-12 21:21 ` Live System User
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=83twfzgtx6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23927@debbugs.gnu.org \
--cc=nyc4bos@aol.com \
/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.