| Age | Commit message (Collapse) | Author |
|---|
|
pkgconf is apparently the annointed successor to pkg-config, at least
in Debian.
|
|
Not sure whose fault the failure is, but for now skip the test.
|
|
Recent gdb Provides gdb-minimal, so we can't conflict with it and
require gdb.
This may cause problems for people building in dirty environments for
older gdb, but there is not much we can do.
|
|
that may be less intimidating for new users.
|
|
add related Enhances (Closes: #1029190).
|
|
|
|
The new Vim addon policy relies on Vim's native package functionality,
rather than the Debian-specific vim-addons tool. This allows the addon
to be immediately available when the package is installed, rather than
requiring extra setup by the user.
* Install notmuch-vim to its own /usr/share/notmuch-vim directory, so
the files are self-contained.
* Remove vim-addon-manager from notmuch-vim Depends
* Add ${vim-addon:Depends} to notmuch-vim Depends to ensure it has the
required relationships on Vim/Neovim.
* Build-Depend on dh-sequence-vim-addon to automatically setup the
required symlinks for Vim and Neovim to see the addon.
Signed-off-by: James McCoy <jamessan@debian.org>
|
|
|
|
It is a bit weird to have debian changelog before upstream release date.
|
|
|
|
This reverts commit 522b279e46c84e4d2d52ccdf082d05fc111dc7b5.
Remove duplicate changelog stanza
|
|
|
|
|
|
|
|
|
|
|
|
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1063205
[dgit import unpatched notmuch 0.38.2-1.1]
|
|
[dgit import tarball notmuch 0.38.2-1.1 notmuch_0.38.2-1.1.debian.tar.xz]
|
|
|
|
Previously we both found a database and returned a message saying that
the database could not be found (along with a success code). This
change should prevent spurious error output.
|
|
Duplicate bug reported in id:87wmtvcor5.fsf@alyssa.is
The error message is nonsense, because notmuch config list actually
includes the database in those two cases.
|
|
|
|
[dgit import orig notmuch_0.38.2.orig.tar.xz]
|
|
|
|
|
|
Currently the --to/--cc/--bcc options add "user@example.com, " to the
message headers, with the the unnecessary ", " separator after the
last address, regardless of how many addresses are being added.
This used to be fine, but with recent emacs mm, trying to send the
email with the trailing commas leads to prompt:
Email address looks invalid; send anyway? (y or n)
Fix this by only adding the commas between addresses, avoiding the
trailing commas.
|
|
qsort(3) does not promise stability, and recent versions of glibc have
been showing more unstable behaviour [2]. Michael Gruber observed [1] test
breakage due to changing output order for message properties.
We provide a sorting order of (key,value) pairs that _looks_ stable by
breaking ties based on value if keys are equal. Internally there may
be some instability in the case of duplicate (key,value) pairs, but it
should not be observable via the iterator API.
[1]: id:CAA19uiSHjVFmwH0pMC7WwDYCOSzu3yqNbuYhu3ZMeNNRh313eA@mail.gmail.com
[2]: id:87msv3i44u.fsf@oldenburg.str.redhat.com
|
|
|
|
Just note the 3 bug fixes.
|
|
No changes from 0.38.1~rc1
|
|
|
|
|
|
Fixes: commit 239fdbbbf0cbd6cd6ebafb87e88cdb3cded75364
|
|
Bonus typo fix.
|
|
According to emacs upstream [1], we can't expect overlay invisibility
and images to get along. This commit uses the previously stashed
undisplayer functions to actually remove the images from the buffer.
When the image is toggled, it is essentially redisplayed from scratch,
using the previously stashed redisplay data.
[1]: https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg00593.html
|
|
This data will eventually be used to redisplay hidden images. A
certain amount of refactoring is done here to avoid code
duplication.
|
|
This data will be used to redisplay an image that is hidden by
deleting it from the buffer. We cannot easily delay until the image
is hidden, as we won't have the original data at that point.
|
|
For some kinds of MIME parts (at least images), our trickery with
overlays will not work, so save the more drastic function created by
Gnus that actually deletes the part from the buffer. In an ideal world
we would return this function as (part of) a value, but here the call
stack is too complicated for anything that simple, so we stash it in
the part plist and rely on that being preserved (unlike the mm handle,
which is transient).
|
|
The function _notmuch_config_load_from_file is only called in two
places in open.cc. Update internal API to match the idiom in open.cc.
Adding a newline is needed for consistency with other status strings.
Based in part on a patch [1] from Eric Blake.
[1]: id:20230906153402.101471-1-eblake@redhat.com
|
|
This is a bit fragile w.r.t. glib changing their error message, but it
already helped me find one formatting bug, so for now I think it's
worth it, instead of just grepping for "UTF-8".
|
|
For now print a generic error message and exit with error on any
non-success code. Previously the code exited, but with exit code zero,
leading users / scripts to think the command had succeeded.
|
|
We should ideally print an informative error message, but at the very
least we should not exit with success.
|
|
|
|
Actual news items to be filled in after they are applied.
|
|
Start preparations for point release
|
|
|
|
This is created (at least) by the Debian build, but there seems no
harm in cleaning it for everyone.
|
|
Having autopkgtests changes Debian package migration (for better and
worse), so make a note when they were introduced to unstable.
|
|
This avoids spurious underline/italics when exporting to markdown.
|
|
|
