From: Ionen Wolkens <sudinave@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] app-emulation/docker-20.10.2 ebuild is borked?
Date: Fri, 8 Jan 2021 22:02:44 -0500 [thread overview]
Message-ID: <X/kc1JUTceJXiMNW@eversor.ev.qc.to> (raw)
In-Reply-To: <rtb1t2$auh$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
On Sat, Jan 09, 2021 at 03:46:10AM +0200, Nikos Chantziaras wrote:
> Portage was trying to update docker from 20.10.1 to 20.10.2. However, it
> aborts with:
>
> ERROR: setup
> CONFIG_RT_GROUP_SCHED: is not set when it should be.
I don't believe this check aborts the build, maybe something else
happened? At least it doesn't for me.
> ERROR: compile
> ERROR: app-emulation/docker-20.10.2::local failed (compile phase):
> USE Flag 'selinux' not in IUSE for app-emulation/docker-20.10.2
>
> OK, so I added "selinux" to IUSE. Portage now aborts with:
>
> Building: bundles/dynbinary-daemon/dockerd-dev
> GOOS="" GOARCH="" GOARM=""
> cannot find package "github.com/docker/docker/cmd/dockerd" in any of:
> /usr/lib/go/src/github.com/docker/docker/cmd/dockerd (from $GOROOT)
>
> /var/tmp/portage/app-emulation/docker-20.10.2/work/docker-20.10.2/src/github.com/docker/docker/cmd/dockerd
> (from $GOPATH)
> * ERROR: app-emulation/docker-20.10.2::local failed (compile phase):
> * dynbinary failed
>
> Unfortunately, 20.10.1 was deleted from portage and I cannot go back as
> docker-cli has already been updated to 20.10.2...
>
I replied to https://bugs.gentoo.org/764524#c1 which should answer both
issues. I'm assuming some extra changes were accidentally merged while adding
cli USE.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-09 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 1:46 [gentoo-user] app-emulation/docker-20.10.2 ebuild is borked? Nikos Chantziaras
2021-01-09 3:02 ` Ionen Wolkens [this message]
2021-01-09 3:22 ` [gentoo-user] " Nikos Chantziaras
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=X/kc1JUTceJXiMNW@eversor.ev.qc.to \
--to=sudinave@gmail.com \
--cc=gentoo-user@lists.gentoo.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