| 1 |
n952162@×××.de wrote: |
| 2 |
> !!! Multiple package instances within a single package slot have been pulled |
| 3 |
> !!! into the dependency graph, resulting in a slot conflict: |
| 4 |
> |
| 5 |
> sys-apps/portage:0 |
| 6 |
> |
| 7 |
> How should I go about handling this? |
| 8 |
> |
| 9 |
> Slot are explained somewhere as allowing multiple packages to have different versions of the same providing package. Why should there be conflicts? Is there a limited number of slots or something? Why is a slot conflict a problem - each dependent package can use its own slot ... |
| 10 |
> |
| 11 |
> Following this message there are a number of "paragraphs", each introduced with a line like the "sys-apps/portage:0" line, above. Each paragraph contains multiple "clauses", apparently representing different versions of the package starting the "paragraph" |
| 12 |
> |
| 13 |
> Each seems to be terminated with a status: |
| 14 |
> - argument |
| 15 |
> - installed |
| 16 |
> - ebuild scheduled for merge |
| 17 |
> |
| 18 |
> Where's the problem? |
| 19 |
> |
| 20 |
> There must be a problem because it goes on to say: |
| 21 |
> |
| 22 |
> "It may be possible to solve this problem by using package.mask to |
| 23 |
> prevent one of those packages from being selected. However, it is also |
| 24 |
> possible that conflicting dependencies exist such that they are |
| 25 |
> impossible to satisfy simultaneously. If such a conflict exists in |
| 26 |
> the dependencies of two different packages, then those packages can |
| 27 |
> not be installed simultaneously." |
| 28 |
> |
| 29 |
> I can solve the problem by preventing *one* of the packages from being selected? |
| 30 |
> Let's see, I have 3 such paragraphs, two with 2 clauses each and one with 6 clauses. If I pick one, everything will be fine? |
| 31 |
> |
| 32 |
> It then suggests looking at the MASKED PACKAGES section of the emerge man page. But that has to do with experimental or development packages. My profile is "stable" - there's no reason why I should have any of those, is there? |
| 33 |
> |
| 34 |
> It goes on, but I think those are other issues which I will raise in a subsequent post. |
| 35 |
> |
| 36 |
> |
| 37 |
|
| 38 |
|
| 39 |
You need to post the whole output so others can see what is causing the |
| 40 |
conflict. There are a few on this list who are very good at parsing the |
| 41 |
output and finding a way to work through it. |
| 42 |
|
| 43 |
Dale |
| 44 |
|
| 45 |
:-) :-) |
Archives