From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:8:6d80::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id b8M3OeeQYmC/gQAAgWs5BA (envelope-from ) for ; Tue, 30 Mar 2021 04:45:59 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id I4PsMeeQYmCNSgAA1q6Kng (envelope-from ) for ; Tue, 30 Mar 2021 02:45:59 +0000 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 39F1C1CBE7 for ; Tue, 30 Mar 2021 04:45:59 +0200 (CEST) Received: from localhost ([::1]:40144 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lR4OD-0000HF-37 for larch@yhetil.org; Mon, 29 Mar 2021 22:45:57 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37720) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lR4O1-0000FV-2E for help-guix@gnu.org; Mon, 29 Mar 2021 22:45:46 -0400 Received: from lepiller.eu ([2a00:5884:8208::1]:35442) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lR4Nw-0007hp-Aw for help-guix@gnu.org; Mon, 29 Mar 2021 22:45:44 -0400 Received: from lepiller.eu (localhost [127.0.0.1]) by lepiller.eu (OpenSMTPD) with ESMTP id 7ee9ab08; Tue, 30 Mar 2021 02:45:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date :in-reply-to:references:mime-version:content-type :content-transfer-encoding:subject:to:from:message-id; s=dkim; bh=Kr2/aYYVDt7BHzTsv8VBRsEzfJF8TvhxdmOAThGBnVc=; b=GOpXYdgapV5O nMoYqVIna7vYpE+oRaiPGJzZZhtNHKHLrV1L3YpQ4q6+4cRWhbgFC7jwHSwIXgJE t7E/h0xV+oJ2lgdYb+MXfF8Nvb1g0E6TjyP7NgRpSRKaX6XfJWieh5STgNHlhcrf WNUERMjOTRuseFjyqWFTEzYACIEdmZM67+NicD/x+V5B36fSv0YT3C5KkS7awV9M RKUbkApv9eXAp43WbkE3+7KK7v1y/O7btAVqNCOWV/SWzcOl+WCXMCVCXCRXWQUm RDShWOx1CGiYFx7xFzok5YwMY0dlNFsRelhIPfdOMDvrrXEQ5kE+EE/LAb+TmqKS GAKu6uFT9Q== Received: by lepiller.eu (OpenSMTPD) with ESMTPSA id df31ba30 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 30 Mar 2021 02:45:30 +0000 (UTC) Date: Mon, 29 Mar 2021 22:45:24 -0400 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: build broken packages handling To: help-guix@gnu.org,Andy Tai From: Julien Lepiller Message-ID: <7BFD9237-0E07-46EE-B736-2E368A294106@lepiller.eu> Received-SPF: pass client-ip=2a00:5884:8208::1; envelope-from=julien@lepiller.eu; helo=lepiller.eu 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1617072359; h=from:from:sender:sender: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:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=UfaT66f089ytQTEL7HCmckNOiIwscYdFrLylDcKrlnk=; b=m2pUZRBQMjZSprGHDFIoqYTWHxlkW9R5+bg5Zj+PHJOoQ9X2DRKFgYpjaqST/5fzidaeB1 TgtQgHQyd9aVejboo1KhWPrnOGUFY/nlrx7wA4sIAW1q0d1sQO0ZvpN3S5TpSa2KxQyueY BQKKms7UsvltXtSfwqUe3OoiYe6ONEvcztIJ9TI4PDTK7AG7qWaEMNzhsZVr2xc/7/5Qhi Xlp7/OyuX6XNcJe4pyJF+YP9bquBu4YxtSz+uhzZ5UNX4hE4LlToBQEbynogC3FDBwVfmV +eG4JjHROKIYRAB+TMGuWAZmWRzIRGTmAV1sLnr1c4W7XdyOLgCLTIdJ6bMUew== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1617072359; a=rsa-sha256; cv=none; b=DQ3KrOgIWH1VUrHbqc5yh77k876qCChZituRBHby/IhM+6Th/Xyod0o1i1Vh9X/w/YBGEc vR7LDFXW27nnRk8jfdKMfPj4tUrgA8WuqDsOthhFk8xmcaB8YO8pt+cBABJqNNeZ+MYtWd n4brSXecHRoCclwcIq/5yf8w5lh9g5TX+PVOrlMJHDFHP27tEM+cIOqxwK81pGWiclHGi1 DI3rV6LnxChCjb/NRc9hWWweCS7FVDDllbqCJeTJo3hifIaV+Vrp+RcBfquSaPOllXeOfV fcK6WfJGnVfzlIdBr1oUI9vUxxymPFxTRH58N5R1Kr3cd5DT/2wQnPKRBbJZlA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=GOpXYdga; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Spam-Score: -1.62 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=GOpXYdga; dmarc=pass (policy=none) header.from=lepiller.eu; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Queue-Id: 39F1C1CBE7 X-Spam-Score: -1.62 X-Migadu-Scanner: scn0.migadu.com X-TUID: ILp8hJfM78f3 Hi Andy, Answers below=2E Le 29 mars 2021 16:02:37 GMT-04:00, Andy Tai a =C3=A9cri= t : >Two questions: > >1=2E When submitting an updated package definition, is there an easy >way to check if other packages may be broken by this update? Right >now it is easy to check if a package builds with updated package >definition; but it is not easy to see if committing it will break >others=2E I can't check right now, but I think the contributing section in the manua= l describes this=2E You might want to have a look :) To list leaf packages that are affected by a change (and the number of pac= kages affected, including non-leaf), you can use guix refresh: guix refresh -l foo Will tell you which leaf packages are affected if you modify foo=2E Build = them all if the number is low=2E If the number of dependents is high enough= to qualify for staging or core-updates, then checking only some of them is= ok=2E > >2=2E If a package is not building in guix, should a bug be filed against >it? Ot there is a way, a CI web interface or something that shows all >existing packages whose builds are broken? Yes, if the package is important to you, please file a bug report with det= ails about the failing build, to bug-guix=2E Don't bother upstream :) We have ci=2Eguix=2Egnu=2Eorg, which is our build farm=2E You can use the = search box to look for failing builds=2E If you manage to fix some of them, definitely send a patch! > >Thanks