Received: from out-218.mta0.migadu.com (out-218.mta0.migadu.com [91.218.175.218]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 876A8221BAF for ; Tue, 31 Jan 2023 22:22:55 +0000 (UTC) Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ayaya.dev; s=key1; t=1675203774; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UI7Jdpnom492eFhICdfHCnHX/O1SxDwoqXuNPRS1J3g=; b=Iw6E61FlXtrWhNDUhz41My+43pn1gWilEHUgKIFx0+c9gt59qblEoxTBukq5ZS+FMDjI5r 2DdhnGP/ww8A3sZh6a+tT6VnWklGdAAKscI/E4C4lO3nSYZy+PGV6siEgARljAI5Rjkrwt MPAlbaJNxkyVuHMcP7iLgf6ZU/feAIY= Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 31 Jan 2023 23:22:46 +0100 Message-Id: Subject: Re: linux-lts vs. linux-edge X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "alice" To: "Christian Kujau" , References: <11ef5892-ee4f-fab7-4eda-81eaca667ee8@nerdbynature.de> In-Reply-To: <11ef5892-ee4f-fab7-4eda-81eaca667ee8@nerdbynature.de> X-Migadu-Flow: FLOW_OUT On Tue Jan 31, 2023 at 10:32 PM CET, Christian Kujau wrote: > Hi folks, > > I was wondering about the packages linux-lts (main) and linux-edge=20 > (community). LTS suggests some kind of Long Term Support, the "more stabl= e=20 > version" of the Linux kernel. But I noticed that both versions are=20 > basically the same, and have been for some time, according to their commi= t=20 > histories[0]: linux-lts was bumped to 6.1.8 on Jan 24, linux-edge on the= =20 > same day. > > So, my first question is: what's the rationale behind these packages?=20 > Looking at kernel.org, v6.1.8 *is* actually the current stable version.= =20 > But what should -edge be? Maybe current mainline, i.e. the -rc versions? lts follows latest lts, and edge follows latest stable. as mentioned in the other response, the intention was that 6.1 would be the next lts, ncopa jus= t seemingly made that change early. you say "are basically the same, and have been for some time", but it has b= een ~1.5 months since this specific upgrade, not multiple years of following th= e same versions or something. on top of that, the change is only **in the edge branch**. alpine indeed on= ly ships the latest lts in stable releases, nothing changed. personally, i wouldn't have upgraded -lts to 6.1 before it was announced as 'lts' (specifically to curb this kind of confusion), but i also don't think anything wrong was really done here. the edge branch is, well, unstable edg= e, and 6.1 is most likely the next lts, just later rather sooner. > The reason I'm asking is that I ran into a bug when upgrading from=20 > linux-edge v6.1.1 to v6.1.8 (external disks not recognized, yet to be=20 > bisected[1]) and I thought "Hah! I'll just go back to linux-lts", only to= =20 > find out that both are the same versions now :-\ you could use 3.17 i suppose. mixing repositories between branches isn't supported, but for the kernel specifically it should work (no library dependencies), so you could add linux-lts from the 3.17-stable repository. > Does anybody know details behind these versions? as mentioned above, -edge is latest-stable and -lts is latest-lts. on top o= f that, -edge has a completely different configuration. > I thought about posting to ~alpine/devel but that list didn't look too > active and seems to have a spam problem too. it is a working and monitored mailing list just like this one. and just lik= e every mailing list in the world, full of spam :-) > > Thanks for your input, > Christian. > > [0] https://gitlab.alpinelinux.org/alpine/aports/-/commits/master/{main,c= ommunity}/linux-{lts,edge} > [1] https://lore.kernel.org/lkml/4fe9541e-4d4c-2b2a-f8c8-2d34a7284930@ner= dbynature.de/ > --=20 > BOFH excuse #344: > > Network failure - call NBC