gnupg-1.4.6 is blocking gnupg-2.0.1-r1

Message

Haystack · Post by **Haystack** » Sun Dec 31, 2006 4:13 pm

How is this possible?

#emerge -uavtDN world
These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[blocks B     ] <=app-crypt/gnupg-2.0.1 (is blocking app-crypt/gnupg-2.0.1-r1)
[ebuild     U ] app-arch/gzip-1.3.10 [1.3.9] USE="nls -pic -static" 417 kB
[ebuild   R   ] sys-apps/busybox-1.3.1  USE="-debug -make-symlinks -savedconfig -static (-netboot%)" 0 kB
[ebuild     U ] x11-drivers/xf86-video-fbdev-0.3.1 [0.3.0] USE="-debug" 213 kB
[ebuild     U ]  x11-misc/util-macros-1.1.5 [1.1.4] USE="-debug" 47 kB
[nomerge      ] kde-base/kopete-3.5.5-r2  USE="crypt ssl -addbookmarks -alias -arts -autoreplace -connectionstatus -contactnotes -debug -gadu -groupwise -highlight -history -irc -jingle -kdeenablefinal -kdehiddenvisibility -latex -netmeeting -nowlistening -sametime -slp -sms -statistics -texteffect -translator -webpresence -winpopup -xinerama -xscreensaver -yahoo"
[ebuild     U ]  app-crypt/gnupg-2.0.1-r1 [1.4.6] USE="X nls -bzip2 -caps% -doc% -ldap -openct% -pcsc-lite% (-selinux) -smartcard (-bindist%) (-curl%) (-ecc%) (-idea%) (-readline%*) (-static%) (-usb%*) (-zlib%*)" LINGUAS="(-ru%)" 3,832 kB
[nomerge      ] net-dns/libidn-0.6.5-r1  USE="java mono nls -doc -emacs"
[nomerge      ]  dev-lang/mono-1.2.2.1  USE="X -nptl"
[nomerge      ]   dev-dotnet/libgdiplus-1.2.2  USE="gif jpeg tiff -exif"
[ebuild     U ]    media-libs/libpng-1.2.14-r1 [1.2.14] USE="-doc" 0 kB
[nomerge      ] sys-libs/db-4.3.29-r2  USE="java -bootstrap -doc -nocxx -tcl -test"
[nomerge      ]  sys-apps/portage-2.1.2_rc4-r3  USE="-build -doc -epydoc -selinux" LINGUAS="-pl"
[ebuild     U ]   app-shells/bash-3.2_p9-r1 [3.2_p9] USE="nls -afs -bashlogger -vanilla" 0 kB

Total: 7 packages (6 upgrades, 1 reinstall, 1 block), Size of downloads: 4,508 kB

!!! Error: The above package list contains packages which cannot be installed
!!!        at the same time on the same system.

For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

Code: Select all

# equery depends gnupg
[ Searching for packages depending on gnupg... ]
app-crypt/gnupg-1.9.94 (=app-crypt/gnupg-1.4*)
                       (=app-crypt/gnupg-1.4*)
                       (=app-crypt/gnupg-1.4*)
                       (=app-crypt/gnupg-1.4*)
                       (=app-crypt/gnupg-1.4*)
                       (=app-crypt/gnupg-1.4*)
app-crypt/gpgme-1.1.2-r1 (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
                         (>=app-crypt/gnupg-1.9.20-r1)
kde-base/kopete-3.5.5-r2 (crypt? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
                         (crypt ? app-crypt/gnupg)
tux joris # emerge --unmerge -p gnupg

>>> These are the packages that would be unmerged:

 app-crypt/gnupg
    selected: 1.4.6 1.9.94
   protected: none
     omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

Why can an old package block its update?

tontudelbot · Post by **tontudelbot** » Sun Dec 31, 2006 5:22 pm

Because versions 1.9 requires 1.4 as a runtime dependency. I think you sould unmerge 1.4 and then i'll get the new 2.0... i think...

Haystack · Post by **Haystack** » Sun Dec 31, 2006 5:27 pm

Unmerging the old version indeed solves the blockage.

I just don't get why 1.9 depends on 1.4. Is that normal??? I think it's very weird.

tontudelbot · Post by **tontudelbot** » Sun Dec 31, 2006 5:29 pm

AFAIK, 1.9 is a development version and 1.4 get runtime libraries wich 1.9 doesn't...

lenk · Post by **lenk** » Mon Jan 01, 2007 11:45 pm

Are you sure unmerging gnupg 1.4 is such a good idea? Is there a better solution to this?

sonicbhoc · Post by **sonicbhoc** » Mon Jan 01, 2007 11:58 pm

well, the new version provides the same functionality, right? If it's blocking the new version it has to be for a reason. I say go ahead and toast the old one and install the new one. I did and so far nothing seems to be broken. But, as always, revdep-rebuild is your friend.

mathfeel · Post by **mathfeel** » Tue Jan 02, 2007 2:56 am

sonicbhoc wrote:well, the new version provides the same functionality, right? If it's blocking the new version it has to be for a reason. I say go ahead and toast the old one and install the new one. I did and so far nothing seems to be broken. But, as always, revdep-rebuild is your friend.

For now, tho, seahorse depends on gnupg-1.4*:

Code: Select all

$ sudo emerge -avuDN world

These are the packages that would be merged, in order:

Calculating world dependencies -
!!! Multiple versions within a single package slot have been
!!! pulled into the dependency graph:

('ebuild', '/', 'app-crypt/gnupg-1.4.6', 'merge') pulled in by
   ('ebuild', '/', 'app-crypt/seahorse-0.8.2', 'nomerge')

('ebuild', '/', 'app-crypt/gnupg-2.0.1-r1', 'merge') pulled in by
   ('ebuild', '/', 'app-crypt/gpgme-1.1.2-r1', 'nomerge')

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in the
dependencies of two different packages, then those packages can not be
installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man page
or refer to the Gentoo Handbook.

!!! Depgraph creation failed.

sonicbhoc · Post by **sonicbhoc** » Tue Jan 02, 2007 12:54 pm

did you file a bug report? Maybe it should be changed and they didn't get to it yet, or maybe you'll just have to mask all versions above the one you're using now.

Row · Post by **Row** » Tue Jan 02, 2007 5:02 pm

I had problems with gnupg too due to KDE.

The best choice was to unmerge gnupg then update world again.

Greets.

b0fh · Post by **b0fh** » Wed Jan 03, 2007 3:26 pm

I'm having this problem, too. I unmerged both versions of gnupg, and now I get this when I try to update world:

Code: Select all

Calculating world dependencies /
!!! Multiple versions within a single package slot have been
!!! pulled into the dependency graph:

('ebuild', '/', 'app-crypt/gnupg-1.4.6', 'merge') pulled in by
   ('installed', '/', 'kde-base/kdepim-3.5.5-r1', 'nomerge')

('ebuild', '/', 'app-crypt/gnupg-2.0.1-r2', 'merge') pulled in by
   ('ebuild', '/', 'net-im/psi-0.10-r2', 'nomerge')
   ('ebuild', '/', 'www-client/seamonkey-1.0.7', 'nomerge')
   ('ebuild', '/', 'app-crypt/gpgme-1.1.2-r1', 'nomerge')

Any ideas?

Row · Post by **Row** » Wed Jan 03, 2007 9:18 pm

My only idea right now is to force installation of last version of gnupg by doing emerge --nodeps gnupg.

Is not a good choice but I've used it sometimes to arrange dependency tree problems.

Gentree · Post by **Gentree** » Thu Jan 04, 2007 1:00 am

Code: Select all

emerge -p -uD world
!!! Multiple versions within a single package slot have been
!!! pulled into the dependency graph:

     app-crypt/gnupg-1.4.6
     app-crypt/gnupg-2.0.1-r2

emerge -C gnupg
emerge !$

[ebuild     U ] dev-libs/libassuan-1.0.1 [1.0.0]
[ebuild  N    ] app-crypt/gnupg-2.0.1-r2  USE="X bzip2 nls -doc -ldap -openct -$

....
>>> app-crypt/gnupg-2.0.1-r2 merged.
>>> Recording app-crypt/gnupg in "world" favorites file...

look OK here.

thedarkspirit · Post by **thedarkspirit** » Wed Apr 11, 2007 3:50 pm

Well... Still the same problems emerging Seahorse @"~x86".

Seahorse wants gnupg 1.4.7-r1 and gpgme the latest version, and I cannot have different ones at the same time. I tried some masking stuff, but could not solve that problem.

Well, according to the Project Website it should be possible to use gnupg 2.x. So I got the latest sources from there, tried compiling it but... it complained:

checking for gpg... /usr/bin/gpg
checking for appropriate GnuPG version... configure: error: Appropriate version of GnuPG not found. Please install one of versions: 1.2 1.4

Hate that.

Anyone who found a clean solution to avoid the double-version-problem?

teknux · Post by **teknux** » Thu Apr 12, 2007 11:47 am

1 - unmerge all gnupg and gpgme stuff
2 - emerge =app-crypt/gnupg-1.9.94
3 - emerge seahorse

it worked for me (i know this isn't the best solution...)

cheers,
tek

Blaubaer · Post by **Blaubaer** » Fri Apr 13, 2007 5:21 pm

thedarkspirit wrote: Well, according to the Project Website it should be possible to use gnupg 2.x.

seahorse 1.0.1 compiles and runs fine with 2.x, but there ist a but in the configure-script so it doesnt check for 2.x.
i tried this:
unpacked the source and added in the file configure 2.0 to the string accepted_versions, then packed it again, did "ebuild /usr/portage/app-crypt/seahorse/seahorse-1.0.1.ebuild digest", then a "emerge --nodeps seahorse". this built seahorse against gnupg 2.x.
the problem i have now is that portage still wants to flipflop between app-crypt/gnupg-1.4.7-r1 and app-crypt/gnupg-2.0.3-r1.
i tried putting app-crypt/gnupg-1.4.7-r1 into packages.provides, but that doesnt help.

sfragis · Post by **sfragis** » Fri Apr 27, 2007 2:24 pm

Blaubaer wrote: the problem i have now is that portage still wants to flipflop between app-crypt/gnupg-1.4.7-r1 and app-crypt/gnupg-2.0.3-r1.
i tried putting app-crypt/gnupg-1.4.7-r1 into packages.provides, but that doesnt help.

Edit the ebuild /usr/portage/app-crypt/seahorse/seahorse-1.0.1.ebuild, change line 27 from

Code: Select all

         =app-crypt/gnupg-1.4*

to

Code: Select all

         >=app-crypt/gnupg-1.4

Then run ebuild as usual. Portage will not bother you anymore.

Does anybody know why gnupg-1.4 is required? I'm running seahorse with gnupg-2.0 installed and no problems at all.
Is it that the configure script is "broken" as observed by Blaubaer?

red-wolf76 · Post by **red-wolf76** » Mon May 14, 2007 10:28 am

Has anybody submitted this solution to bugzilla yet?

EDIT: Bummer, it ain't really a solution. Emerging seahorse fails because of the wrong gnupg version.

gnupg-1.4.6 is blocking gnupg-2.0.1-r1

gnupg-1.4.6 is blocking gnupg-2.0.1-r1

Unmerging is a solution

My only idea