From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 46514385734F; Thu, 16 Jun 2022 21:19:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 46514385734F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x09.wildebeest.org [172.31.17.139]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id E246A302FB88; Thu, 16 Jun 2022 23:19:48 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 491B02E80832; Thu, 16 Jun 2022 23:19:48 +0200 (CEST) Date: Thu, 16 Jun 2022 23:19:48 +0200 From: Mark Wielaard To: Martin =?utf-8?B?TGnFoWth?= Cc: Simon Marchi , buildbot@sourceware.org, Tom de Vries , "gdb-patches@sourceware.org" Subject: Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware) Message-ID: References: <20220429200422.GB7305@gnu.wildebeest.org> <20220501194445.GB30898@gnu.wildebeest.org> <28a953d1-9fdc-e4f7-18cc-0b7b1a4e88ea@suse.de> <9576d8d18b533c753df75a2cdb6ca9d786d71ff3.camel@klomp.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="nEuaF6xcYdSuVCE/" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-11.5 required=5.0 tests=BAYES_00, GIT_PATCH_0, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: buildbot@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "The https://builder.sourceware.org/ buildbot" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2022 21:19:52 -0000 --nEuaF6xcYdSuVCE/ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi Martin, On Thu, Jun 16, 2022 at 06:09:13AM +0200, Martin Liška wrote: > > $ podman run --name opensuse-leap -ti --entrypoint /bin/bash builder-opensuse-leap > > builder@9d1600f0c01e:~> rpm -q libdebuginfod-devel > > libdebuginfod-devel-0.185-150400.3.35.x86_64 > > > > Are the container files pulling from the wrong repositories? > > Yeah, I was still using 15.3, while we released 15.4 in the meantime. > Apparently the following helps: > > podman build ... --pull=true Aha. The reason this wasn't necessary on the container builders was because they do a docker system prune -a -f every Sunday to get a fresh image. Note that this did also cause libabigail to turn green on opensuse leap (because it got a newer elfutils): https://sourceware.org/pipermail/libabigail/2022q2/004430.html > And about: > > ls -lah /usr/lib64/libdebuginfod-0.185.so > ls: cannot access '/usr/lib64/libdebuginfod-0.185.so': No such file or > directory > > It's really a broken package and I'm going to fix it (it's missing > Requires: libdebuginfod1 = %{version} > > In the meantime I install it manually in this podman file. Thanks! I'll add this to the README_containers. Cheers, Mark --nEuaF6xcYdSuVCE/ Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-README_containers-Document-build-pull-and-system-pru.patch" >From 530d374997b18b46965de4c93e86543e1d2b89f5 Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 16 Jun 2022 23:18:43 +0200 Subject: [PATCH] README_containers: Document build --pull and system prune -a -f --- README_containers | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README_containers b/README_containers index 66ac558..c414f72 100644 --- a/README_containers +++ b/README_containers @@ -69,8 +69,9 @@ Building the image ------------------ Note that the container files are rebuild once a week for the -builder.sourceware.org workers. So although unlikely it might be that -a freshly build container contains slightly newer versions of the +builder.sourceware.org workers (each Sunday the container builders run +docker system prune -a -f). So although unlikely it might be that a +freshly build container contains slightly newer versions of the packages than the one that ran on the builder.sourceware.org worker. The containers contain all build dependencies for all projects @@ -85,6 +86,10 @@ podman build -t builder-debian-stable \ -f builder/containers/Containerfile-debian-stable \ builder/containers +If you want to make sure you get the latest base image add --pull +which will attempt to pull a newer version of the image even if you +already got one locally. + Or use docker instead of podman, they take the same arguments (although the last PATH is optional in some versions). @@ -109,4 +114,7 @@ container and enter it as root: podman start debian-stable podman exec -it --user root debian-stable apt install emacs +After you are done you can reclaim all disk space used by the images +and containers by running: podman system prune -a -f + The same works with the docker command. -- 2.30.2 --nEuaF6xcYdSuVCE/--