<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/configure, branch 0.30_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-06-01T11:02:43Z</updated>
<entry>
<title>configure: check existence of python3 setuptools and dev package</title>
<updated>2020-06-01T11:02:43Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2020-06-01T05:31:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=16d073ebe8fe062bb733165bdb10d7d2937616b5'/>
<id>urn:sha1:16d073ebe8fe062bb733165bdb10d7d2937616b5</id>
<content type='text'>
The notmuch2 CFFI-based Python interface is not buildable unless
python3 dev package and python3 setuptools are installed.

Check that these exist in configure (and disable notmuch2 bindings
build if not) so that build of these bindings don't fail when make(1)
is executed.
</content>
</entry>
<entry>
<title>python-cffi: enable out-of-tree builds</title>
<updated>2020-05-30T15:42:14Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-22T01:03:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ef0ab496b3f1e3a85f08102e3aaf251f4af69fd3'/>
<id>urn:sha1:ef0ab496b3f1e3a85f08102e3aaf251f4af69fd3</id>
<content type='text'>
This is a simple hack to enable out-of-tree builds, a concern raised
by Tomi in id:m24kzjib9a.fsf@guru.guru-group.fi

This change at least enables "make check" to complete without error,
but I'm sure it could be improved.  I am not expert enough in
setuptools to know how.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
Amended by db per id:87d06usa31.fsf@powell.devork.be
</content>
</entry>
<entry>
<title>configure: report GMime minimum version in ./configure output</title>
<updated>2020-05-23T01:07:51Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T21:17:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=78800929641fb79e758baa60d02216ed2ea941d0'/>
<id>urn:sha1:78800929641fb79e758baa60d02216ed2ea941d0</id>
<content type='text'>
We already report the minimum version for Glib, zlib, and Xapian
development libraries.  For consistency, report it for GMime as well.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>smime: tests of X.509 certificate validity are known-broken on GMime &lt; 3.2.7</title>
<updated>2020-05-23T01:04:57Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-22T00:42:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b14d9ae204dedab0b63ab54fc6d59ffe7090ba88'/>
<id>urn:sha1:b14d9ae204dedab0b63ab54fc6d59ffe7090ba88</id>
<content type='text'>
When checking cryptographic signatures, Notmuch relies on GMime to
tell it whether the certificate that signs a message has a valid User
ID or not.

If the User ID is not valid, then notmuch does not report the signer's
User ID to the user.  This means that the consumer of notmuch's
cryptographic summary of a message (or of its protected headers) can
be confident in relaying the reported identity to the user.

However, some versions of GMime before 3.2.7 cannot report Certificate
validity for X.509 certificates.  This is resolved upstream in GMime
at https://github.com/jstedfast/gmime/pull/90.

We adapt to this by marking tests of reported User IDs for
S/MIME-signed messages as known-broken if GMime is older than 3.2.7
and has not been patched.

If GMime &gt;= 3.2.7 and certificate validity still doesn't work for
X.509 certs, then there has likely been a regression in GMime and we
should fail early, during ./configure.

To break out these specific User ID checks from other checks, i had to
split some tests into two parts, and reuse $output across the two
subtests.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: drop support for xapian versions less than 1.4</title>
<updated>2020-04-24T00:28:45Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2020-04-21T21:07:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=00cdfe10717020423870fdaf56e973db9aba9f5a'/>
<id>urn:sha1:00cdfe10717020423870fdaf56e973db9aba9f5a</id>
<content type='text'>
Xapian 1.4 is over 3 years old now (1.4.0 released 2016-06-24),
and 1.2 has been deprecated in Notmuch version 0.27 (2018-06-13).

Xapian 1.4 supports compaction, field processors and retry locking;
conditionals checking compaction and field processors were removed
but user may want to disable retry locking at configure time so it
is kept.
</content>
</entry>
<entry>
<title>configure: Check GMime version properly</title>
<updated>2020-03-20T00:55:04Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-03-18T08:02:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=13f2027101a5f9e1ace7a83d7877b2bf4ad4ca75'/>
<id>urn:sha1:13f2027101a5f9e1ace7a83d7877b2bf4ad4ca75</id>
<content type='text'>
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>configure: fix reference to possibly undefined $PKG_CONFIG_PATH</title>
<updated>2019-12-09T20:24:37Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2019-11-17T21:24:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=eb1f799892a483f4e933867b2b9bafabd405045e'/>
<id>urn:sha1:eb1f799892a483f4e933867b2b9bafabd405045e</id>
<content type='text'>
In case zlib not found by pkg-config(1) the pkg-config information
is resolved by attempting to print ZLIB_VERSION from from zlib
installation if it exists anyway.

If above done successfully compat/zlib.pc is written for forthcoming
pkg-config execution.

Since `set -u` is in effect (since 124a67e96, 2016-05-06),
expanding unset $PKG_CONFIG_PATH (would have) failed whenever tried.

Now it is changed to set as "$PKG_CONFIG_PATH:compat" if PKG_CONFIG_PATH
is set and is non-empty string, plain "compat" otherwise.
</content>
</entry>
<entry>
<title>configure: Install zsh completions where zsh will find them.</title>
<updated>2019-12-03T12:25:55Z</updated>
<author>
<name>Oliver Kiddle</name>
<email>okiddle@yahoo.co.uk</email>
</author>
<published>2019-11-14T22:10:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2044c7aad9cbe2e87c773169a622e549b588d208'/>
<id>urn:sha1:2044c7aad9cbe2e87c773169a622e549b588d208</id>
<content type='text'>
Zsh searches in the $fpath array for completion functions. By default
this includes $(prefix)/share/zsh/site-functions but not the existing
value. The prefix for zsh and notmuch isn't guaranteed to be the same
but it normally will be making this a better default for
zsh_completion_dir.
</content>
</entry>
<entry>
<title>tests: run python-cffi tests</title>
<updated>2019-12-03T12:12:30Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-10-20T02:10:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=85adc756c97646ae63e68fc2f80afd6b34b86fa9'/>
<id>urn:sha1:85adc756c97646ae63e68fc2f80afd6b34b86fa9</id>
<content type='text'>
The entire python-cffi test suite is considered as a single test at
the level of the notmuch test suite. This might or might not be ideal,
but it gets them run.
</content>
</entry>
<entry>
<title>configure: check for python cffi and pytest modules</title>
<updated>2019-12-03T12:12:30Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-11-03T14:54:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3aaa8cfe941bd59730ae04df46da6aa3181f85e5'/>
<id>urn:sha1:3aaa8cfe941bd59730ae04df46da6aa3181f85e5</id>
<content type='text'>
This is needed to build the new python bindings, and run their tests.
</content>
</entry>
</feed>
