| 1 |
Daniel Iliev wrote: |
| 2 |
> On Mon, 22 Sep 2008 08:48:57 +0100 |
| 3 |
> Mick <michaelkintzios@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> Initially portage informed me about: |
| 6 |
>> |
| 7 |
>> [blocks B] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2) |
| 8 |
>> |
| 9 |
>> So, I unmerged <app-crypt/qca-1.0-r3 and emerged |
| 10 |
>> app-crypt/qca-2.0.0-r2. Now it seems kopete won't compile without |
| 11 |
>> app-crypt/qca-1.0-r2: =============================================== |
| 12 |
>> # emerge -upDv kopete |
| 13 |
>> |
| 14 |
>> These are the packages that would be merged, in order: |
| 15 |
>> |
| 16 |
>> Calculating dependencies... done! |
| 17 |
>> [ebuild NS ] app-crypt/qca-1.0-r2 0 kB |
| 18 |
>> [ebuild N ] kde-base/kopete-3.5.9 USE="addbookmarks alias |
| 19 |
>> autoreplace connectionstatus contactnotes crypt gadu highlight |
| 20 |
>> history irc jingle nowlistening sametime slp sms ssl statistics |
| 21 |
>> texteffect webpresence winpopup xscreensaver |
| 22 |
>> yahoo -arts -debug -groupwise -kdeenablefinal -kdehiddenvisibility |
| 23 |
>> -latex -netmeeting -translator -xinerama" 0 kB |
| 24 |
>> [blocks B ] <app-crypt/qca-1.0-r3 (is blocking |
| 25 |
>> app-crypt/qca-2.0.0-r2) |
| 26 |
>> |
| 27 |
>> Total: 2 packages (1 new, 1 in new slot, 1 block), Size of downloads: |
| 28 |
>> 0 kB =============================================== |
| 29 |
>> |
| 30 |
>> What is the elegant way out of this? |
| 31 |
> |
| 32 |
> |
| 33 |
> The ssl support in Kopete depends on qca-tls-1*, which pulls qca-1*. |
| 34 |
> So, if you don't need ssl support in Kopete, then you could disable it |
| 35 |
> by: |
| 36 |
> |
| 37 |
> echo 'kde-base/kopete -ssl' >> /etc/portage/package.use |
| 38 |
|
| 39 |
That's wrong. The right answer is in the "Please, let me understand" |
| 40 |
thread. That is, update to app-crypt/qca-1.0-r3, which is slotted |
| 41 |
(app-crypt/qca-1.0-r2 is not.) |
Archives