Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Pierre-Elliott =?iso-8859-1?Q?B=E9cue?= <becue@crans.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Best way to handle circular build deps to make a pypy- package
Date: Wed, 15 Aug 2018 15:50:02 +0200
Message-ID: <wn4ls-87p-3@gated-at.bofh.it>
References: <wn1QC-6Qe-27@gated-at.bofh.it> <wn20h-6Tj-3@gated-at.bofh.it> <wn3Sp-7Y8-1@gated-at.bofh.it>
Old-Return-Path: <becue@crans.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wwllcilflrk77k74"
Content-Disposition: inline
User-Agent: NeoMutt/20170113 (1.7.2)
Approved: robomod@news.nic.it
Lines: 70
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10807


--wwllcilflrk77k74
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Le mercredi 15 ao=FBt 2018 =E0 15:11:25+0200, Pierre-Elliott B=E9cue a =E9c=
rit=A0:
> Le mercredi 15 ao=FBt 2018 =E0 13:10:39+0200, Samuel Thibault a =E9crit=
=A0:
> > Pierre-Elliott B=E9cue, le mer. 15 ao=FBt 2018 13:05:09 +0200, a ecrit:
> > >  2. What's the proper way to handle such packages?
> >=20
> > 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=3Dnocheck dpkg-buildpackage -Pnocheck
>=20
> Thanks, I'll dig the wiki pages and try this!
>=20
> Cheers!

Hi,

So I found a way to build locally, using your suggestions. In my case I
guess I could upload directly the output of the nocheck build as the bin
package isn't altered.

But how should I handle the upload in the archive in a general case? Let's
imagine my profile produces a different bin package, eg if foo -> bar (for
specific foo functionalities) -> foo, so with a stage1 foo, then a stage1
bar and then a stage2 foo, how should I proceed? Do all the builds locally
and upload the packages obtained from the last build?

On the other hand, let's assume one wants to do a sourceful upload, and not
upload the .deb files (I know this is not possible when one introduces a new
package in the archive), then the buildd farm couldn't succeed because the
nocheck wouldn't be taken into account. So this means profile builds
systematically require source + binary upload?

Maybe some of these questions may seem dumb, but I'd rather ask them than
upload shit to the archive. ^^

Thanks. :)

--=20
Pierre-Elliott B=E9cue
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.

--wwllcilflrk77k74
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEESYqTBWsFJgT6y8ijKb+g0HkpCsoFAlt0LvcACgkQKb+g0Hkp
CsrvEQ/+I5qi0ayvBBrtaMNa/Sn2+2Yk+BoSLuwfr1D1h3QIEy2KCkdv0gIwD/Nm
dK8GSK9ncfzwEIogLS86bfSYgnIpH+9aWcgoQZuxyRaNqzcA7aHlWIUKg3X+bBbn
ip+DvjiDdoOfp/DL9Qp6zrUrs8hkCY2Qa5T+pRkka9b2/JDZvNZnPQtdVXTw9hEM
XzVyO798toyeJMpPKxOGXVtrb9lZCPUGxR8rWjAxt/KtJrORjfyI2WcEGgQHJ/uX
MVA+fm4zHm4SvSiHklDWdcjtyHqHpuUJfpSiT8xAVpVl76sOCdZoVNGmckQj82nL
FO7B03ijF2gyQ3nbWYDol56tRD1ZDT4CDV0pYRy+MpH4Qpk/dTG10k5Kw+YbMEgy
cBB62HOphk3PZSDYvW7lRbEfDBYCyY3ou4ixGk42T3BlHBL8qSQQT5isdkf8wD5Z
z9wHMZP70YyedwYDJTp7WTykca4Ii52177H0aVL0o6qI0jW4+7/52hi8uMOUE5R/
Jusazj+ZuLo6pdYXr7c7VLpzkjTQg3IJ1CSn5NV1NUoLGYeZ4S1Tm5YSO1jML5EQ
lo9v6IfU2Ic++7r2qZIbjYFUI6jt/rgNMRIJr+7+4lGcT+QiKC+Iwm2oJ1tjBXL2
mUpeK7dSrAbRbYinzAdJUhlC083qJRpV+4G/UTZ/F7oO1/v/Xh0=
=ZCDD
-----END PGP SIGNATURE-----

--wwllcilflrk77k74--