| Age | Commit message (Collapse) | Author |
|
Work around apparent bug in gcc 15.2.0-17
|
|
Workaround for slow riscv64 autobuilders.
|
|
This is in preparation for moving them to contrib and dropping them
from the test suite upstream.
|
|
Not sure whose fault the failure is, but for now skip the test.
|
|
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>
|
|
The python setuputils clean relys on including _notmuch_config.py,
which is cleaned up. Rather than relying on careful ordering, just do
all the cleaning from the GNU Make based build system.
|
|
Hopefully just a temporary measure.
|
|
I plan to add further architecture dependent checks, which makes this
preferable to directly calling dpkg-architecture.
|
|
The test is fixed now.
|
|
We should fix this flaky test upstream, but for now, fix the build.
|
|
This is particularly useful for the docs for the notmuch2 python
bindings, which are otherwise not packaged.
|
|
In principle these tests should pass now.
|
|
These are failing on (surprisingly) the Debian amd64
autobuilder. There were also previous reports of failures on Ubuntu
s390x. Fixing this may require changing the way the default is
calculated.
|
|
A hopefully temporary change to try and debug some test failures on
autobuilders.
|
|
Ship a new debian package for the notmuch2 CFFI-based Python interface
to notmuch.
Unlike the notmuch python module, the new notmuch2 module is no longer
arch-independent, because it builds and ships a shared object in
addition to the python code.
This patch encourages new downstream development to rely on notmuch2
instead of on notmuch, to get the benefits of the new module.
I welcome any suggested improvements to this packaging, but it appears
to me to be sufficient to get "import notmuch2" to work and do some
basic tests.
|
|
notmuch release 0.29.2-2 for experimental (experimental) [dgit]
[dgit distro=debian no-split --quilt=linear]
|
|
Convert to pybuild while we are at it.
|
|
Debian's build hardening toolchain options produce binary artifacts
that are more resistant to compromise. The most visible change for
notmuch today is likely to be the addition of the "bindnow" linker
flag, which contributes to making the "Global Offset Table" fully
read-only.
See https://wiki.debian.org/Hardening for more details.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
|
|
This should no longer be needed on the official debian autobuilders,
but it might help others with merged /usr build environments.
|
|
Yes, a build chroot can have /usr/bin/bash, thanks to usrmerge, but we
can't depend on it existing in the user's system.
|
|
This ${prefix}/share/vendor-completion convention seems to be debian
specific, so leave the global default alone for now.
|
|
|
|
notmuch-dbgsym should be auto generated now.
|
|
With dh-elpa, this setting is no longer used
|
|
This packaging helper eliminates most of the boilerplate from packaging
emacs extensions for debian. It requires package.el compatible metadata.
|
|
Because ruby generates a Makefile, we have to use recursive make.
Because mkmf.rb hardcodes the name Makefile, put our Makefile{.local}
in the parent directory.
|
|
dh defaults for dh_auto_configure are now incompatible with notmuch's
homebrew configure script (at least in debian experimental)
|
|
|
|
The idea is to allow hardening verification tools (in particular blhc)
to scan the logs. Actually fixing the problem will require modifying
the notmuch configure script to propagate CPPFLAGS.
|
|
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
|
|
Now that we have Tomi's fix to set TERM for dtach, it should be safe to
run the tests on the autobuilders.
|
|
Hopefully this is temporary, but I don't want to rush a fix for the
tests.
|
|
This patch is due to Jakub Wilk <jwilk@debian.org>.
It does add a build depend on python3 for people using the "make
debian-snapshot" target.
|
|
- enable hardening
- fix dh syntax. Now that we have compat level 9, the old, wrong
syntax is no longer accepted.
- update debian/libnotmuch{3,-dev}.install for multiarch.
- update versioned dependency on debhelper.
|
|
|
|
This reverts commit 2b76283b52a2389a591ca055b086381c44e2a61f.
Conflicts:
debian/rules
|
|
There was a leftover override, installing it into the wrong package.
|
|
This reverts commit fc126d89b2baa479d98c864fbef4174b6da707c0.
This override of the make variable RPATH_LDFLAGS should no longer
be required since the auto-configuration was fixed
|
|
So far the package does notthing fancy with vim-addon-manager.
|
|
This uses dh_python2 (included with sufficiently recent versions of
the python/python-all packages). python-all brings in all of the
supported versions of python. The double calls to dh_auto_install and
friends are to avoid looping over python versions ourselves.
|
|
Probably there is a nicer way to do this; perhaps it should be a
configure option.
(cherry picked from commit 387dc520dd68cc805e390f3a1399f85b5d5bd83a)
|
|
This avoids patching the version file once per Debian upload.
Original version file is saved and restored.
(cherry picked from commit 2938a98bf4c4abe0426caee4555d889d655bc0df)
|
|
David Bremner informs me that shoving everything from the notmuch "git
log" into the debian/changelog is a bit excessive. Instead, we'll
start manually updating this file, (which feels a bit redundant with
NEWS, but perhaps makes us a better Debian-comunity member).
|
|
On Bdale Garbee's recommendation I'm switching from gitpkg, (which
constructed a source tree but still required me to go run debuild), to
git-buildpackage. I hadn't originally used git-buildpackage because it
didn't seem to work without a configuration file, (where gitpkg was
fine).
Bdale was kind enough to point me to his fw/altos source at
git.gag.com where I found an example gpb.conf file as well as a target
in debian/rules to automatically update debian/changelog with the new
version number.
|
|
I had the wrong syntax for the dh_auto_configure override.
|
|
And just make the Debian packaging request site-lisp/notmuch like it
wants. Otherwise, the installed files won't appear on the load-path
so won't be found by emacs.
|
|
Signed-off-by: martin f. krafft <madduck@debian.org>
|
|
|