X-Original-To: alpine-infra@lists.alpinelinux.org Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252]) by lists.alpinelinux.org (Postfix) with ESMTP id 92A0E5C4533 for ; Sun, 29 Oct 2017 12:28:10 +0000 (GMT) dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail; c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type:In-Reply-To:References; bh=XDmGgwyyvLVn1wZRLMRkUQKosjoBbAT4a2nWDLhG0BY=; b=NLQwJPMmNcNaBKSw1vjQSytyY+dLeuEXsSazuJa0uti+mjSUJGap1HrJniYiKJ041zZTTTT9uruE5IYYqnxDst71qD7P+pZ1vOB+El9HhjrhKsiv2OA72obGB05rd0p9ZbP4MsfcIfqF4wCyxJ0xnUb1hle5AYBfwZLvRwWgEAE= Received: from [127.0.0.1] (BITMESSAGE [127.0.0.1]) by mail.bitmessage.ch with ESMTPA ; Sun, 29 Oct 2017 13:26:50 +0100 Subject: Re: Building unofficial packages on Alpine build infrastructure? To: Natanael Copa References: <514355cb-b6f1-c220-99fc-b096dcb0b693@bitmessage.ch> <20171027181301.478d6385@ncopa-desktop.copa.dup.pw> From: Oliver Smith Cc: alpine-infra@lists.alpinelinux.org Message-ID: <9d702d8d-6023-346b-cd1a-fa35323fa96f@bitmessage.ch> Date: Sun, 29 Oct 2017 12:27:00 +0000 MIME-Version: 1.0 In-Reply-To: <20171027181301.478d6385@ncopa-desktop.copa.dup.pw> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="O9tSTjkKnLh6wSFi2x21ix3tweRd34BNc" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --O9tSTjkKnLh6wSFi2x21ix3tweRd34BNc Content-Type: multipart/mixed; boundary="rPHlco0AmoNVjppd5nt90txevlTXb31Gr"; protected-headers="v1" From: Oliver Smith To: Natanael Copa Cc: alpine-infra@lists.alpinelinux.org Message-ID: <9d702d8d-6023-346b-cd1a-fa35323fa96f@bitmessage.ch> Subject: Re: Building unofficial packages on Alpine build infrastructure? References: <514355cb-b6f1-c220-99fc-b096dcb0b693@bitmessage.ch> <20171027181301.478d6385@ncopa-desktop.copa.dup.pw> In-Reply-To: <20171027181301.478d6385@ncopa-desktop.copa.dup.pw> --rPHlco0AmoNVjppd5nt90txevlTXb31Gr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable > I am glad to have you around I want help if we can. I have already have= > use for the apk string version compare implementation that you wrote in= > python. I am happy to read that and a bit curious what you have used for :) > What are your exact needs? Build servers on what architecture(s)? x86_64, armhf, aarch64 > Where do you want upload the built packages? We have two mirrors set up (thanks to Martijn Braam!): http://postmarketos1.brixit.nl http://postmarketos2.brixit.nl Right now they host some outdated test packages we don't use, which were = from an experiment with providing packages, where the files inside the ap= k packages are reproducible. Lots of code has been written for that to "c= hallenge" package contents by rebuilding them and what not, but all in al= l it didn't seem feasible to continue this effort at this point and would= only drive away from how Alpine handles things instead of being closer t= o upstream. (I can provide more details if someone is interested, there's= a lot of theory already written down and it involves every package being= rebuilt and challenged by a third party (e.g. Travis) before it gets acc= epted into the binary repo. Maybe at some far point in the future I can p= ick this up again and help with Alpine getting reproducible builds upstre= am.) When I realized that this path was not working out, and with the quotes f= rom Alpine developers I have put in the first mail of this thread I figur= ed directly building the packages with Alpine's infra would be the next b= est thing. So users didn't have to trust another entity for building the = packages, it would be all from Alpine. > Do you mind if we follow this up after the v3.7 release? Not at all! In fact I realize that the timing for my post wasn't that great because o= f the upcoming 3.7 release, and it would have been nicer of me if I asked= kaniini directly (sorry for that!). =46rom the answers you have given me, I think it a better short term solu= tion for postmarketOS would be building the packages on our own. This is = really good to know, we can move forward with this information. Thank you very much, Oliver Natanael Copa: > On Tue, 24 Oct 2017 22:47:00 +0000 > Oliver Smith wrote: >=20 >> Dear Alpinists, >> >> >> at least Timo Teras[1] and William Pitcock[2] have proposed, that the >> Alpine package building infrastructure could be used for unofficial >> Alpine packages, when "the new build infrastructure [is] in place". >=20 > replacing the building infra is a big project. I don't know how much > time it will take, and so far the progress have been slow. >=20 >> So postmarketOS[3] is a thin layer on top of Alpine, that provides >> packages to make it work on mobile devices. Currently every user is >> compiling these from source, but we would be very grateful if we could= >> use Alpine's infrastructure for building binary packages. That way we >> could focus more on actual development and giving back to Alpine (e.g.= >> together with Ad=C3=A9lie, we're currently upstreaming KDE), instead o= f >> duplicating the effort. >> >> For reference, here[4] are our current aports. Especially the device >> folder makes no sense to be upstreamed. We will not build packages tha= t >> contain closed source blobs (our firmware aports will be refactored to= >> download these files at installation time[5]). >> >> Thoughts? >=20 > I am glad to have you around I want help if we can. I have already have= > use for the apk string version compare implementation that you wrote in= > python. >=20 > What are your exact needs? Build servers on what architecture(s)? >=20 > Where do you want upload the built packages? >=20 > Do you mind if we follow this up after the v3.7 release? >=20 > Thanks! >=20 >> >> >> Best regards, >> Oliver Smith >> >> >> [1]: Timo Teras: "This would allow several improvements: - would >> simplify us supporting contributed ppa type aports trees our infra wou= ld >> build" >> [2]: William Pitcock: "Once we have the new build infrastructure in >> place, I am sure that we could arrange for derivatives to make use of >> it. But I will need to talk with the infra team before committing us t= o >> that." >> [3]: >> [4]: >> [5]: >> >> >=20 >=20 --rPHlco0AmoNVjppd5nt90txevlTXb31Gr-- --O9tSTjkKnLh6wSFi2x21ix3tweRd34BNc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEVuhTDbWL3IASV/XwWuf1UT4IhcsFAln1yTEACgkQWuf1UT4I hctkcBAAkFpxDf8Kde17ov2KEctU+G+xmOSCnPXaKV4m4J3ZZryAh5+xtTuKrl2S YzcFmPF6aOaXLvrjcxaEqK73eAKw/C5FNiuSSkZdY3JirNxjkp2buT6xOmlz4HuQ xYXUcBWGpUg1QwaBQ0h4BffR0E6gxfPqipcPlLfON8wgtPq0j8bj21qwQWOKq4ob ky/hUMDf2KJWwRptJfC55j2c8+Np25nzPr6wlQyWTybyoMjpDP2FsFa+70gioVdp qFfCfnmxgWiWX09ZQxw/enjYcS0UMK0pdAzIrNUuzTD0XEcTFQbQ60pXwSAGWLid d0Oz7iAVqcSnyt+0qLeHHf/grri7FrSa9oVrObJuRm26e78p+rDSqfqbVjv2WkID 5Ik231gyEwDIYVzeKbmGnbZN7R4cK7iOdRxAdJuoVs55gEITcCQOtNh1celeevsO GcAHl8rVtimzUgwVpkchJSxQ1uUoYlBSBpHUcaSQkruP491bHjgAW4UDlxXhxurJ yePfr1pYgbxMv+2ZtjefUW3VLsJEIKS6CaTIG65WBf8jLStEjejwlBUfIj5uKDtj zGqCOmc5aRkJVHvezRohSLvKneFaVgXU8syJAbuuW19NsaeEfnAbINGIpqu4NyOc 8Tv7TJTUQ2vDOJIjiSFhF724PEC9aT+Tt0PF0dvTWvY2wKZVp6Q= =G0gA -----END PGP SIGNATURE----- --O9tSTjkKnLh6wSFi2x21ix3tweRd34BNc--