WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: unit193@ubuntu.com, Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	 Andy Whitcroft <apw@canonical.com>,
	Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
	 Martin Hauke <mardnh@gmx.de>, Joe Doss <joe@solidadmin.com>,
	 Neal Gompa <ngompa@fedoraproject.org>,
	 WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Adding Debian, Ubuntu, OpenSUSE, RHEL, CentOS kernels to WireGuard CI: Seeking URLs
Date: Fri, 22 May 2020 02:04:58 -0600
Message-ID: <CAHmME9oX+8HoK_wAoc5oR9rWenYz4ki8EK+NebQEV2ALZDSrdg@mail.gmail.com> (raw)

Hi distro kernel maintainers,

I currently have build.wireguard.com churning away at every new kernel
release between 3.10 and 5.5 for each and every wireguard-linux-compat
commit, making sure that we don't break anything. It's a pretty CPU
intensive, but it means we don't break mainline kernels ever when
releasing. Scroll down to the bottom to see what I mean.

This is not the case, however, with distro kernels, which differ
notoriously from mainline in surprising ways. There's been some
breakage, and unless we do something about it, I imagine there will
continue to be much breakage. Because so many users use Linux via your
kernels, it seems imperative that we support these well. And with
distros like Ubuntu now supporting WireGuard directly through
wireguard-linux-compat, it seems ever more important that we minimize
breakage so as to not create release delays downstream of us.

At the moment, wireguard-linux-compat supports:
- Debian oldoldstable (8), oldstable (9), stable (10), testing (11), sid
- Ubuntu 14.04, 16.04, 18.04, 19.04, 19.10, 20.04
- OpenSUSE 42, 15, 15.2 (leap)
- RHEL 7.8, 8.2
- CentOS 8.1

The logic here is that we support the latest single kernel for each
major supported release of these distros. For example, on Debian
stable, we support 4.19.0-9 but not 4.19.0-8 anymore.

I'd like to put these on build.wireguard.com to mitigate breakage. In
order to make this happen, I'll need two things:
- A URL I can scape that will give me the latest kernel versions for
relevant distros.
- A URL I can construct using a selected version to download a boring
kernel source tarball.
I would prefer to not involve git, if possible, and for these URLs to
point to the sources for actual kernels that are shipping as the
standard latest-kernel for each of the above releases.

If you can provide those pieces of information for my CI scripts, it
seems likely that we can drastically reduce breakage for your
distribution frankenkernels. If you cannot provide that, but other
distros can, I will probably naturally prioritize support for those
other distros that make maintenance easier, simply as a matter of
habit rather than something intentional.

Let me know if this is something that interests you. I'm happy to get
creative on what sorts of pages we scrape for this info.

Thanks,
Jason

             reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  8:04 Jason A. Donenfeld [this message]
2020-05-22  8:44 ` Jason A. Donenfeld
2020-05-23  5:59   ` Jason A. Donenfeld
2020-05-22 12:43 ` Georg Faerber
2020-05-23 12:31   ` Georg Faerber
2020-05-23  7:07 ` Neal Gompa
2020-05-23  7:21   ` Jason A. Donenfeld
2020-05-23 11:49     ` Neal Gompa
2020-05-24  0:01       ` Jason A. Donenfeld
2020-05-24  0:20         ` Neal Gompa
2020-05-24  1:10           ` Jason A. Donenfeld
2020-05-24  1:41             ` Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHmME9oX+8HoK_wAoc5oR9rWenYz4ki8EK+NebQEV2ALZDSrdg@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=apw@canonical.com \
    --cc=dkg@fifthhorseman.net \
    --cc=joe@solidadmin.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=mardnh@gmx.de \
    --cc=ngompa@fedoraproject.org \
    --cc=unit193@ubuntu.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git