| 1 |
Martin Vaeth wrote: |
| 2 |
> |
| 3 |
> I guess that virtual/jdk prefers the non-binary package, and apparently |
| 4 |
> portage is not able to resolve the conflict automatically by letting the |
| 5 |
> binary package satisfy the dependency. If you manually install openjdk-bin, |
| 6 |
> the problem is probably resolved. |
| 7 |
|
| 8 |
Ahhh... yes, that's the point. It's a very, very old 32-bit system, and |
| 9 |
there is no "x86" (and not even "~x86") openjdk-bin package. |
| 10 |
|
| 11 |
On my other (64-bit) system, openjdk-bin was apparently automatically |
| 12 |
installed, and virtual/jdk-11 was installed without cups, too. |
| 13 |
|
| 14 |
So the 32-bit system falls back auf openjdk (without -bin) which needs |
| 15 |
cups at build time. icedtea-bin does exist for "x86", so cups for build |
| 16 |
time was not necessary. |
| 17 |
|
| 18 |
And jdk-11 seems to need just openjdk (and not icedtea any more). |
| 19 |
|
| 20 |
Well, I can't change the system from 32 to 64 bit just quickly |
| 21 |
(it's my mail server, my web server, even my online shop...). |
| 22 |
|
| 23 |
For the time being, I'll try to enable cups selectively for |
| 24 |
single packages where it's absolutely needed - and in the |
| 25 |
long-term, I guess I'll have to construct a second server |
| 26 |
with 64-bit in parallel where I can switch to later when |
| 27 |
everything is working. |
| 28 |
|
| 29 |
Thanks for your analysis! |
| 30 |
|
| 31 |
-Matt |
Archives