Hi all, to-day I upgraded my portage and then I ran
emerge -NDpvu here is the output:

[ebuild U ] dev-libs/libsigc++-2.2.2 [2.0.17] USE="-debug -doc
-test" 4,397 kB
[ebuild U ] media-video/realplayer-11.0.0.4028-r1 [10.0.9] USE="X
-nsplugin" 0 kB

[ebuild U ] dev-cpp/cairomm-1.6.0 [1.2.4] USE="-doc (-examples%)" 779 kB
[ebuild U ] dev-perl/extutils-depends-0.300 [0.205] 10 kB
[ebuild U ] dev-perl/Cairo-1.06.0 [1.04.0] USE="-test%" 88 kB
[ebuild U ] dev-cpp/glibmm-2.16.4 [2.12.8] USE="-debug -doc
-examples" 6,227 kB

[ebuild U ] dev-perl/glib-perl-1.182 [1.143] USE="(-xml%)" 242 kB
[ebuild U ] dev-cpp/gtkmm-2.12.7 [2.10.9] USE="-accessibility -debug
-doc -examples -test%" 14,843 kB

[ebuild NS ] app-crypt/qca-2.0.0-r2 USE="-debug -doc -examples" 0 kB
[ebuild U ] dev-perl/gtk2-perl-1.145 [1.142-r1] 641 kB
[blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2)

So it seems qca-1.0-r3 is blocking qca-2.0.0-r2! But I have no
qca-1.0-r3 installed! :-(

What's happening?
Regards
emilio

unemerge old version
emerge -Cva qca

and merge new
emerge -va qca


econti napsal(a):

Hi all, to-day I upgraded my portage and then I ran
emerge -NDpvu here is the output:

[ebuild U ] dev-libs/libsigc++-2.2.2 [2.0.17] USE="-debug -doc
-test" 4,397 kB
[ebuild U ] media-video/realplayer-11.0.0.4028-r1 [10.0.9] USE="X
-nsplugin" 0 kB
[ebuild U ] dev-cpp/cairomm-1.6.0 [1.2.4] USE="-doc (-examples%)"
779 kB

[ebuild U ] dev-perl/extutils-depends-0.300 [0.205] 10 kB
[ebuild U ] dev-perl/Cairo-1.06.0 [1.04.0] USE="-test%" 88 kB
[ebuild U ] dev-cpp/glibmm-2.16.4 [2.12.8] USE="-debug -doc
-examples" 6,227 kB

[ebuild U ] dev-perl/glib-perl-1.182 [1.143] USE="(-xml%)" 242 kB
[ebuild U ] dev-cpp/gtkmm-2.12.7 [2.10.9] USE="-accessibility -debug
-doc -examples -test%" 14,843 kB

[ebuild NS ] app-crypt/qca-2.0.0-r2 USE="-debug -doc -examples" 0 kB
[ebuild U ] dev-perl/gtk2-perl-1.145 [1.142-r1] 641 kB
[blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2)

So it seems qca-1.0-r3 is blocking qca-2.0.0-r2! But I have no
qca-1.0-r3 installed! :-(

What's happening?
Regards
emilio

On Tuesday 23 September 2008 12:57:24 econti wrote:
> Hi all, to-day I upgraded my portage and then I ran
> emerge -NDpvu here is the output:
>
> [ebuild U ] dev-libs/libsigc++-2.2.2 [2.0.17] USE="-debug -doc
> -test" 4,397 kB
> [ebuild U ] media-video/realplayer-11.0.0.4028-r1 [10.0.9] USE="X
> -nsplugin" 0 kB
> [ebuild U ] dev-cpp/cairomm-1.6.0 [1.2.4] USE="-doc (-examples%)" 779
> kB [ebuild U ] dev-perl/extutils-depends-0.300 [0.205] 10 kB
> [ebuild U ] dev-perl/Cairo-1.06.0 [1.04.0] USE="-test%" 88 kB
> [ebuild U ] dev-cpp/glibmm-2.16.4 [2.12.8] USE="-debug -doc
> -examples" 6,227 kB
> [ebuild U ] dev-perl/glib-perl-1.182 [1.143] USE="(-xml%)" 242 kB
> [ebuild U ] dev-cpp/gtkmm-2.12.7 [2.10.9] USE="-accessibility -debug
> -doc -examples -test%" 14,843 kB
> [ebuild NS ] app-crypt/qca-2.0.0-r2 USE="-debug -doc -examples" 0 kB
> [ebuild U ] dev-perl/gtk2-perl-1.145 [1.142-r1] 641 kB
> [blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2)
>
> So it seems qca-1.0-r3 is blocking qca-2.0.0-r2! But I have no
> qca-1.0-r3 installed! :-(
> What's happening?
> Regards
> emilio

It's quite simple really. You didn't see a '<' character. It's here:

<app-crypt/qca-1.0-r3

The thing that is blocking qca-2 MUST BE a version less than 1.0-r3

There is only one sane way to resolve blockers. Run emerge with -t to find out
why stuff is being pulled in. Then find out what you already have, I use eix
for this.

Finally solve the problem with a great big fat hefty dose of "look and think"

--
alan dot mckinnon at gmail dot com

Tomáš Krasni�an wrote:

unemerge old version
emerge -Cva qca

and merge new
emerge -va qca




And if it still gives you a error, add this to your package.keyword and
package.unmask file:


=app-crypt/qca-1.0-r3

That last part was what fixed it for me.

Dale

:-) :-)

econti wrote:

Hi all, to-day I upgraded my portage and then I ran
emerge -NDpvu here is the output:

[ebuild U ] dev-libs/libsigc++-2.2.2 [2.0.17] USE="-debug -doc
-test" 4,397 kB
[ebuild U ] media-video/realplayer-11.0.0.4028-r1 [10.0.9] USE="X
-nsplugin" 0 kB
[ebuild U ] dev-cpp/cairomm-1.6.0 [1.2.4] USE="-doc (-examples%)"
779 kB

[ebuild U ] dev-perl/extutils-depends-0.300 [0.205] 10 kB
[ebuild U ] dev-perl/Cairo-1.06.0 [1.04.0] USE="-test%" 88 kB
[ebuild U ] dev-cpp/glibmm-2.16.4 [2.12.8] USE="-debug -doc
-examples" 6,227 kB

[ebuild U ] dev-perl/glib-perl-1.182 [1.143] USE="(-xml%)" 242 kB
[ebuild U ] dev-cpp/gtkmm-2.12.7 [2.10.9] USE="-accessibility -debug
-doc -examples -test%" 14,843 kB

[ebuild NS ] app-crypt/qca-2.0.0-r2 USE="-debug -doc -examples" 0 kB
[ebuild U ] dev-perl/gtk2-perl-1.145 [1.142-r1] 641 kB
[blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2)

So it seems qca-1.0-r3 is blocking qca-2.0.0-r2! But I have no
qca-1.0-r3 installed! :-(

What's happening?
Regards
emilio


The others already gave you a working solution, but here's the reason
this is happening:


The qca package recently became slotted. However, only qca-1.0-r3 and
higher are slotted. You have qca-1.0-r2 installed with is *not* slotted
and therefore you can't install qca-2.x at the same time. Problem is,
qca-1.0-r3 is keyworded so you need to place this:


=app-crypt/qca-1.0-r3

in your /etc/portage/package.keywords and then proceed as the others
said. Unmerge the current version:


emerge -aC =app-crypt/qca-1.0-r2

and only then do your world update.

cut


The others already gave you a working solution, but here's the reason
this is happening:


The qca package recently became slotted. However, only qca-1.0-r3 and
higher are slotted. You have qca-1.0-r2 installed with is *not*
slotted and therefore you can't install qca-2.x at the same time.
Problem is, qca-1.0-r3 is keyworded so you need to place this:


=app-crypt/qca-1.0-r3

in your /etc/portage/package.keywords and then proceed as the others
said. Unmerge the current version:


emerge -aC =app-crypt/qca-1.0-r2

and only then do your world update.
I followed the tip but now the output of emerge -NDpvu contains, among
the others, this line:


[ebuild NS ] app-crypt/qca-1.0-r3 0 kB

Regards
emilio

Am Mittwoch 24 September 2008 10:07:27 schrieb ext econti:

> I followed the tip but now the output of emerge -NDpvu contains, among
> the others, this line:
>
> [ebuild *NS * ] app-crypt/qca-1.0-r3 *0 kB

As it should.

Bye...

Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net

On Tuesday 23 September 2008, Nikos Chantziaras wrote:
> econti wrote:
> > Hi all, to-day I upgraded my portage and then I ran
> > emerge -NDpvu here is the output:
> >
> > [ebuild U ] dev-libs/libsigc++-2.2.2 [2.0.17] USE="-debug -doc
> > -test" 4,397 kB
> > [ebuild U ] media-video/realplayer-11.0.0.4028-r1 [10.0.9] USE="X
> > -nsplugin" 0 kB
> > [ebuild U ] dev-cpp/cairomm-1.6.0 [1.2.4] USE="-doc (-examples%)"
> > 779 kB
> > [ebuild U ] dev-perl/extutils-depends-0.300 [0.205] 10 kB
> > [ebuild U ] dev-perl/Cairo-1.06.0 [1.04.0] USE="-test%" 88 kB
> > [ebuild U ] dev-cpp/glibmm-2.16.4 [2.12.8] USE="-debug -doc
> > -examples" 6,227 kB
> > [ebuild U ] dev-perl/glib-perl-1.182 [1.143] USE="(-xml%)" 242 kB
> > [ebuild U ] dev-cpp/gtkmm-2.12.7 [2.10.9] USE="-accessibility -debug
> > -doc -examples -test%" 14,843 kB
> > [ebuild NS ] app-crypt/qca-2.0.0-r2 USE="-debug -doc -examples" 0 kB
> > [ebuild U ] dev-perl/gtk2-perl-1.145 [1.142-r1] 641 kB
> > [blocks B ] <app-crypt/qca-1.0-r3 (is blocking
> > app-crypt/qca-2.0.0-r2)
> >
> > So it seems qca-1.0-r3 is blocking qca-2.0.0-r2! But I have no
> > qca-1.0-r3 installed! :-(
> > What's happening?
> > Regards
> > emilio
>
> The others already gave you a working solution, but here's the reason
> this is happening:
>
> The qca package recently became slotted. However, only qca-1.0-r3 and
> higher are slotted. You have qca-1.0-r2 installed with is *not* slotted
> and therefore you can't install qca-2.x at the same time. Problem is,
> qca-1.0-r3 is keyworded so you need to place this:
>
> =app-crypt/qca-1.0-r3
>
> in your /etc/portage/package.keywords and then proceed as the others
> said. Unmerge the current version:
>
> emerge -aC =app-crypt/qca-1.0-r2
>
> and only then do your world update.

Sure. But,...

...since I run stable I would expect that the new slot app-crypt/qca-2.0.0-r2
would remain keyworded until app-crypt/qca-1.0-r3 became stable. Then emerge
would emerge both at the same time, hopefully in the right order. No blocks
and no problem?
--
Regards,
Mick