From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 1/5] debian/control: build-depend on python3-sphinx instead of python-sphinx
Date: Thu, 30 Nov 2017 09:25:52 -0500 [thread overview]
Message-ID: <87k1y74zdb.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20171130094043.2039-2-dkg@fifthhorseman.net>
On Thu 2017-11-30 04:40:39 -0500, Daniel Kahn Gillmor wrote:
> python2 is going to be deprecated, and python3-sphinx is available all
> the way back to oldoldstable. let's use the more modern version.
> ---
> debian/control | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debian/control b/debian/control
> index 20b8a2db..3a624fdc 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -18,7 +18,7 @@ Build-Depends:
> python3-all (>= 3.1.2-7~),
> dh-python,
> dh-elpa (>= 1.3),
> - python-sphinx (>= 1.0),
> + python3-sphinx,
> ruby, ruby-dev (>>1:1.9.3~),
> emacs25-nox | emacs25 (>=25~) | emacs25-lucid (>=25~) |
> emacs24-nox | emacs24 (>=24~) | emacs24-lucid (>=24~) |
hm, on further reflection, this one is specifically problematic because
of the use of:
${python} -m sphinx.writers.manpage
in ./configure, used to test for the presence of the sphinx module.
This can be fixed by preferring python3 here:
--- a/configure
+++ b/configure
@@ -557,7 +557,7 @@ fi
printf "Checking for python... "
have_python=0
-for name in ${PYTHON} python python2 python3; do
+for name in ${PYTHON} python3 python python2; do
if command -v $name > /dev/null; then
have_python=1
python=$name
any thoughts or preferences on this?
--dkg
next prev parent reply other threads:[~2017-11-30 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 9:40 debian packaging cleanup Daniel Kahn Gillmor
2017-11-30 9:40 ` [PATCH 1/5] debian/control: build-depend on python3-sphinx instead of python-sphinx Daniel Kahn Gillmor
2017-11-30 14:25 ` Daniel Kahn Gillmor [this message]
2017-12-03 13:35 ` Tomi Ollila
2017-12-04 14:30 ` Daniel Kahn Gillmor
2017-12-04 20:58 ` Tomi Ollila
2017-12-04 21:12 ` Tomi Ollila
2017-12-06 1:46 ` [PATCH v2] " Daniel Kahn Gillmor
2017-12-07 12:31 ` David Bremner
2017-11-30 9:40 ` [PATCH 2/5] debian/changelog: remove trailing whitespace Daniel Kahn Gillmor
2017-11-30 9:40 ` [PATCH 3/5] debian/control: Priority: extra is deprecated Daniel Kahn Gillmor
2017-11-30 9:40 ` [PATCH 4/5] debian: bump Standards-Version to 4.1.1 Daniel Kahn Gillmor
2017-12-05 1:30 ` David Bremner
2017-12-05 17:13 ` Daniel Kahn Gillmor
2017-11-30 9:40 ` [PATCH 5/5] debian/control: put elpa-notmuch in Section: lisp Daniel Kahn Gillmor
2017-12-07 14:23 ` Daniel Kahn Gillmor
2017-11-30 12:01 ` debian packaging cleanup David Bremner
2017-11-30 14:57 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1y74zdb.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).