Dear Maintainer,

The packaged version of org-roam has a requirement on emacsql-sqlite
(see /usr/share/emacs/site-lisp/elpa-src/org-roam-2.3.1/org-roam.el
line 86) or in salsa:

https://salsa.debian.org/emacsen-team/org-roam/-/blob/v2.3.1/org-roam.el?ref_type=tags#L86

However, that is not currently listed as package requirement.  There
is a requirement on elpa-emacsql which provides only the high level
abstractions but not on the sqlite backend.  Without elpa-emacsql-sqlite
installed, starting org-roam in emacs leads to the following error:

    File is missing: Cannot open load file, No such file or directory, emacsql-sqlite

    To ensure normal operation, you should investigate and remove the
    cause of the error in your initialization file.  Start Emacs with
    the ‘--debug-init’ option to view a complete error backtrace.

and the full backtrace from `--debug-init` is:

    Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "emacsql-sqlite")
      require(emacsql-sqlite)
      load-with-code-conversion("/usr/share/emacs/site-lisp/elpa/org-roam-2.3.1/org-roam.el" "/usr/share/emacs/site-lisp/elpa/org-roam-2.3.1/org-roam.el" nil t)
      require(org-roam)

I suggest that elpa-emacsql-sqlite be added as a requirement for
elpa-org-roam (however, I think that things have changed for the
latest version of org-roam so this may apply only to the version
currently on Debian stable).

Best wishes
David

Hi,

David Miguel Susano Pinto <carandraug+dev@gmail.com> writes:

[snip]

Agreed

Elpa-emacsql-sqlite is an empty dummy package in sid/unstable and this
bug this only affects trixie.  I think this bug meets the criteria for a
stable update because the regression risk is zero.

Give me a few minutes to make the upload and file the unblock bug, but
please ping me if you don't see an unblock bug in a week.

Cheers,
Nicholas

Nicholas D Steeves <nsteeves@gmail.com> writes:

Note that currently trixie and sid/forky share the same version of
elpa-org-roam (2.3.1-1). You cannot upload a higher version in stable
(yet) because there is no version available in between and hence there
is no upgrade path (and your upload to stable-proposed-updates will
likely be rejected with the same reason).

I think you'll need to first upload a no-op 2.3.1-2 and wait for it to
enter Forky, and then prepare 2.3.1-1+deb13u1 for stable so that an
upgrade path is available.

P.S. For stable updates the bug it fixes also needs to be important or
above. I have bumped the severity to important here as well.

Xiyue Deng <manphiz@gmail.com> writes:

+deb13u1 is the "in between" version...the upgrade path is 2.3.1-1,
2.3.1-1+deb13u1, (>> 2.3.1-1+deb13u1).  Point release manager will
install +deb13u1 to testing and unstable when it is installed to
stable-updates, when that is the most correct action.

No, when dependencies are wrong they also need to be fixed in sid and
testing, so I have fixed it there too.

This is actually an RC bug that would have been caught if the
Uploader[s] of this package installed and used the package.

Cheers,
Nicholas