|
From: | Gregor Kling |
Subject: | Re: emacsql-sqlite-builtin |
Date: | Thu, 2 Feb 2023 10:11:14 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 |
On 01.02.23 16:35, Basil L. Contovounesios wrote:
Gregor Kling [2023-02-01 13:21 +0100] wrote:On 01.02.23 12:10, Basil L. Contovounesios wrote:What versions do you have installed?Status: Installed in ‘emacsql-3.1.1/’ (unsigned).This looks like the version from MELPA Stable.Status: Installed in ‘emacsql-sqlite-builtin-20221127.2146/’ (unsigned).And this like the version from MELPA. This seems like a likely culprit, because the emacsql-connection class changed between these versions. What is your value of package-archives? I suggest making sure all your EmacSQL packages are installed from the same archive: either https://elpa.nongnu.org/nongnu-devel/ or https://melpa.org/packages/ This should ensure that their versions are mutually consistent. > If different versions of the same package exist in different archives, you can tell Emacs precisely where to get different packages from by customising the user options package-archive-priorities and package-pinned-packages.
In the aftermath this would have been better placed in help-gnu-emacs because of lack of knowledge. Nevertheless, thanks Basil, for breaking the tie. (setq package-archives '(("GNU ELPA" . "https://elpa.gnu.org/packages/") ("nongnu" . "https://elpa.nongnu.org/nongnu/") ("nongnu-devel" . "https://elpa.nongnu.org/nongnu-devel/")) package-archive-priorities '(("GNU ELPA" . 10) ("nongnu" . 8) ("nongnu-devel" . 6)) (setq package-pinned-packages '(("emacsql-sqlite-builtin" . "nongnu-devel"))) has solved the issue. -- Gregor Kling Abteilung ITS, Sachgebiet ITS-N Anwendungsentwicklung (IPAM, Tooling, Automation) DNS, DHCP Technische Hochschule Mittelhessen University of Applied Sciences Tel: 0641/309-1292 E-Mail: gregor.kling@its.thm.de
smime.p7s
Description: S/MIME Cryptographic Signature
[Prev in Thread] | Current Thread | [Next in Thread] |