1 |
Hello, |
2 |
|
3 |
On 24/03/2008, Randy Barlow <randy@×××××××××××××××××.com> wrote: |
4 |
|
5 |
[snip] |
6 |
|
7 |
> > Calculating world dependencies \ |
8 |
> > !!! Multiple versions within a single package slot have been |
9 |
> > !!! pulled into the dependency graph: |
10 |
> > |
11 |
> > app-crypt/gnupg:0 |
12 |
> > |
13 |
> > ('installed', '/', 'app-crypt/gnupg-1.4.7-r1', 'nomerge') pulled in by |
14 |
> > ('installed', '/', 'mail-client/squirrelmail-1.4.10a-r2', 'nomerge') |
15 |
> > |
16 |
> > ('ebuild', '/', 'app-crypt/gnupg-2.0.7-r1', 'merge') pulled in by |
17 |
> > ('installed', '/', 'x11-plugins/enigmail-0.95.6-r2', 'nomerge') |
18 |
> > ('installed', '/', 'mail-filter/spamassassin-3.2.1-r1', 'nomerge') |
19 |
> > ('installed', '/', 'mail-client/evolution-2.12.3-r1', 'nomerge') |
20 |
> > |
21 |
|
22 |
[snip] |
23 |
|
24 |
> |
25 |
> I see that squirrelmail has a 'crypt' USE variable that I could disable, |
26 |
> would that solve this problem? Would that have any other consequences |
27 |
> that I should consider? I don't generally sign or encrypt e-mails, so |
28 |
> that wouldn't be a concern for me. Thanks! |
29 |
|
30 |
Yes, it would solve the problem indeed. Toggle off the "crypt" USE |
31 |
flag for squirrelmail via package.use. Alternatively, unmask the |
32 |
latest version of squirrelmail because it no longer acknowledges this |
33 |
flag anyway. Until the author of the relevant plugin updates it so as |
34 |
to be compatible with the newer version of gnupg, this is presumably |
35 |
how things will remain. |
36 |
|
37 |
Regards, |
38 |
|
39 |
--Kerin |
40 |
-- |
41 |
gentoo-server@l.g.o mailing list |