public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>
Cc: Simon Marchi <simark@simark.ca>,
	buildbot@sourceware.org, Tom de Vries <tdevries@suse.de>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdb builder status (Was: Adding binutils to the GNU Toolchain buildbot on sourceware)
Date: Thu, 16 Jun 2022 06:09:13 +0200	[thread overview]
Message-ID: <b7159e41-22e1-47b7-0615-12808b0678d2@suse.cz> (raw)
In-Reply-To: <Yqo3dC5PocUkNmGG@wildebeest.org>

On 6/15/22 21:48, Mark Wielaard 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

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.

Cheers,
Martin

  reply	other threads:[~2022-06-16  4:09 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
2022-06-16  4:09                               ` Martin Liška [this message]
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=b7159e41-22e1-47b7-0615-12808b0678d2@suse.cz \
    --to=mliska@suse.cz \
    --cc=buildbot@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.org \
    --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).