From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: Can't build rdma-core's azp image
Date: Mon, 4 May 2020 22:09:06 -0300 [thread overview]
Message-ID: <20200505010906.GD26002@ziepe.ca> (raw)
In-Reply-To: <519a9c33-fa1b-7439-fa6a-7a54b69bde0b@amazon.com>
On Sun, Apr 19, 2020 at 09:37:45AM +0300, Gal Pressman wrote:
> Unpacking libc6:arm64 (2.27-3ubuntu1) ...
> dpkg: dependency problems prevent configuration of libc6:i386:
> libc6:i386 depends on libgcc1; however:
> Package libgcc-s1:i386 which provides libgcc1 is not configured yet.
>
> dpkg: error processing package libc6:i386 (--configure):
> dependency problems - leaving unconfigured
> dpkg: dependency problems prevent configuration of libgcc-s1:ppc64el:
> libgcc-s1:ppc64el depends on libc6 (>= 2.17); however:
> Package libc6:ppc64el is not configured yet.
>
> dpkg: error processing package libgcc-s1:ppc64el (--configure):
> dependency problems - leaving unconfigured
> Errors were encountered while processing:
> libc6:i386
> libgcc-s1:ppc64el
> E: Sub-process /usr/bin/dpkg returned an error code (1)
Wow, that is actually an APT bug... Must be from old age :O
Ah we can hack around that with this:
https://github.com/jgunthorpe/rdma-plumbing/pull/new/azp_fix
Let me know if it works
Now that github has docker hosting I wonder if we should try to host a
copy of the docker image there.. Their docker hosting is a pain last I
looked though..
Jason
next prev parent reply other threads:[~2020-05-05 1:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 15:47 Can't build rdma-core's azp image Gal Pressman
2020-04-07 17:28 ` Leon Romanovsky
2020-04-07 18:06 ` Jason Gunthorpe
2020-04-08 6:35 ` Gal Pressman
2020-04-16 7:05 ` Gal Pressman
2020-04-17 16:21 ` Jason Gunthorpe
2020-04-19 6:37 ` Gal Pressman
2020-05-05 1:09 ` Jason Gunthorpe [this message]
2020-05-05 6:40 ` Gal Pressman
2020-05-05 13:21 ` Jason Gunthorpe
2020-05-05 14:05 ` Gal Pressman
2020-05-26 6:25 ` Gal Pressman
2020-05-26 19:23 ` Jason Gunthorpe
2020-05-27 7:35 ` Gal Pressman
2020-07-26 7:05 ` Gal Pressman
2020-07-26 23:19 ` Jason Gunthorpe
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=20200505010906.GD26002@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=galpress@amazon.com \
--cc=linux-rdma@vger.kernel.org \
/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 NNTP newsgroup(s).