#699001 notmuch-emacs should have a tighter dependence on notmuch

Package:
notmuch-emacs
Source:
notmuch
Submitter:
Daniel Kahn Gillmor
Date:
2025-09-18 08:05:06 UTC
Severity:
minor
#699001#5
Date:
2013-01-23 21:53:13 UTC
From:
To:
i run notmuch over a mailstore that is also served by a dovecot
instance (which is the reason for much of the spew below).

However, after a recent switch to notmuch 0.15, i got this one-time
error during "notmuch new":

 Internal error: add_message returned unexpected value: 4 (notmuch-new.c:543)

fwiw, i think that "unexepected value: 4" is NOTMUCH_STATUS_FILE_ERROR.

Unfortunately, i don't remember if this is the first time i've run
notmuch new since the 0.15 upgrade or if it has to do with some
particular message.

as you can see from the transcript below, running "notmuch new" a
second time didn't reproduce the error.  If you have any suggestions
on how i could supply better information, please let me know.

sorry for the vagueness of this report.
#699001#10
Date:
2013-01-24 11:40:23 UTC
From:
To:
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

Almost certainly unrelated to this bug report, but it looks like you
have an old version of notmuch-emacs installed. Perhaps the fact that
that is possible deserves its own bug.

d
#699001#15
Date:
2013-01-24 15:02:01 UTC
From:
To:
good catch, thanks!  I agree that it's probably unrelated to this
particular bug, but i've gone ahead and upgraded notmuch-emacs to match.

maybe notmuch-emacs should have:

 Depends: notmuch (= ${binary:Version})

if you think they the versions should be tightly bound.
#699001#20
Date:
2013-01-26 02:58:57 UTC
From:
To:
clone 698810 -1
reassign -1 notmuch-emacs
retitle -1 notmuch-emacs should have a tighter dependence on notmuch
owner -1 bremner@debian.org

thanks
#699001#35
Date:
2013-01-26 03:33:24 UTC
From:
To:
Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:

As of 0.15, specific format versions can be requested from the CLI, and
the emacs client requests specific format versions.  In other words, a
tight coupling between the notmuch and notmuch-emacs versions should not
be necessary from now on.

I think I would just go ahead and claim that this bug has now been fixed
upstream already.

jamie.
#699001#40
Date:
2013-01-26 13:06:38 UTC
From:
To:
Jameson Graef Rollins <jrollins@finestructure.net> writes:

It occured to me this specific option is not binNMU safe. But I guess
maybe something like  "(>= ${source:Version}), (<< ${source:Version}+)"
would work.

This doesn't prevent people from running:

     apt-get install notmuch

and breaking their notmuch-emacs installs (in the case a newer version
is available). I agree that it is better than before since now they
should get an error message to hint that they should also upgrade
notmuch-emacs.

d
#699001#47
Date:
2023-09-12 17:04:58 UTC
From:
To:
Dear Maintainer,

The notmuch-emacs package has been replaced with elpa-notmuch.
However, this bug still seems relevant; M-x notmuch doesn't work if
notmuch isn't installed.  elpa-notmuch should at least have a
"Recommends: notmuch", or more likely a "Depends".

I have no idea whether the version coupling issue is still relevant.
#699001#52
Date:
2023-09-12 17:55:24 UTC
From:
To:
Benjamin Moody <benjamin.moody@gmail.com> writes:

Recommends seems reasonable to me. Depends is too strong because it is
possible (and more or less sensible) to use elpa-notmuch without a local
notmuch install.