From debbugs-submit-bounces@debbugs.gnu.org Thu May 06 20:57:01 2021 Received: (at 48214) by debbugs.gnu.org; 7 May 2021 00:57:01 +0000 Received: from localhost ([127.0.0.1]:40742 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1leond-00034j-FJ for submit@debbugs.gnu.org; Thu, 06 May 2021 20:57:01 -0400 Received: from knopi.disroot.org ([178.21.23.139]:55680) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1leona-00034Z-5q for 48214@debbugs.gnu.org; Thu, 06 May 2021 20:57:00 -0400 Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id D917853B49; Fri, 7 May 2021 02:56:55 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23DrNKWaOwHW; Fri, 7 May 2021 02:56:54 +0200 (CEST) References: <87a6pbjlao.fsf@disroot.org> <871ramoogd.fsf@nckx> <87eeekiq76.fsf@disroot.org> <87zgx7hpy0.fsf@disroot.org> <87tunfhjiy.fsf@disroot.org> <87eeejd1kx.fsf@gnu.org> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1620349014; bh=lCFOr+ZcPu/Ka0C9GHJhuUImWSMyhH6RDqMZz6BGnfw=; h=References:From:To:Cc:Subject:In-reply-to:Date; b=P8IbJDaU+ZKQ7GVLfUziUxiuY/5RehYpNfq2sm/KasgyzkImrKw+b1WIi27xGhAZO zwpmrmBeFlv0XQBtCJINhkssusWSlk72myiG05oAU4MPFWtcusv3xDzkdZlTqDA2oM qmqw004h85wW2nXIrjTFZANESZXZf+RPZVYWROvE1foKjNs0EVsVH3Flygz+uchWer wKTTNPXeJl40UkV8ovDHMunXtQhR17bsEKs1UGdJhfy9e95G+7GZTkM9zDxOpdvEMV LPO1Ea7ZFqC98s/aV2BZbzm6mz8h0weXYu8q9oobLYOeXVQ9vGxsrO1mz7/1szMs4V mqh5YwalJgzjQ== From: Bone Baboon To: Ludovic =?utf-8?Q?Court=C3=A8s?= Subject: Re: bug#48214: inetutils-1.9.4 build fails In-reply-to: <87eeejd1kx.fsf@gnu.org> Date: Thu, 06 May 2021 20:55:35 -0400 Message-ID: <87lf8rgy60.fsf@disroot.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 48214 Cc: 48214@debbugs.gnu.org, me@tobias.gr X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Ludovic Court=C3=A8s writes: >> How can I use a package definition from core-updates with guix build or >> in a system configuration if it is not available on Guix's master >> branch? > > You can do better :-), you can install 2.0 from master like so: > > guix install inetutils --with-latest=3Dinetutils Thank you for sharing that command. I prefer to build locally over using substitutes. When I try to run `guix build inetutils --no-substitutes --with-latest=3Dinetutils` it does not complete because there is an interactive prompt. The prompt says "Would you like to add this key to your keyring ''?". I have a substitute server that is sequentially building packages unattended and this would cause it to become stuck and make no further progress. >> On the inetutils mailing list it was suggested that I try inetutils 2.0 >> on the core-updates branch. I can successfully build inetutils 2.0 from >> the core-updates branch even with IPv6 disabled. >> >> What is the purpose of the core-updates branch? > > The =E2=80=98core-updates=E2=80=99 branch contains updates to core packag= es and core > Guix functionality that entails a rebuild of all the packages. In that > branch we put package upgrades that would otherwise lead to too many > rebuilds (info "(guix) Submitting Patches"). Thank you for explaining this. --- What is the process for a package to be brought into master from core-updat= es? --- I would rebuild all the packages on my system if I could use inetutils 2.0. Is there a way that I can rebuild all the packages I am using that depend on inetutils to use inetutils 2.0 (or more generally any newer version of package from core-updates)? >> Can the Guix master branch provide inetutils 2.0 instead of 1.9.4? > > No: =E2=80=98guix refresh -l inetutils=E2=80=99 shows that almost 2,000 p= ackages depend > on inetutils. > > That said, if needed, =E2=80=98master=E2=80=99 could provide 2.0 in addit= ion to 1.9, as > is done for GDB for instance. Would having multiple versions of inetutils in master also create multiple versions of packages that depend on inetutils for example a version of isc-dhcp that depends on inetutils 1.9 and another that depends on inetutils 2.0? --- Not having inetutils 2.0 in master appears to break how I connect to the internet using Guix if I do both of these: * Disable IPv6 ** See my previous email in this thread that explains the rationale on why I am disabling IPv6. * Build from source isc-dhcp fails to build because it depends on inetutils 1.9 which is failing. I am using isc-dhcp when I connecting to the internet. >> What are the reasons I might not want to use a package from the >> core-updates branch? > > =E2=80=98core-updates=E2=80=99 is where we put core changes as I wrote, i= ncluding > experimental changes. That branch also does not receive security > updates in a timely fashion. So it=E2=80=99s really a branch for develop= ers > working on core improvements. Thank you for explaining this.