1 |
Blocking the package which gets blocked by its previous one? |
2 |
Is this a wprkaround, a solution ? |
3 |
Feels weird... |
4 |
|
5 |
|
6 |
On 12/07 09:53, Jalus Bilieyich wrote: |
7 |
> Put in package.mask: |
8 |
> |
9 |
> >=app-emulation/containerd-1.0.0:0/0 |
10 |
> |
11 |
> On 12/07/2017 08:36 PM, tuxic@××××××.de wrote: |
12 |
> > Hi, |
13 |
> > |
14 |
> > this morning in its endless wisdom emerge spake to me today: |
15 |
> > |
16 |
> > | WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: |
17 |
> > | |
18 |
> > | app-emulation/containerd:0 |
19 |
> > | |
20 |
> > | (app-emulation/containerd-1.0.0:0/0::gentoo, ebuild scheduled for merge) conflicts with |
21 |
> > | ~app-emulation/containerd-1.0.0_beta2_p20171019 required by (app-emulation/docker-17.11.0:0/0::gentoo, installed) |
22 |
> > | ^ ^^^^^^^^^^^^^^^^^^^^^ |
23 |
> > |
24 |
> > |
25 |
> > I removed containerd yesterday and installed it again only to get the same |
26 |
> > error this morning again. |
27 |
> > |
28 |
> > Any away around this? |
29 |
> > |
30 |
> > Cheers |
31 |
> > Meino |
32 |
> > |
33 |
> > |
34 |
> > |
35 |
> > |
36 |
> |