Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware)

[Mark Wielaard <mark@klomp.org>]

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

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

[-- Attachment #2: 0001-README_containers-Document-build-pull-and-system-pru.patch --]
[-- Type: text/x-diff, Size: 1819 bytes --]

From 530d374997b18b46965de4c93e86543e1d2b89f5 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
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