all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23927@debbugs.gnu.org, Live System User <nyc4bos@aol.com>
Subject: bug#23927: 25.0.94; Errors when updating using package.el
Date: Sat, 09 Jul 2016 20:51:52 -0400	[thread overview]
Message-ID: <ninwexql3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83twfzgtx6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Jul 2016 10:19:33 +0300")

Eli Zaretskii wrote:

>> 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. 

The above error actually means that the first "info.el" found in
load-path did not "(provide 'info)", not that no "info.el" was found.

> But why and how could that happen?

The OP has some broken info.el early in their load-path, presumably one
that isn't part of Emacs.

> A typo?  From package.el:

Looks like a clear typo.

>   (defface package-status-built-in

It is a shame this was named "built-in" (with hyphen), when compared to
the long-standing "font-lock-builtin-face" (without hyphen) from which
it inherits.





  reply	other threads:[~2016-07-10  0:51 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
2016-07-10  0:51   ` Glenn Morris [this message]
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=ninwexql3.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=23927@debbugs.gnu.org \
    --cc=eliz@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.