notmuch, branch 0.23.6thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.23.62017-02-27T10:58:07Zdebian: set upload date and suite2017-02-27T10:58:07ZDavid Bremnerdavid@tethera.net2017-02-27T10:58:07Zurn:sha1:c028ec8860407041a19448d50998de8e3fd44217NEWS: set release date2017-02-27T10:57:42ZDavid Bremnerdavid@tethera.net2017-02-27T10:57:42Zurn:sha1:7e565a3db387f45e548cc464a88fb0870c387b9adebian: note read-after-free fix in d/changelog2017-02-25T12:48:10ZDavid Bremnerdavid@tethera.net2017-02-25T12:48:10Zurn:sha1:b1a42b5916205e24dc8fed9796d0adc5d17dd077NEWS: document read-after-free bugfix2017-02-25T12:45:43ZDavid Bremnerdavid@tethera.net2017-02-25T12:45:43Zurn:sha1:4191ab22e00bb15bd63b9e3661c5fa922361e959version: bump to 0.23.62017-02-23T13:03:41ZDavid Bremnerdavid@tethera.net2017-02-23T13:03:10Zurn:sha1:48253190adb70fcc1783beeeb386c19ff4832fa9
python and debian bumped at the same time
lib: fix g_hash_table related read-after-free bug2017-02-22T10:28:03ZDavid Bremnerdavid@tethera.net2017-02-22T10:17:47Zurn:sha1:4e649d000b9d3764aea98cb0e1120947d7f76f3d
The two g_hash_table functions (insert, add) have different behaviour
with respect to existing keys. g_hash_table_insert frees the new key,
while g_hash_table_add (which is really g_hash_table_replace in
disguise) frees the existing key. With this change 'ref' is live until
the end of the function (assuming single-threaded access to
'hash'). We can't guarantee it will continue to be live in the
future (i.e. there may be a future key duplication) so we copy it with
the allocation context passed to parse_references (in practice this is
the notmuch_message_t object whose parents we are finding).
Thanks to Tomi for the simpler approach to the problem based on
reading the fine glib manual.
debian: start changelog for 0.23.62017-02-21T11:51:44ZDavid Bremnerdavid@tethera.net2017-02-21T11:51:44Zurn:sha1:928016a4ea0de23960b9c44b9f5d556b8878b5abNEWS: news for gpgconf use in test suite2017-02-21T11:50:05ZDavid Bremnerdavid@tethera.net2017-02-21T11:50:05Zurn:sha1:5e22323c15811ea43736b2f5f2fa21464e8942f4test: use gpgconf --create-socketdir if available2017-02-21T11:45:40ZDavid Bremnerdavid@tethera.net2017-02-14T21:42:39Zurn:sha1:e7b88e8b0a93ca83d807edc00e0c97af54c5b5f1
This enables the shortened socket pathes in /run or equivalent. The
explicit call to gpgconf is needed for nonstandard GNUPGHOME settings.
(amended according to id:m2fujatr4k.fsf@guru.guru-group.fi)
configure: add test for gpgconf --create-socketdir2017-02-21T11:43:15ZDavid Bremnerdavid@tethera.net2017-02-14T21:42:38Zurn:sha1:12f7d4e61d30fb9a5c99e128ab1aab0bf069cdb4
This is primarily intended for use in the test suite (since notmuch
builds fine without gnupg installed). Thus we only write the variable
to sh.config.