public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Update is blocked by ots previous version...?
Date: Fri, 8 Dec 2017 03:36:11 +0100	[thread overview]
Message-ID: <20171208023611.zdkmtwejqupsqorx@solfire> (raw)

Hi,

this morning in its endless wisdom emerge spake to me today:

| WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:
| 
| app-emulation/containerd:0
| 
|   (app-emulation/containerd-1.0.0:0/0::gentoo, ebuild scheduled for merge) conflicts with
|     ~app-emulation/containerd-1.0.0_beta2_p20171019 required by (app-emulation/docker-17.11.0:0/0::gentoo, installed)
|     ^                         ^^^^^^^^^^^^^^^^^^^^^


I removed containerd yesterday and installed it again only to get the same
error this morning again.

Any away around this?

Cheers
Meino





             reply	other threads:[~2017-12-08  2:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  2:36 tuxic [this message]
2017-12-08  3:53 ` [gentoo-user] Update is blocked by ots previous version...? Jalus Bilieyich
2017-12-08  3:58   ` tuxic
2017-12-08  8:18 ` Neil Bothwick
2017-12-08 15:38   ` tuxic

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=20171208023611.zdkmtwejqupsqorx@solfire \
    --to=tuxic@posteo.de \
    --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