Context: I was using debian 12 with KDE Plasma, long story short I have to reinstall debian 12 with xfce, I use the same configuration file for emacs (it used to work fine in debian 12 with KDE) but in this new debian I got this message:

Warning (Emacs): elpaca version mismatch

Note 2: I didnt install emacs from the debian repositories because they dont have the version 29.1 so I compile myself the source.

  • ragnese@alien.topBEnglish
    1·
    11 months ago

    Remember when you first setup elpaca in your init.el and you copy+pasted a big block of elisp from elpaca’s documentation? That elpaca setup code has a version-number variable that it sets. When you initialized your new Emacs instance, it installed elpaca from MELPA, but the version on MELPA is a newer version than your copy+pasted code from elpaca’s docs. The solution is to replace your copy+pasted code by copy+pasting the new code in elpaca’s docs.

    • nv-elisp@alien.topBEnglish
      1·
      11 months ago

      [The Elpaca installer] has a version-number variable that it sets. […] The solution is to replace [the installer with] the new code in elpaca’s docs

      This is correct. For anyone troubleshooting Elpaca, there is a Wiki which covers this warning.

      When you initialized your new Emacs instance, it installed elpaca from MELPA

      This is incorrect. The installer directly clones Elpaca. Elpaca is not hosted on any ELPA. Doing so would require an installer package to be installed by another package manager. I don’t offer support for users running multiple package managers because it creates confusion about which package manager is responsible for which package, load-path entry, etc. MELPA rejected a similar proposal for straight.el as well:

      https://github.com/melpa/melpa/issues/4939

      cc: /u/liesdestroyer

      • ragnese@alien.topBEnglish
        1·
        11 months ago

        This is incorrect. The installer directly clones Elpaca. Elpaca is not hosted on any ELPA. Doing so would require an installer package to be installed by another package manager.

        Ah, right. That’s obvious in hindsight, but I didn’t give it much thought.

    • camber-weaver@alien.topBEnglish
      1·
      11 months ago

      Yes, this. I’ve had this happen a number of times and the solution was just to bump the specified elpaca version. I’ve had no negative consequences from doing so.