public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] app-emulation/docker-20.10.2 ebuild is borked?
Date: Sat, 9 Jan 2021 03:46:10 +0200	[thread overview]
Message-ID: <rtb1t2$auh$1@ciao.gmane.io> (raw)

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.

That's a stupid requirement and not needed, as it breaks realtime 
scheduling with rtkit (PulseAudio for example.)

So I copied the ebuild to my local overlay and removed ~RT_GROUP_SCHED 
from CONFIG_CHECK. Portage now aborts with:

   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...

Help?



             reply	other threads:[~2021-01-09  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09  1:46 Nikos Chantziaras [this message]
2021-01-09  3:02 ` [gentoo-user] app-emulation/docker-20.10.2 ebuild is borked? Ionen Wolkens
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='rtb1t2$auh$1@ciao.gmane.io' \
    --to=realnc@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