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

Re: Best way to handle circular build deps to make a pypy- package

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Pierre-Elliott Bécue <becue@crans.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Best way to handle circular build deps to make a pypy- package
Date	Mon, 20 Aug 2018 18:50:01 +0200
Message-ID	<woVxn-8rZ-3@gated-at.bofh.it> (permalink)
References	<wn1QC-6Qe-27@gated-at.bofh.it> <wn20h-6Tj-3@gated-at.bofh.it> <wn3Sp-7Y8-1@gated-at.bofh.it> <woTlU-7eo-15@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Aug 20 16:45:36 2018
Old-Return-Path	<becue@crans.org>
X-Amavis-Spam-Status	No, score=-12.8 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate:hard: -6.1
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/simple; d=crans.org; s=mail; t=1534783508; bh=CG15t8mqn+BYxM5F8drZC5Y5IOOa2btHq/tlF1pTvDQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gAlWULGo+XpdcyhhJ/rPG4ydbvgMbkm1XhpAwp6c84uTO2QHqfaKD2MEARxCa0d9G whoEAS2dK1Kxapk+4bNZCkt8hpDLOiBjD8XsqylWniSWWYjCVcFOc+5OJGdg1PrpjH comINKQ2jsaleH9UVtxvDMED7fRAdDbkWeClbjxHw5O8Z2BsLNJQEU9A5sSLAexRLt f9klE8qkloeETC+lgDVKsQ8wBMzo5N+Btl1pBgVj4R+9e7UYlwttrQHHpn086D5nlG e5wrKRZtkS0UFL0QqCuTPq0jpwsH1s9DgeK5fmtJy6549mogg6ObkwvewIGxIOEKJu BlyWAjKNF6tyLu1uQM0YQ+8eLBp+zZVVMMYiYojg70dDm2Z/StzeX0zQwlfnbQm0g5 8nNwMq1oa1T5X2cNyAAR83ZoNSPRPHuttqDOGl9hg80zvVf4SCkTIAMUoW2UdPZaO7 bq/EqFtOvNaaeg0PAJjTQNB8xaU2HprINJ0nKH6GaXB6E0m8QSoKZf9D3CyfRHy1UD FYnWyBaa3JlY/lVRsMPSNd80oEIEPMb8jFoI9wGBL3x09TLkPlPX/CRxfatcV4xFk6 YMOqZyRb+hA1Pcp53yRXY2t66gyCrbvn2gToVGXqxvjA4jJNuplboURsWQVwkPKFj0 hQiDXMVyX5GQTgqfgR8E3iZY=
MIME-Version	1.0
Content-Type	multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="p6syzvywtgqercig"
Content-Disposition	inline
User-Agent	NeoMutt/20170113 (1.7.2)
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/16245
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20180820164505.vk7pex2tslwcmapu@crans.org
Approved	robomod@news.nic.it
Lines	66
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	debian-python@lists.debian.org
X-Original-Date	Mon, 20 Aug 2018 18:45:05 +0200
X-Original-Message-ID	<20180820164505.vk7pex2tslwcmapu@crans.org>
X-Original-References	<20180815110509.nyvuqbncnlm54pp7@crans.org> <20180815111039.xl62gs2cibvqoolm@var.youpi.perso.aquilenet.fr> <20180815131125.sx5fcgnapb4wuhow@crans.org> <6799255f-d1a1-c260-4c86-cbd012644031@debian.org>
Xref	csiph.com linux.debian.maint.python:10825

Show key headers only | View raw

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

Le lundi 20 août 2018 à 16:20:54+0200, Thomas Goirand a écrit :
> On 08/15/2018 03:11 PM, Pierre-Elliott Bécue wrote:
> > Le mercredi 15 août 2018 à 13:10:39+0200, Samuel Thibault a écrit :
> >> Pierre-Elliott Bécue, le mer. 15 août 2018 13:05:09 +0200, a ecrit:
> >>>  2. What's the proper way to handle such packages?
> >>
> >> Build profiles? You can annotate the build-dep needed for check with
> >> <!nocheck> so that one can easily (re)bootstrap the circle at any time
> >> by using DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -Pnocheck
> > 
> > Thanks, I'll dig the wiki pages and try this!
> > 
> > Cheers!
> 
> Hi!
> 
> I have uploaded PBR 4.2.0-2 with lots of <!nocheck> in debian/control,
> which includes removing mock if such build profile is activated.
> 
> I hope this helps,
> Cheers,

Hi,

Thanks!

Unfortunately I'll have to look into some deps of pbr that are not yet
pypy-packaged. But I'll find my way.

I'll start to work on this between mid and late September.

Thanks again and cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.

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

Thread

Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-15 13:10 +0200
  Re: Best way to handle circular build deps to make a pypy- package Ghislain Vaillant <ghisvail@gmail.com> - 2018-08-15 13:20 +0200
  Re: Best way to handle circular build deps to make a pypy- package Samuel Thibault <sthibault@debian.org> - 2018-08-15 13:20 +0200
    Re: Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-15 15:20 +0200
      Re: Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-15 15:50 +0200
        Re: Best way to handle circular build deps to make a pypy- package Samuel Thibault <sthibault@debian.org> - 2018-08-15 17:40 +0200
      Re: Best way to handle circular build deps to make a pypy- package Thomas Goirand <zigo@debian.org> - 2018-08-20 16:30 +0200
        Re: Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-20 18:50 +0200

csiph-web