Groups > linux.debian.maint.python > #12968

Re: help with FTBFS bug due to python3.8/3.9 confusion

Path	csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod
From	Andrey Rahmatullin <wrar@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: help with FTBFS bug due to python3.8/3.9 confusion
Date	Mon, 26 Oct 2020 11:00:01 +0100
Message-ID	<B47sd-4GD-3@gated-at.bofh.it> (permalink)
References	<B45A6-3xJ-3@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Oct 26 09:57:59 2020
Old-Return-Path	<wrar@debian.org>
X-Amavis-Spam-Status	No, score=-12 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -3.5
Dkim-Signature	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wrar.name; s=20160710; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:From:Sender:Reply-To:Subject:Date: Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=jMRSMZJm3CpQipLIu/3XKpLGuooZiVdwxQtWcIC+6wU=; b=q9VjwiOpMOsJsJkAxO8VIChS7j rKJJ59ngf29HCs24SzXU5yXfAoZBI8BbGNBmi4yqN/Q2cqbq0uTtILRyeCH3Bm8qdwR4RiNgs4ieW 63APh6/GQFPNDWoDFO2rOo4/oCZ1x7jFdXNkpmUsqNkVOJgC70WUYB2Q3zap3yfq5R3U=;
MIME-Version	1.0
Content-Type	multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition	inline
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/18731
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20201026095744.GA2060918@belkar.wrar.name
Approved	robomod@news.nic.it
Lines	60
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Mon, 26 Oct 2020 14:57:44 +0500
X-Original-Message-ID	<20201026095744.GA2060918@belkar.wrar.name>
X-Original-References	<CADopUHZsBUXJLTLdau2DW0Xh+LokKN+mRfnp+2djMWrv0CPe7w@mail.gmail.com>
Xref	csiph.com linux.debian.maint.python:12968

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Oct 26, 2020 at 08:54:37AM +0100, Stephen Sinclair wrote:
> The recommendations are to change the build-dep on "python-dev" to
> "python-all-dev", and I can confirm that this does allow the package
> to build.  (Is this the right thing to do?)
Building a module for all supported Python versions is a right thing to
do.

> However, autopkgtest tests still fail.  The commenter in that bug
> report claims, "the lack of 3.8 modules in the package also explains
> your problem."  However, I do not understand that claim -- wouldn't it
> be counter-productive to specify which minor version of Python the
> package depends on?  I would need to update this manually when the
> default switches to Python 3.9.
If you are packaging a public module you need to provide it for all
supported Python versions.
Not sure which tests fail and how, I don't think this is described
anywhere?

> Although the CMake build is quite complicated and therefore I can
> expect such problems, but I am nonetheless confused why it would
> select the wrong Python version, as I do specify the Python executable
> via the command,
> 
> > -DPYTHON_EXECUTABLE=$(shell which python3)"
> 
> Is there a better way to find the path to the default python interpreter?
When building a public module you don't need to care about the default
version.

-- 
WBR, wRAR

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

help with FTBFS bug due to python3.8/3.9 confusion Stephen Sinclair <radarsat1@gmail.com> - 2020-10-26 09:00 +0100
  Re: help with FTBFS bug due to python3.8/3.9 confusion Andrey Rahmatullin <wrar@debian.org> - 2020-10-26 11:00 +0100

csiph-web