| 1 |
Peter <pete4abw@×××××××.net> writes: |
| 2 |
|
| 3 |
> Well, before that, try and examine each module that is to be emerged and |
| 4 |
> see which ones want luks. Perhaps there is a broken ebuild which is |
| 5 |
> causing the problem. Normally, there are checks that prevent this kind of |
| 6 |
> circular error. |
| 7 |
> |
| 8 |
> Do emerge -puNDvt world and see where luks is showing. There is no need |
| 9 |
> for luks unless you specifically need it. That's what the emerge command |
| 10 |
> will show. |
| 11 |
|
| 12 |
[nomerge ] sys-apps/pmount-0.9.6 USE="crypt" |
| 13 |
[ebuild N ] sys-fs/cryptsetup-luks-1.0.1-r2 USE="nls -dynamic" 0 kB |
| 14 |
|
| 15 |
Does the `noemerge' just mean its not installing in this output or |
| 16 |
that it won't be installed unless cryptsetup-luks is ...? |
| 17 |
|
| 18 |
kde-base/kdebase-kioslaves-3.5.1 depends on pmount so I guess |
| 19 |
I'll keep it. |
| 20 |
|
| 21 |
But this doesn't really answer why I didn't get better output on the |
| 22 |
test emerge -vuDp world... does it? |
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives