| 1 |
Alan McKinnon wrote: |
| 2 |
> emerge -e --keep-going @world |
| 3 |
> shows output like this when a build fails: |
| 4 |
> |
| 5 |
> * One or more packages are either masked or have missing dependencies: |
| 6 |
> * |
| 7 |
> * >=dev-libs/icu-49:0/50= pulled in by: |
| 8 |
> * (x11-libs/qt-core-4.8.4-r1::gentoo, installed) |
| 9 |
> |
| 10 |
> I can't parse that. What kind of SLOT is "0/50=" ? |
| 11 |
> |
| 12 |
> So far this has happened twice. The packages that failed prior are not |
| 13 |
> important, |
| 14 |
> what is important is that when the depgraph is *recalculated*, I get |
| 15 |
> that error. |
| 16 |
> It's always that specific atom for icu causing issues and it's always |
| 17 |
> pulled in |
| 18 |
> by qt-<something> |
| 19 |
> |
| 20 |
> Anyone know what that atom means and if it's a bug or not? |
| 21 |
> |
| 22 |
> This system is ~amd64 and portage is latest masked 2.2.0_alpha161. |
| 23 |
> Active python is 2.7 |
| 24 |
> |
| 25 |
|
| 26 |
|
| 27 |
LOL I'll give this a go, sort of. I get this for icu: |
| 28 |
|
| 29 |
root@fireball / # equery l -p icu |
| 30 |
* Searching for icu ... |
| 31 |
[IP-] [ ] dev-libs/icu-49.1.2:0 |
| 32 |
[-P-] [ ~] dev-libs/icu-50.1-r1:0/50.1 |
| 33 |
[-P-] [ ~] dev-libs/icu-50.1-r2:0/50.1 |
| 34 |
[-P-] [ ~] dev-libs/icu-50.1.1:0/50.1.1 |
| 35 |
root@fireball / # |
| 36 |
|
| 37 |
So, does it maybe want icu-50.* instead of the 49 that is installed? |
| 38 |
That would be equal to or greater than what you likely have. I might |
| 39 |
add, the 50 and above are keyworded. |
| 40 |
|
| 41 |
I took a stab at it but not sure what I hit. ;-) |
| 42 |
|
| 43 |
Dale |
| 44 |
|
| 45 |
:-) :-) |
| 46 |
|
| 47 |
-- |
| 48 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives