From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DAED6C433DF for ; Sun, 24 May 2020 02:15:42 +0000 (UTC) Received: from krantz.zx2c4.com (krantz.zx2c4.com [192.95.5.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8797220759 for ; Sun, 24 May 2020 02:15:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="WkcjIPGN" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8797220759 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=wireguard-bounces@lists.zx2c4.com Received: by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 769a3ddf; Sun, 24 May 2020 01:59:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4vNhzsJiI+mIOA6h12itBv1JGu4dNjEWfmCatAqeGvQ=; b=WkcjIPGN1JUpIwyzWm2Z2fLIyQV/U5gAJOIthXYazQRZSZWAFqx1xZw5TlHiafhsX/ CfSk2Jd4YE//aUDA+W3atUtfqxeYVsqyYYFnFzRbagllVdBsUl6Uab9+Djdyx9iNQjQa RcfHkZ8OrpgZXJ5sxh3AyYE2YecZQKQUwf4OBpd/Hg9ChN/2hiIKZrGx4ArHJi/I3IQL lG5YTICVFLwIo9MX8izB81hNFIOwBvEfbG02kjIm5IyyKNAIwCgZaMz5r4agG5rMn2jD dqDy+Cf27s/bv4Y0+DCJStx23BeT52czyD4uoR0lNm6ttFsy6xdqnXTGGNHRSJPWbOxu h+jA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=4vNhzsJiI+mIOA6h12itBv1JGu4dNjEWfmCatAqeGvQ=; b=phOUlv+GIvJp8/v9eYAG/fwuhosGR1HbOe3H7mKpTDxjRMzFy+S4VB/QD+eLrLdUBQ jtLDagCVXf8tDFDRF97xoJfH9Bv4LLtM3/jNIjgBTIFc/n3htaaHAlIywoG+nuY0iW5Q l9wnrrzpLp2ikHUvfHoyKV452kNFDnq3NFFo8R6xcKWu9tzUzEq50GRTSLHczQ/mWq+w 8qQEtwtsjb2TiE4/81x/gPAZqno4dDDaXpqzoLgQmPG79fr5/XnvQSyARFmn81qo/MYV UvPPSWxVjDegBNjvlpjIZuoo34IZzmXwjUE/dj9MVHtDs7iTGU/1ISCgBer4d58G9I0q +85A== X-Gm-Message-State: AOAM532IntMhH63fE3Vf6WYrgN4Cmojy/hm3rafnrnBgmEQFeaI+qJOu 9O+J2NyZSf7z9e2V2qbPckMk/uoikaQ50pI+haD+bTUuHNY= X-Received: by 2002:a02:3b45:: with SMTP id i5mr11900922jaf.47.1590279671473; Sat, 23 May 2020 17:21:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Neal Gompa Date: Sat, 23 May 2020 20:20:35 -0400 Message-ID: Subject: Re: Adding Debian, Ubuntu, OpenSUSE, RHEL, CentOS kernels to WireGuard CI: Seeking URLs To: "Jason A. Donenfeld" Cc: unit193@ubuntu.com, Daniel Kahn Gillmor , Andy Whitcroft , Ubuntu Kernel Team , Martin Hauke , Joe Doss , WireGuard mailing list , Carl George Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" On Sat, May 23, 2020 at 8:01 PM Jason A. Donenfeld wrote: > > On Sat, May 23, 2020 at 5:50 AM Neal Gompa wrote: > > > > On Sat, May 23, 2020 at 3:21 AM Jason A. Donenfeld wr= ote: > > > > > > Hi Neal, > > > > > > Thanks for these very helpful instructions. In trying to implement > > > this, one snag I encountered was that the .src.rpm file has inside of > > > it the linux-{version}.tar.xz file that I actually want. Is there > > > anywhere on the internet that hosts these .tar.xz files directly? > > > > > > > There *is*, but that starts getting into using the CentOS Git system > > more directly. Per your original email, you weren't interested in that > > path, so I didn't go there. > > Well, one trick is that most web git viewers (such as cgit) can > produce a tarball on the fly from a URL. Something like this exist > here? So, CentOS uses a Dist-Git[1] system, which means the part that is actually tracked in git is the packaging files, and there's an associated binary repo reference stored in the Git repo for fetching binary artifacts. Dist-Git is the common ancestor to virtually all current approaches to storing binaries efficiently alongside a Git repo (Git-Annex and Git LFS came much later). It seems it's possible to do this without having to use Git itself (which is better than with git-annex and git-lfs), but it's a bit cumbersome... The way that you'd fetch the tarball in this scenario would be to something like the following: 1. Get the tags via API, but with commits: $ curl --silent --header "Content-Type: application/json" \ https://git.centos.org/api/0/rpms/kernel/git/tags?with_commits=3Dtrue \ | jq '.["tags"] ' This gives you now a JSON dictionary with the tags as keys and the associated commit as values. 2. Get the corresponding commit and fetch the .kernel.metadata file containing the lookaside references: $ curl --silent https://git.centos.org/rpms/kernel/raw/${kernel_tag_commit}/f/.kernel.metad= ata \ > kernel_sources 3. Fetch the source matching to your kernel source package: $ wget https://git.centos.org/sources/kernel/${rel}/${kernel_src_checksum} = \ --output-document=3D${kernel_src_filename} The $kernel_src_checksum and $kernel_src_filename would be populated from the entries in the kernel_sources files you downloaded earlier. Note: $rel is either "c7" or "c8" depending on which one you're trying to g= et. [1]: https://github.com/release-engineering/dist-git -- =E7=9C=9F=E5=AE=9F=E3=81=AF=E3=81=84=E3=81=A4=E3=82=82=E4=B8=80=E3=81=A4=EF= =BC=81/ Always, there's only one truth!