notmuch, branch archive/debian/0.39_rc2-1

debian: changelog for 0.39~rc2-1

2025-03-11T09:12:45Z

version: bump to 0.39~rc2

2025-03-11T09:12:45Z

ruby: fix "undefining the allocator of T_DATA" warnings

2025-03-08T14:39:22Z

Ruby 3.2 introduced a warning when C-extensions use structs without redefining the allocation default allocation routine meant for objects. See https://bugs.ruby-lang.org/issues/18007 for details. In the Ruby bindings this happens at `Data_Wrap_Notmuch_Object` call sites, so the object types used there needed to update their allocation. This ruby code (given a database at the hardcoded path with messages matching `tag:tmp`) exercise all the ruby objects: require 'notmuch' Notmuch::Database.open File.expand_path("~/mail") do |db| db.get_directory("/tmp") db.query("tag:tmp").search_threads.each do |t| t.messages.each do |m| puts m.header("Subject") end end end Before these changes with ruby 3.2.5 and notmuch 0.38.3 it outputs: notmuch.rb:5: warning: undefining the allocator of T_DATA class Notmuch::Query notmuch.rb:5: warning: undefining the allocator of T_DATA class Notmuch::Threads notmuch.rb:5: warning: undefining the allocator of T_DATA class Notmuch::Thread notmuch.rb:6: warning: undefining the allocator of T_DATA class Notmuch::Messages notmuch.rb:6: warning: undefining the allocator of T_DATA class Notmuch::Message notmuch release 0.38.3 now available (the last line is the message I tagged with tmp), and after the changes: notmuch release 0.38.3 now available

docs: avoid nmbug in notmuch-git.1

2025-03-01T12:42:57Z

These days, `nmbug` is `notmuch-git` with special defaults, so avoid the term `nmbug` in the doc when we talk about `notmuch-git` in general. Also, spell git in lower case (as we do for notmuch) except for the one case where we name the beast.

Accept "key-missing" from a signature from a revoked key

2025-02-28T20:32:36Z

We have traditionally expected a signature to show up as "revoked" when the signing key is revoked. However, GnuPG's recent fix to avoid a denial of service against legitimate signatures appears to have changed the status of signature verification from keys which happen to have been revoked. See https://bugs.debian.org/1098995 and https://dev.gnupg.org/T7547 This change makes the test suite a little bit less brittle while we look for a resolution from upstream. It should probably also be backported to debian unstable unless a notmuch release to unstable is imminent. Signed-off-by: Daniel Kahn Gillmor

python: Fix message ID docstring

2025-02-28T15:31:55Z

The messageidb attribute does not exist. The returned BinString type already allows use as both strings and binary. Presumably this was written before that type was adopted.

debian: upload to experimental instead of unstable

2025-02-25T20:35:44Z

version: bump to 0.39~rc1

2025-02-25T20:15:24Z

debian: changelog stanza for 0.39~rc1-1

2025-02-25T20:11:07Z

test/emacs: add workaround for Emacs 30 pp changes

2025-02-25T11:25:59Z

This relies on the fact that setting pp-default-function has no effect for Emacs <30.