From: Mark Wielaard <mark@klomp.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: Tom de Vries <tdevries@suse.de>, Simon Marchi <simark@simark.ca>,
buildbot@sourceware.org,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware)
Date: Wed, 15 Jun 2022 21:48:04 +0200 [thread overview]
Message-ID: <Yqo3dC5PocUkNmGG@wildebeest.org> (raw)
In-Reply-To: <caa4c55a-be3f-004e-23f0-f854a44bb7ce@suse.cz>
Hi Martin,
On Wed, Jun 15, 2022 at 09:18:38PM +0200, Martin Liška wrote:
> > Is that a opensuse leap packaging bug?
>
> Note we don't have the package in Leap and this is what I see when building the current Containerfile-opensuse-leap:
>
> STEP 3/10: RUN zypper -n install gcc gcc-c++ libtool ccache valgrind isl-devel mpc-devel mpfr-devel gmp-devel patch util-linux diffutils iproute2 bsdtar cpio procps coreutils make git autoconf dejagnu automake gettext-devel bison flex bzip2 libbz2-devel xz xz-devel gzip zlib-devel zstd libzstd-devel findutils file tar curl libarchive-devel libcurl-devel libmicrohttpd-devel sqlite-devel libelf-devel libdw-devel libdebuginfod-devel xmlto poppler-tools libxslt docbook-dtds docbook-xsl-stylesheets libxml2-devel dos2unix dpkg python3-devel python3-mock python3-rpm python3-pyxdg python3-pip openmpi-devel gdb help2man wget texinfo libexpat-devel glibc-devel glibc-locale
> ...
> 'libdebuginfod-devel' not found in package names. Trying capabilities.
> No provider of 'libdebuginfod-devel' found. ['--plus-content debug'?]
That is surprising, I did test locally before adding the package. And
clearly the buildbot/docker builder could find the package and build
the image. And when I do it locally it also seems to work:
$ podman build -t builder-opensuse-leap -f builder/containers/Containerfile-opensuse-leap builder/containers
[...]
Retrieving package libdebuginfod-devel-0.185-150400.3.35.x86_64 (129/429), 23.4 KiB ( 8.9 KiB unpacked)
Retrieving: libdebuginfod-devel-0.185-150400.3.35.x86_64.rpm [done]
[...]
(129/429) Installing: libdebuginfod-devel-0.185-150400.3.35.x86_64 [.......done]
[...]
Successfully tagged localhost/builder-opensuse-leap:latest
395a607b4cd69683b3212862d3dd3c8557b2a581f210cb903c1168ecd5f01b16
$ 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?
> > BTW. To debug such builder container issues you can use this IMHO handy
> > guide:
> > https://sourceware.org/git/?p=builder.git;a=blob;f=README_containers;hb=HEAD
> >
> >> CC buildbot list, where you can propose such patches yourself if you
> >> notice anything else missing.
> >>
> >> Cheers,
> >>
> >> Mark
next prev parent reply other threads:[~2022-06-15 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YmbmguMq2Aq+BzAX@wildebeest.org>
[not found] ` <524b04b7-a78c-7aae-4605-b40f61e6830c@arm.com>
[not found] ` <YmhzY4c3pOPLRgSw@wildebeest.org>
[not found] ` <16fe426d-c436-f030-dc43-0e81e7f0e853@arm.com>
[not found] ` <20220428141957.GB23335@gnu.wildebeest.org>
[not found] ` <m3zgk5clif.fsf@fitzsim.org>
[not found] ` <20220428162803.GD23335@gnu.wildebeest.org>
[not found] ` <20220429200422.GB7305@gnu.wildebeest.org>
[not found] ` <20220501194445.GB30898@gnu.wildebeest.org>
[not found] ` <f12d07da-8692-5321-95e1-8b2fb5a84cf1@simark.ca>
[not found] ` <YnG8lzwMZwRn+wAo@wildebeest.org>
[not found] ` <28a953d1-9fdc-e4f7-18cc-0b7b1a4e88ea@suse.de>
2022-06-15 11:09 ` Mark Wielaard
2022-06-15 14:38 ` Mark Wielaard
2022-06-15 19:18 ` Martin Liška
2022-06-15 19:48 ` Mark Wielaard [this message]
2022-06-16 4:09 ` Martin Liška
2022-06-16 21:19 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yqo3dC5PocUkNmGG@wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=mliska@suse.cz \
--cc=simark@simark.ca \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).