From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Getting =?utf-8?Q?=E2=80=98core-updates=E2=80=99?= merged Date: Sat, 17 Nov 2018 15:14:47 +0100 Message-ID: <87muq7oko8.fsf_-_@gnu.org> References: <588d8f0c-703e-7897-b9b8-39d29c453854@riseup.net> <8736s3vq6l.fsf@elephly.net> <875zwz5yq4.fsf@fastmail.com> <87o9aovqor.fsf@gnu.org> <87ftw0u3kw.fsf@elephly.net> <87wopcsoro.fsf@gnu.org> <20181116230358.1ef639a7@alma-ubu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54208) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gO1N4-00062C-Lp for guix-devel@gnu.org; Sat, 17 Nov 2018 09:14:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gO1N3-0006yQ-Hv for guix-devel@gnu.org; Sat, 17 Nov 2018 09:14:50 -0500 In-Reply-To: <20181116230358.1ef639a7@alma-ubu> (=?utf-8?Q?=22Bj=C3=B6rn?= =?utf-8?Q?_H=C3=B6fling=22's?= message of "Fri, 16 Nov 2018 23:03:58 +0100") 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+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?Q?Bj=C3=B6rn_H=C3=B6fling?= Cc: guix-devel@gnu.org Hi! Bj=C3=B6rn H=C3=B6fling skribis: > On Fri, 16 Nov 2018 22:20:27 +0100 > ludo@gnu.org (Ludovic Court=C3=A8s) wrote: >> Ricardo Wurmus skribis: [...] >> > I would prefer to have core-updates in the next release. This has >> > been delayed for much too long. This would also avoid the bad look >> > for a new release to have somewhat outdated core packages. >> > >> > If we can=E2=80=99t get core-updates ready within the next few weeks I= won=E2=80=99t >> > object to a release without it, but I think we should really try.=20=20 >>=20 >> Yes, that makes sense to me. >>=20 >> So everyone: let=E2=80=99s join forces and get =E2=80=98core-updates=E2= =80=99 finally merged! > > What is to do for core-updates to succeed? Is it "just" that > hydra/berlin need to build it, or is there anything a human being can > do (Or is the former necessary to define the latter?)? > > Is there a list of open/unresolved tasks? What remains to be done is mostly (1) ensuring that there=E2=80=99s no significant regression in terms of build failures compared to =E2=80=98mast= er=E2=80=99, and (2) making sure GuixSD boots and works fine. For #1, a simple test is to try and upgrade your profile and see if everything builds and works well. In addition, you can look at these dashboards to identify build failures that need to be addressed: https://hydra.gnu.org/jobset/gnu/core-updates https://berlin.guixsd.org/jobset/core-updates-core-updates For #2, running =E2=80=9Cmake check-system=E2=80=9D, or at least the inexpe= nsive subset of system tests (the expensive tests are the installation tests) should give a good overview=E2=80=94Mark already reported an issue at . The next step of course is to try it on the bare metal for your own system config. If we all do our share of testing, this can actually be pretty fast. If today is a rainy day, here=E2=80=99s a good activity for you! :-) Thanks, Ludo=E2=80=99.