Hello,

I did an upgrade on testing and rebooted leading me to restart emacs.
on loading org-roam reported an error needing emacsql-sqlite.

I installed elpa-emacsql-sqlite and restarted emacs and that worked.

Right now there's elpa-emacsql and 3 different database specific
packages

elpa-emacsql - high level SQL database frontend for Emacs
elpa-emacsql-mysql - high level SQL database frontend for Emacs
                     (MySQL backend)
elpa-emacsql-psql - high level SQL database frontend for Emacs
                    (PostgreSQL backend)
elpa-emacsql-sqlite - high level SQL database frontend for Emacs
                      (SQLite backend)

I'm guessing emacsql split the database drivers into subpackages
recently, and org-roam should probably depend explicitly on
elpa-emacsql-sqlite in stead of elpa-emacsql.

Thanks,
Diane

I took the privilege to reassign both Bug#1137368 and Bug#1138783 to
src:emacsql. I think the root cause of both issues is that the
elpa-emacsql package only contains the high-level interface without any
actual backend, so it cannot do much by itself. The package description
says: "EmacSQL is a high-level Emacs Lisp front-end for SQLite". So it
is expected that by installing elpa-emacsql it should provide the sqlite
backend at least.

Currently, the 3 backend packages, elpa-emacsql-{sqlite,mysql,psql},
depend on elpa-emacsql. This prevents elpa-emacsql from depending on
elpa-emacsql-sqlite, which will introduce a circular dependency.
Reversing the dependency is also wrong, as elpa-emacsql-sqlite by itself
won't work without the support of elpa-emacsql. The same goes for other
backends. In this case, separating the backends inherently causes
circular dependencies for things to work.

I believe in this case the separation of backends complicates the
handling with minimal gain: packages depending on emacsql by ELPA
convention need to be patched to depend on emacsql-sqlite (like case in
elpa-closql and org-roam), and the space saving is really not worth it -
all 3 backends code is less than 40kb combined.

Therefore, I'd like to propose merging back all *.el back to
elpa-emacsql and make all backend packages dummy, which would solve all
the issues mentioned above.

CCing Sean who did the initial packaging with separate backends and
the current maintainer Aymeric for comments. I will proceed with the
implementation once the plan is approved.

Thanks!

Xiyue Deng [04/Jun  2:24am -07] wrote:

This would mean that the elpa-* package names would no longer correspond
to the upstream ELPA packages, right?  Are there no alternatives?

Sean Whitton <spwhitton@spwhitton.name> writes:

Actually after merging everything back into elpa-emacsql it is aligned
with upstream (NonGNU) ELPA[1] and MELPA[2], where there is only
`emacsql' with no package split.

(Maybe there was a package split but they also merged everything back?)

[1] https://elpa.nongnu.org/nongnu/emacsql.html
[2] https://melpa.org/#/emacsql

Xiyue Deng [04/Jun 12:21pm -07] wrote:

I'd suggest verifying this.

Sean Whitton <spwhitton@spwhitton.name> writes:

OK. So I looked up the elpa/nongnu.git history and found this commit[1]
that explains why[2] everything was merged back in a single emacsql
package.

(Savannah cgit search is very slow right now. Hopefully opening just the
commit is faster.)

[1] https://cgit.git.savannah.gnu.org/cgit/elpa/nongnu.git/commit/?id=9e236b82a2da24bb9983e2f63061323354d6ecfe
[2] https://lists.gnu.org/archive/html/emacs-devel/2022-12/msg00525.html

Xiyue Deng [05/Jun  2:02am -07] wrote:

Nice.  Sounds like we can merge them back together, then.

Sean Whitton <spwhitton@spwhitton.name> writes:

Ack. Uploaded emacsql with a fix.

We believe that the bug you reported is fixed in the latest version of
emacsql, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1137368@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xiyue Deng <manphiz@debian.org> (supplier of updated emacsql package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 05 Jun 2026 17:05:35 -0700
Source: emacsql
Architecture: source
Version: 4.3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org>
Changed-By: Xiyue Deng <manphiz@debian.org>
Closes: 1137368 1138783
Changes:
 emacsql (4.3.6-2) unstable; urgency=medium
 .
   * Run `wrap-and-sort -ast'
   * Merge everything into elpa-emacsql (Closes: #1137368, #1138783)
     - This is aligned with ELPA/MELPA package handling and solves many of
       the dependency issues.
     - d/control: package transition
       + Make elpa-emacsql-{sqlite,psql,mysql} transitional dummy packages.
       + Add proper Breaks/Replaces/Provides in elpa-emacsql.
       + Update package descriptions.
     - Ship all *.el files in elpa-emacsql
       + Also drop d/elpa-emacs-{mysql,psql,sqlite}.elpa.
   * Fix field name typo in debian/copyright (Sources ⇒ Source).
   * Update standards version to 4.7.4, no changes needed.
   * Set upstream metadata fields: Bug-Database, Repository,
     Repository-Browse.
   * Set upstream metadata fields: Bug-Submit.
   * Migrate d/watch to version 5 format
   * Add d/salsa-ci.yml with the default template
   * Add myself to Uploaders
Checksums-Sha1:
 aa8f1c9ed3d3ed90302cb19ee63820c94cde9c68 2356 emacsql_4.3.6-2.dsc
 73b5c91bb262452f43724fa7af7b5c3888711036 4084 emacsql_4.3.6-2.debian.tar.xz
Checksums-Sha256:
 820fce4488d8026586705d0fb2dcd3b6669ead897c9b401b76d0d520f0e65ee2 2356 emacsql_4.3.6-2.dsc
 37a702c4ca6e30a559fac2aec46297333e385c50d7af9386e30fc5ee0bcfe3e9 4084 emacsql_4.3.6-2.debian.tar.xz
Files:
 a5117a3f219d59bc04394eef6fca04ba 2356 editors optional emacsql_4.3.6-2.dsc
 eed2be23f0b099dc6eac33c1524f62c6 4084 editors optional emacsql_4.3.6-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEiKQfd6o81mjI+LWALell7WOCXJMFAmojZPYTHG1hbnBoaXpA
ZGViaWFuLm9yZwAKCRAt6WXtY4Jck5AfD/9EvVn9WVOK2vJgmdHixuhPeGL+KCXE
pQSZYStTZlQQ4kjt7zxmrb8fqsxxF/zw55PsJtUP1wHKl+ruMqPgktojPjCQnTws
WlF6MCAdOLwg6i7oItx2q0Bwi2+c8tTVMved16MpzDKtJN35yn3+Ci5/wxQ8qUz6
8gl/+Ot4oiN6Abn6w5cGQE7UqamNOOjm73VlIW0p7h+OTfHvhcS6Y6edWzP4T3WT
0Lg9Vj2FX3/9tm75/MosR5kWGTOdbQJOcrTPGgGBla62rzJ5AuflWGuiifcHlJVh
a/j0H2COiqNiqKvyt16RNTrrW5hzKE0GCJoa7100AJJK5mrfOCqSxaagic+SDdqw
B+LHvLDCzyTvDHcX1Hyb2hIPVajEPB56zvI5e0DkU7uq/AWGneU3A58CSMxkvJpv
Za9A03wjefK0+mfbmlPmWCs5PYxbBTNkcO42TJ5WgwIMJ/c/jAJtrfgVXvHKPfxO
e4L02gWxv+tSqRi2KifvL6/W1Rzek26oIAOOdH8u7iJ7FiTDS7J2ODwvHIWfRo7d
LykkGxPyV3XUF4gXospC7dBch2Etw+oxJhlyeppCuucNdRRexyuOu3PZBAKD6cGl
ZljrbmzhWVTO8fUGx2JgPV98xEkpht5+D/vVXbLI5QgDpGzXWQoLGDbVtAoZ+7ND
Uq+QpmoLA5MmJA==
=VhzG
-----END PGP SIGNATURE-----

We believe that the bug you reported is fixed in the latest version of
emacsql, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1138783@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xiyue Deng <manphiz@debian.org> (supplier of updated emacsql package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 05 Jun 2026 17:05:35 -0700
Source: emacsql
Architecture: source
Version: 4.3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org>
Changed-By: Xiyue Deng <manphiz@debian.org>
Closes: 1137368 1138783
Changes:
 emacsql (4.3.6-2) unstable; urgency=medium
 .
   * Run `wrap-and-sort -ast'
   * Merge everything into elpa-emacsql (Closes: #1137368, #1138783)
     - This is aligned with ELPA/MELPA package handling and solves many of
       the dependency issues.
     - d/control: package transition
       + Make elpa-emacsql-{sqlite,psql,mysql} transitional dummy packages.
       + Add proper Breaks/Replaces/Provides in elpa-emacsql.
       + Update package descriptions.
     - Ship all *.el files in elpa-emacsql
       + Also drop d/elpa-emacs-{mysql,psql,sqlite}.elpa.
   * Fix field name typo in debian/copyright (Sources ⇒ Source).
   * Update standards version to 4.7.4, no changes needed.
   * Set upstream metadata fields: Bug-Database, Repository,
     Repository-Browse.
   * Set upstream metadata fields: Bug-Submit.
   * Migrate d/watch to version 5 format
   * Add d/salsa-ci.yml with the default template
   * Add myself to Uploaders
Checksums-Sha1:
 aa8f1c9ed3d3ed90302cb19ee63820c94cde9c68 2356 emacsql_4.3.6-2.dsc
 73b5c91bb262452f43724fa7af7b5c3888711036 4084 emacsql_4.3.6-2.debian.tar.xz
Checksums-Sha256:
 820fce4488d8026586705d0fb2dcd3b6669ead897c9b401b76d0d520f0e65ee2 2356 emacsql_4.3.6-2.dsc
 37a702c4ca6e30a559fac2aec46297333e385c50d7af9386e30fc5ee0bcfe3e9 4084 emacsql_4.3.6-2.debian.tar.xz
Files:
 a5117a3f219d59bc04394eef6fca04ba 2356 editors optional emacsql_4.3.6-2.dsc
 eed2be23f0b099dc6eac33c1524f62c6 4084 editors optional emacsql_4.3.6-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEiKQfd6o81mjI+LWALell7WOCXJMFAmojZPYTHG1hbnBoaXpA
ZGViaWFuLm9yZwAKCRAt6WXtY4Jck5AfD/9EvVn9WVOK2vJgmdHixuhPeGL+KCXE
pQSZYStTZlQQ4kjt7zxmrb8fqsxxF/zw55PsJtUP1wHKl+ruMqPgktojPjCQnTws
WlF6MCAdOLwg6i7oItx2q0Bwi2+c8tTVMved16MpzDKtJN35yn3+Ci5/wxQ8qUz6
8gl/+Ot4oiN6Abn6w5cGQE7UqamNOOjm73VlIW0p7h+OTfHvhcS6Y6edWzP4T3WT
0Lg9Vj2FX3/9tm75/MosR5kWGTOdbQJOcrTPGgGBla62rzJ5AuflWGuiifcHlJVh
a/j0H2COiqNiqKvyt16RNTrrW5hzKE0GCJoa7100AJJK5mrfOCqSxaagic+SDdqw
B+LHvLDCzyTvDHcX1Hyb2hIPVajEPB56zvI5e0DkU7uq/AWGneU3A58CSMxkvJpv
Za9A03wjefK0+mfbmlPmWCs5PYxbBTNkcO42TJ5WgwIMJ/c/jAJtrfgVXvHKPfxO
e4L02gWxv+tSqRi2KifvL6/W1Rzek26oIAOOdH8u7iJ7FiTDS7J2ODwvHIWfRo7d
LykkGxPyV3XUF4gXospC7dBch2Etw+oxJhlyeppCuucNdRRexyuOu3PZBAKD6cGl
ZljrbmzhWVTO8fUGx2JgPV98xEkpht5+D/vVXbLI5QgDpGzXWQoLGDbVtAoZ+7ND
Uq+QpmoLA5MmJA==
=VhzG
-----END PGP SIGNATURE-----