I am getting this error when I start my emacs. It happens even if I comment out my init.el but not when I use the --no-init-file option.
Any thoughts on how to debug this issue? If this is a an upstream issue, do I need to create a Ticket for that?
This issue was fixed in commit 2db57579b0 of 2018-03-19 by initialising Info-default-directory-list et al. before loading early-init-file.
Now, package-initialize will either be called automatically after loading early-init-file and before loading user-init-file, or you can manually call it in user-init-file. In the latter case, you should set package-enable-at-startup to nil in early-init-file so as to avoid giving rise to the "Unnecessary call to package-initialize in init file" warning.
--no-init-filejust prevents using your init file - any init file you might have somewhere. I don't know why that would be different from having only a commented-out init file. Check whether you might have some other init file, i.e., with one of the other acceptable names. See the Emacs manual, node Init File. – Drew Feb 25 '18 at 16:41eary-init.elchanges. – npostavs Feb 26 '18 at 13:37emacs-develthread: lists.gnu.org/archive/html/emacs-devel/2018-02/msg00532.html. A workaround for now is to setpackage-enable-at-startuptonilin yourearly-init-file. – Basil Feb 26 '18 at 15:01Info-default-directory-listerrors, introduces one suchearly-init-file, and settingpackage-enable-at-startuptonilin this newearly-init-fileis a workaround for the errors for now, if not for the foreseeable future. See(emacs) Early Init Fileand theemacs-develthread I linked. – Basil Feb 26 '18 at 16:02