<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/Makefile.local, branch 0.30</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.30</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.30'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-07-03T10:37:00Z</updated>
<entry>
<title>build: produce signatures for release candidate tarballs.</title>
<updated>2020-07-03T10:37:00Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-06-16T14:17:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=552029f7482ea76806f18b8ef2cbe9c8706b39f4'/>
<id>urn:sha1:552029f7482ea76806f18b8ef2cbe9c8706b39f4</id>
<content type='text'>
Today Defalos on #notmuch asked for a signed tarball for
0.30~rc2. This is a minimal change to support this in the future.  The
question of automagically uploading will need more thought; currently
I like the fact that tags from pre-releases are only pushed manually.
</content>
</entry>
<entry>
<title>bindings/python-cffi: copy version file into bindings dir</title>
<updated>2020-07-03T09:38:55Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-06-30T00:22:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3a42abb456893b71b530f099a1467400f2b0ea71'/>
<id>urn:sha1:3a42abb456893b71b530f099a1467400f2b0ea71</id>
<content type='text'>
Attempt to avoid breaking "pip install ."

As far as I can tell, we need to have a copy (not just a relative
symlink) of the version file.
</content>
</entry>
<entry>
<title>debian: return an error if debian snapshot build fails</title>
<updated>2019-12-20T23:54:11Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-12-04T08:47:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7ebb2f5509c175c0efc6682fc7abf89a68f61f7d'/>
<id>urn:sha1:7ebb2f5509c175c0efc6682fc7abf89a68f61f7d</id>
<content type='text'>
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: optionally build python-cffi bindings</title>
<updated>2019-12-03T12:12:30Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-10-20T01:52:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=46e96156218e456df3fdd239e8c055220fba667a'/>
<id>urn:sha1:46e96156218e456df3fdd239e8c055220fba667a</id>
<content type='text'>
Put the build product (and tests) in a well known location so that we
can find them e.g. from the tests.
</content>
</entry>
<entry>
<title>release: use xz compression</title>
<updated>2019-03-27T20:59:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-03-19T10:08:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4bfbd5baa1e754e18d58dd6b8052a8072c0bfc2f'/>
<id>urn:sha1:4bfbd5baa1e754e18d58dd6b8052a8072c0bfc2f</id>
<content type='text'>
This produces tarballs that are roughly 30% smaller.
</content>
</entry>
<entry>
<title>build: Rename GPG_FILE to DETACHED_SIG_FILE</title>
<updated>2019-03-27T20:54:12Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-03-23T12:35:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1f82039e0da1adf078559ef9bf80e2b47858a607'/>
<id>urn:sha1:1f82039e0da1adf078559ef9bf80e2b47858a607</id>
<content type='text'>
This is just a semantic cleanup -- we have multiple files that are
OpenPGP signatures.  And while we're probably making signatures with
GnuPG, they can be verified with any OpenPGP implementation, so "GPG_"
is arguably both not specific enough, and overly-specific.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: distribute signed sha256sums</title>
<updated>2019-03-27T20:53:41Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-03-23T12:35:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=01f9c71312937011c4474688d3d1dd64c14731fb'/>
<id>urn:sha1:01f9c71312937011c4474688d3d1dd64c14731fb</id>
<content type='text'>
Distribute clearsigned sha256sum file in addition to the detached
signature.

Verifies that use the sha256sum ensure that the thing signed includes
the name of the tarball. This defends the verifier by default against
a freeze, rollback, or project substitution attack.

A verifier can use something like the following (as expressed in
bash):

      set -o pipefail
      wget https://notmuchmail.org/releases/notmuch-$VERSION.tar.gz{,.sha256.asc}
      gpgv --keyring ./notmuch-signers.pgp --output - notmuch-$VERSION.tar.gz.sha256.asc | sha256sum -c -

See id:87r2b8w956.fsf@fifthhorseman.net and other messages in that
thread for discussion.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: ensure that SHA256_FILE is built</title>
<updated>2019-03-27T20:53:18Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-03-23T12:35:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cc8d837d5a137a14a62526dcea60af1de7a353e4'/>
<id>urn:sha1:cc8d837d5a137a14a62526dcea60af1de7a353e4</id>
<content type='text'>
The SHA256_FILE used to be built automatically because of the makefile
dependencies.

Since b8a8dbed91d16299a8768646fb6f18181f31ec40, it isn't getting made
properly, so the release target would fail.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>build: sign tarball instead of sha256sum</title>
<updated>2019-03-12T01:28:11Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-02-13T02:17:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b8a8dbed91d16299a8768646fb6f18181f31ec40'/>
<id>urn:sha1:b8a8dbed91d16299a8768646fb6f18181f31ec40</id>
<content type='text'>
Adam Majer pointed out in [1] the way were signing releases was
unusual. Neither Carl nor I could think of a good reason for
explicitely signing the checksum (internally of course that's what GPG
is going anyway).

[1] mid:b3fd556d-c346-7af9-a7a2-13b0f3235071@suse.de
</content>
</entry>
<entry>
<title>doc: install build and install info pages</title>
<updated>2018-05-26T15:26:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-05-21T20:08:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7a6d4a0852664483bbba702cf3b030448b079e2c'/>
<id>urn:sha1:7a6d4a0852664483bbba702cf3b030448b079e2c</id>
<content type='text'>
All of the man pages are installed as info pages, plus
the (unfinished) notmuch-emacs manual
</content>
</entry>
</feed>
