From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 4Ip4IQn3OWQEewEASxT56A (envelope-from ) for ; Sat, 15 Apr 2023 02:59:53 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id ELpaIQn3OWRhaQEA9RJhRA (envelope-from ) for ; Sat, 15 Apr 2023 02:59:53 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 3F12410A7C for ; Sat, 15 Apr 2023 02:59:53 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pnUGM-0007ao-Km; Fri, 14 Apr 2023 20:59:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pnUGL-0007aa-Al for guix-devel@gnu.org; Fri, 14 Apr 2023 20:59:33 -0400 Received: from mail-40133.protonmail.ch ([185.70.40.133]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pnUGJ-0002L0-3G for guix-devel@gnu.org; Fri, 14 Apr 2023 20:59:33 -0400 Date: Sat, 15 Apr 2023 00:59:13 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1681520365; x=1681779565; bh=KoF5QR4gJeEExM7r71QxbxLtd5iT1lbwAxKappE7Gfk=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=cTpBrH4x+AY/iYUoyZc38XOsimLgY/XHpL9XWd7wxtEHsdu8aUJoXzj02GqzT/r3n tif0TJHkKbDcDvx7R/37y5az/hglUyy0pvvnwtaIT/NA8JWVKwAKhR6uSONdYnsRvh oQrAbcqJhTt/wMRWaJ8kgdZ9A+njiGnqgw+JX36FKcTu0NUisqJOLCg1lN/81nDjLi 4/YJ3ql3oLeY1TtVluFAzaSmI/fCFhXTtx3hQ3WzHlYbYFaEldpZBsPRvqJplYfBuo I6Y6tkuyzKXv7lN0y0ZsUluMwbnhMQKRgbek2v85k16BX0THyvOR4jI3rp6SW9hUgW qzrCkqwWPiNrg== To: Josselin Poiret From: John Kehayias Cc: guix-devel@gnu.org Subject: =?utf-8?Q?Re:_A_Joyous_Core-Updates_Week-End_=F0=9F=8E=89?= Message-ID: <87fs9255b6.fsf@protonmail.com> In-Reply-To: <87fs96ukro.fsf@jpoiret.xyz> References: <87fs96ukro.fsf@jpoiret.xyz> Feedback-ID: 7805494:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.70.40.133; envelope-from=john.kehayias@protonmail.com; helo=mail-40133.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Seal: i=1; s=key1; d=yhetil.org; t=1681520393; a=rsa-sha256; cv=none; b=Vok7gZQYCoGc5Glaom6l2hMlk6mOkE8NfsqiMPu0wwNKs291yjnf37ZGfVUuRwKBRVBqWH A4vE7diFmAZweZAMP43uHYYlkoZAsd/01S4bf/ydedHhlSDrHKcMKaBmEDe18IdTF7b+gi mQeSsZuAxuzp2+GAaHWkZ+myhPqZUXla3prJQZI1SnqpJn6VRFc4dv3roFeGYJ/rLH+ZmG njDEpRafK8UNuWDhYzFiooFs3zhDmnN0HwExEyWT/BXgZuwVYnmNxyFnR8w25vg5LbSE51 HqMbATP+EGcJit5RRtMFXS3fCe/SXz89WrlbqS1GHALk8fFFupa0UjLphQod5g== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=cTpBrH4x; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=quarantine) header.from=protonmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1681520393; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=KoF5QR4gJeEExM7r71QxbxLtd5iT1lbwAxKappE7Gfk=; b=DR4XAWcjEQUUlUItaxsBDc/ag5k9IjTP3uXuj0sHH7IRS8XgWzlGGoHhQzRi/4Hn5RX3u/ DaK96VyskWKfoGymINF2nYL3N2mKNAs2A+aCND8HoPeuBkoLKGgvb5zldYFB4y+NaeX6Xt dWPp9BYxODhQmRDf6kZa4q13JOvdlDnBr4sgYNCj2dl88/6hK1spAYue6zgy//wGHTTmX2 aDFGSpAcFaKUVQepkCT/SE/QQcFkzIlog+5ECy3qMOtXEq2ZoSAi7OtiijwV81syqprhCt 6Rl2/sBveb9K7ras01pzdiClKIRh58ci8OEpTdah10GlLHITcP8oUCoXunziYQ== X-Migadu-Queue-Id: 3F12410A7C Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=cTpBrH4x; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=quarantine) header.from=protonmail.com X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -6.44 X-Spam-Score: -6.44 X-TUID: RiwrxcqdCn1N Hi Guix, On Wed, Apr 12, 2023 at 12:16 AM, Josselin Poiret wrote: > Hello everyone, > > It's that time of the year again! Merging core-updates! Do you *want* > glibc 2.35, gcc 11 as default, mesa 22, python 3.10, and more?! Here's > your chance! > Time flies! Big thanks to Andreas especially for really shepherding (no pun= intended) us to an already good state. > What is core-updates you ask? It's the big branch where all changes > that affect significant parts of the dependency graph are pushed, to > avoid world rebuilds, and also to test them out. This branch is then > merged back into the main one periodically, and of course, this is never > painless, as upgrading important dependencies like glibc or gcc are > going to cause issues. Note that this workflow might change in the near > future though, see [1]. > > Some people have been hard at work fixing most of the build issues, and > we have most of the big changes sorted out now. However, it's > impossible for the usual suspects to cover every single package, so we > would like to ask the wider community for their help with the merge. > Anyone can help, and in various ways (you don't need to know how to code > in Guile!). > > This week-end (15=E2=80=9316 April), let's get everyone together and work= on > core-updates! Here's what you can do to help: > Thanks for organizing! I know many are in Europe (US here) so I may miss a = lot of people due to time zone/schedule, but looking forward to helping out. I've been aw= ay from Guix a bit due to some other stuff but hope to put my eyes for review and commit a= ccess to good use to help out with everyone's hard work. > > 1) Use `guix time-machine` to test out your packages. > > If you have a package manifest lying around (you can get one out of your > profile by using `guix package --export-manifest`), you can see which > packages are available by doing `guix time-machine --branch=3Dcore-update= s > -- weather -m MANIFEST.SCM`! > > You can also test the packages themselves by doing `guix time-machine > --branch=3Dcore-updates -- shell YOUR-PACKAGE`, at which point you'll be > in a shell with the new package available. You can then try it out to > see if it works properly! > I also want to stress this point, more testing of your favorite package (or= reconfiguring your system to core-updates if you are feeling more adventurous) is really = helpful. So don't be afraid even if you have no idea what's happening under the hood. > > 2) Hack on `core-updates`. > > This is better to do beforehand: add a new worktree for core-updates > (you don't want to prune all of the .go files when switching between > master and core-updates, don't you?) using `git worktree add > ../core-updates/ core-updates`. > > You can then enter that directory and follow the instructions from the > manual, at "(guix)Building from Git". You will have a checkout ready to > work on core-updates! You can then try to build your manifest from the > checkout and see if everything builds, and try fixing the ones that > don't. > > > 3) Hang out on #guix and on the MLs. > > Follow what fellow members of the community are doing and struggling > with, cheer them on and/or offer them your assistance! Feel free to > reply to this if you have any questions about the process, or with your > attempts, struggles and successes! > Question on procedure: are we going to be posting every patch to guix-patch= es and waiting for QA to build? Or only for not trivial (whatever that means) patches? I g= uess I'm asking if this will be a sort of sprint weekend and larger changes/cleanup in the = aftermath? This depends on context of course, but in light of recent discussions on patch p= ushing, QA, and teams (that I need to catch up on) I wanted to see what we were doing here. > > See you this week-end. > > [1] > > Best, Thanks again, see you all on IRC and git logs this weekend! John