purcell / emacs.d

An Emacs configuration bundle with batteries included
BSD 2-Clause "Simplified" License
6.85k stars 2.05k forks source link

Error during initalization "Wrong type argument" listp, tomorrow #865

Closed Invarianz closed 4 days ago

Invarianz commented 4 days ago

I was in the process of setting up your Emacs config on a Ubuntu 24.04 machine.

When the config is loaded emacs fails with the following backtrace:

Debugger entered--Lisp error: (wrong-type-argument listp tomorrow)
  package-desc-from-define("color-theme-sanityinc-tomorrow" "20240621.1005" "A version of Chris Kempson's " tomorrow " themes." '((emacs "24.1")) :url "https://github.com/purcell/color-theme-sanityinc-t..." :commit "ddf2920a8866040e57359d2e1c5517fffcad2e38" :revdesc "ddf2920a8866" :keywords '("faces" "themes") :authors '(("Steve Purcell" . "steve@sanityinc.com")) :maintainers '(("Steve Purcell" . "steve@sanityinc.com")))
  package-process-define-package((define-package "color-theme-sanityinc-tomorrow" "20240621.1005" "A version of Chris Kempson's " tomorrow " themes." '((emacs "24.1")) :url "https://github.com/purcell/color-theme-sanityinc-t..." :commit "ddf2920a8866040e57359d2e1c5517fffcad2e38" :revdesc "ddf2920a8866" :keywords '("faces" "themes") :authors '(("Steve Purcell" . "steve@sanityinc.com")) :maintainers '(("Steve Purcell" . "steve@sanityinc.com"))))
  package-load-descriptor("/home/groessingp/.emacs.d/elpa-29.3/color-theme-sa...")
  package-load-all-descriptors()
  package-initialize()
  load-with-code-conversion("/home/groessingp/.emacs.d/lisp/init-elpa.el" "/home/groessingp/.emacs.d/lisp/init-elpa.el" nil t)
  #<subr require>(init-elpa)
  apply(#<subr require> init-elpa nil)
  (prog1 (apply orig feature args) (if (and (not already-loaded) (memq feature features)) (progn (let ((time (sanityinc/time-subtract-millis (current-time) require-start-time))) (add-to-list 'sanityinc/require-times (list feature require-start-time time) t)))))
  (let* ((already-loaded (memq feature features)) (require-start-time (and (not already-loaded) (current-time)))) (prog1 (apply orig feature args) (if (and (not already-loaded) (memq feature features)) (progn (let ((time (sanityinc/time-subtract-millis ... require-start-time))) (add-to-list 'sanityinc/require-times (list feature require-start-time time) t))))))
  sanityinc/require-times-wrapper(#<subr require> init-elpa)
  apply(sanityinc/require-times-wrapper #<subr require> init-elpa)
  require(init-elpa)
  load-with-code-conversion("/home/groessingp/.emacs.d/init.el" "/home/groessingp/.emacs.d/init.el" t t)
  load("/home/groessingp/.emacs.d/init" noerror nomessage)
  startup--load-user-init-file(#f(compiled-function () #<bytecode -0x11489325849cd4eb>) #f(compiled-function () #<bytecode -0x1f3c61addc0acb35>) t)
  command-line()
  normal-top-level()

From my little understanding of Elisp it seems that the "tomorrow" string in the description of the theme package is interpreted wrongly. I'm running this behind a proxy. So before launching Emacs and loading your config, I add the following in init.el:

;; Bootstrap config
(require 'init-proxy)
(setq custom-file (locate-user-emacs-file "custom.el"))

with the following content:

;;; init-proxy.el --- Proxy Support -*- lexical-binding:t -*-
;;; Commentary:
;;; Code:

(setq url-proxy-services
            '(("no_proxy" ."^\\(localhost\\|10.*\\)")
                  ("http" . "10.62.39.85:3128")
                      ("https" . "10.62.39.85:3128")))

(provide 'init-proxy)
;;; init-proxy.el ends here

The proxy does not need authentication and the file is located in lisp/init-proxy.el.

I somehow can't imagine that the proxy is the issue, however can't run the above backtrace in an open network right now.

Thanks!

purcell commented 4 days ago

Ah, that looks like an instance of a bug in package-build that affected packages with double-quotes in their descriptions: the MELPA packages for such packages are uninstallable as a result, but they should get rebuilt soon.

Invarianz commented 4 days ago

Thanks for the quick response. The issue you're referring to is exactly related to my problem. As far as I can see the rebuilds on MELPA are complete and my distribution initializes without an issue!

purcell commented 4 days ago

Great! Glad it's working for you now. Happy tinkering! 😄