What has happened so far: Versions before gpgme-0.3.14 has been occupying the normal /usr/lib/libgpgme.so name space. Sometime back the API changed and the need for slots was created. Subsequent versions were moved to a different namespace introducing difficulties for newer application. There are currently FOUR slots of gpgme and I would like to bring the tree back to two slots of gpgme. For this to happen lots of ebuilds need stabilising. What I did with a lot of help from the peoples of bug 57193, I introduced gpgme-0.3.14-r1 to use a namespace /usr/lib/libgpgme3 and to make 0.9.0-r1 use the normal namespace since it is almost a stable version. As a result of this a lot of programs needed revision bumps to make them work with the correct libraries. ARCH TESTERS can you please make stable the following versions. Please ensure that BEFORE you test you ONLY have the 2 gpgme versions (gpgme-0.3.14-r1 and 0.9.0-r1) installed. The following should just require a compile test should be enough because all that has changed from the previous version is the installed header and library locations. package - herd (maintainer) - current keywords app-crypt/gpgme/gpgme-0.3.14-r1 - crypto (dragonheart) - ~x86 ~ppc ~sparc ~alpha ~hppa ~amd64 ~ia64 app-crypt/cryptplug/cryptplug-0.3.16-r1 - crypto - ~x86 ~ppc ~sparc ~alpha ~hppa ~amd64 ~ia64 app-crypt/seahorse/seahorse-0.6.3-r1 - gnome - ~x86 ~ppc ~sparc ~amd64 dev-tcltk/tclgpgme/tclgpgme-1.0-r1 - bugwranglers - ~x86 ~alpha ~sparc ~ppc kde-base/kdepim/kdepim-3.3.0-r1 - kde - ~x86 ~amd64 ~ppc64 ~sparc ~ppc net-im/licq/licq-1.3.0_pre-r5 - net-im - ~x86 ~ppc ~sparc ~alpha ~ia64 ~amd64 mail-client/sylpheed/sylpheed-0.9.12-r3 - net-mail - (hattya) - ~x86 ~ppc ~sparc ~alpha ~hppa ~ia64 ~amd64 mail-client/sylpheed-claws/sylpheed-claws-0.9.12a - net-mail (genone) - ~x86 ~ppc ~sparc ~alpha ~amd64 The following have a src_test to support checking: app-crypt/gpgme/gpgme-0.9.0-r1 - crypto (dragonheart) - ~x86 ~ppc ~sparc ~alpha ~hppa ~amd64 ~ia64 ppc64 dev-python/pyme/pyme-0.5.1 - python - ~x86 dev-python/pyme/pyme-0.6.0 - python - ~x86 mail-filter/anubis/anubis-3.9.95.ebuild - net-mail (ticho) - ~x86 ~ppc The following don't have a source test: app-crypt/gpa/gpa-0.7.0-r2 - crypto - ~x86 ~ppc ~sparc ~amd64 Please keep the following as unstable because of not fully tested gtk2 support. Additional keywords welcome though. mail-client/sylpheed/sylpheed-0.9.12-r4 - net-mail - (hattya) - ~x86 ~ppc ~sparc ~alpha ~hppa ~ia64 ~amd64 mail-client/sylpheed-claws/sylpheed-claws-0.9.12a-r1 - net-mail (genone) - ~x86 ~ppc ~sparc ~alpha ~amd64 Please this all in one hit so there isn't conflicting incompatible version dependancies between the 4 gpgme SLOTS. Thankyou Daniel Black
x86 marked - gpgme-0.3.14 gpgme-0.9.0-r1 cryptplug-0.3.16-r1 tclgpgme-1.0-r1 running gpa after emerge SEGFAULTED. still investigating.
I'm getting a segfault *during* the emerge, and this came up during an 'emerge -Uua world': if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../gpgme -O2 -mcpu=i686 -pipe -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -MT t-genkey.o -MD -MP -MF ".deps/t-genkey.Tpo" \ -c -o t-genkey.o `test -f 't-genkey.c' || echo './'`t-genkey.c; \ then mv -f ".deps/t-genkey.Tpo" ".deps/t-genkey.Po"; \ else rm -f ".deps/t-genkey.Tpo"; exit 1; \ fi /usr/bin/gpgsm --homedir . --import ./cert_g10code_test1.der echo disable-crl-checks > ./gpgsm.conf echo faked-system-time 1008241200 >> ./gpgsm.conf test -d ./private-keys-v1.d || mkdir ./private-keys-v1.d cp ./32100C27173EF6E9C4E9A25D3D69F86D37A4F939 private-keys-v1.d/32100C27173EF6E9C4E9A25D3D69F86D37A4F939.key echo 32100C27173EF6E9C4E9A25D3D69F86D37A4F939 > ./trustlist.txt echo >> ./trustlist.txt echo "# CN=test cert 1,OU=Aegypten Project,O=g10 Code GmbH,L=Düsseldorf,C=DE" >> ./trustlist.txt echo "3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E S" >> ./trustlist.txt /bin/sh ../../libtool --mode=link gcc -O2 -mcpu=i686 -pipe -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -o t-import t-import.o ../../gpgme/libgpgme.la gpgsm: WARNING: running with faked system time: 2001-12-13 11:00:00 gpgsm: keybox `./pubring.kbx' created gpgsm: some signal caught ... exiting make[3]: *** [pubring.kbx] Segmentation fault make[3]: *** Deleting file `pubring.kbx' make[3]: *** Waiting for unfinished jobs.... mkdir .libs gcc -O2 -mcpu=i686 -pipe -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -o .libs/t-import t-import.o ../../gpgme/.libs/libgpgme.so creating t-import make[3]: Leaving directory `/var/tmp/portage/gpgme-0.9.0-r1/work/gpgme-0.9.0/tests/gpgsm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gpgme-0.9.0-r1/work/gpgme-0.9.0/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gpgme-0.9.0-r1/work/gpgme-0.9.0' make: *** [all] Error 2 !!! ERROR: app-crypt/gpgme-0.9.0-r1 failed. !!! Function src_compile, Line 47, Exitcode 2 !!! (no error message)
I'm getting a segfault *during* the emerge, and this came up during an 'emerge -Uua world': if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../gpgme -O2 -mcpu=i686 -pipe -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -MT t-genkey.o -MD -MP -MF ".deps/t-genkey.Tpo" \ -c -o t-genkey.o `test -f 't-genkey.c' || echo './'`t-genkey.c; \ then mv -f ".deps/t-genkey.Tpo" ".deps/t-genkey.Po"; \ else rm -f ".deps/t-genkey.Tpo"; exit 1; \ fi /usr/bin/gpgsm --homedir . --import ./cert_g10code_test1.der echo disable-crl-checks > ./gpgsm.conf echo faked-system-time 1008241200 >> ./gpgsm.conf test -d ./private-keys-v1.d || mkdir ./private-keys-v1.d cp ./32100C27173EF6E9C4E9A25D3D69F86D37A4F939 private-keys-v1.d/32100C27173EF6E9C4E9A25D3D69F86D37A4F939.key echo 32100C27173EF6E9C4E9A25D3D69F86D37A4F939 > ./trustlist.txt echo >> ./trustlist.txt echo "# CN=test cert 1,OU=Aegypten Project,O=g10 Code GmbH,L=Düsseldorf,C=DE" >> ./trustlist.txt echo "3CF405464F66ED4A7DF45BBDD1E4282E33BDB76E S" >> ./trustlist.txt /bin/sh ../../libtool --mode=link gcc -O2 -mcpu=i686 -pipe -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -o t-import t-import.o ../../gpgme/libgpgme.la gpgsm: WARNING: running with faked system time: 2001-12-13 11:00:00 gpgsm: keybox `./pubring.kbx' created gpgsm: some signal caught ... exiting make[3]: *** [pubring.kbx] Segmentation fault make[3]: *** Deleting file `pubring.kbx' make[3]: *** Waiting for unfinished jobs.... mkdir .libs gcc -O2 -mcpu=i686 -pipe -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -o .libs/t-import t-import.o ../../gpgme/.libs/libgpgme.so creating t-import make[3]: Leaving directory `/var/tmp/portage/gpgme-0.9.0-r1/work/gpgme-0.9.0/tests/gpgsm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gpgme-0.9.0-r1/work/gpgme-0.9.0/tests' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gpgme-0.9.0-r1/work/gpgme-0.9.0' make: *** [all] Error 2 !!! ERROR: app-crypt/gpgme-0.9.0-r1 failed. !!! Function src_compile, Line 47, Exitcode 2 !!! (no error message)
Sean, What is your emerge info?
> Sean, What is your emerge info? Nothing really odd, I think. Portage 2.0.50-r11 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8.1) ================================================================= System uname: 2.6.8.1 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://128.213.5.34/gentoo/ http://mirror.datapipe.net/gentoo ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/" MAKEOPTS="" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb bidi bitmap-fonts cdr crypt cups curl dac dga directfb dvd dvdr encode esd fam fbcon flac flash foomaticdb gd gdbm gif gpm gtk gtk2 imagemagick imap imlib ipv6 jabber java jpeg junit kde lcms ldap libg++ libwww lirc mad mikmod mmx motif mpeg mpi nas ncurses nls oggvorbis opengl oss pam pcmcia pda pdflib perl png pnp ppds python qt quicktime readline ruby sasl scanner sdl slang slp speex spell sqlite sse ssl svga tcltk tcpd tiff truetype trusted unicode usb video_cards_radeon videos wmf wxwindows x86 xml xml2 xmms xosd xprint xv zlib"
Sean - what you have seems to be same fault as #54758. Can we continue discussion there. What version of gnupg, libgcrypt, libgpg-error, newpg (anything else) do you have? Also consider changing you /etc/make.profile link to a 2004.2 profile. If you have a bit of time can you rummage around gpgme mailing lists for a similar error. I don't it's gentoo specific but having said that it works for me hence this bug.
sparc stabled: app-crypt/cryptplug-0.3.16-r1 app-crypt/gpgme-0.3.14-r1 app-crypt/gpgme-0.9.0-r1 app-crypt/seahorse-0.6.3-r1 dev-tcltk/tclgpgme-1.0-r1 more to follow later...
everything requested now masked stable on ppc
kde-base/kdepim-3.3.0-r1 and mail-client/sylpheed-0.9.12-r3 stable on sparc.
ia64 and amd64 - final 3 to stable if you'd be so kind mail-client/sylpheed/sylpheed-0.9.12-r3.ebuild:KEYWORDS="...~ia64 ~amd64" app-crypt/gpgme/gpgme-0.3.14-r1.ebuild:KEYWORDS="....~ia64" app-crypt/gpgme/gpgme-0.9.0-r1.ebuild:KEYWORDS="....~ia64" Thank you people.
All done on hppa since some days :)
ia64 is done (thanks hattya)
stable on ppc64, app-crypt/cryptplug-0.3.16-r1 app-crypt/gpgme-0.3.14-r1 app-crypt/gpgme-0.9.0-r1 app-crypt/seahorse-0.6.3-r1 dev-tcltk/tclgpgme-1.0-r1 ~ppc64 kde-base/kdepim-3.3.0-r1 mail-client/sylpheed-0.9.12-r6 I'm a little unclear if there are other packages that need stablization.
Removing sparc@ since AFAIK we're done.
Can the following few packages please be stabilised: mail-filter/anubis/anubis-3.9.95.ebuild x86 >=mail-client/sylpheed/sylpheed-0.9.12-r3 ppc64 mail-client/balsa/balsa-2.0.15-r2.ebuild x86 sparc >=kde-base/kdepim/kdepim-3.3.0-r1.ebuild x86 amd64 ppc64 app-crypt/cryptplug/cryptplug-0.3.16-r1.ebuild ia64 Ok, with the exception of the few ebuilds above, all ebuilds have more recent versions with equal or more stable keywords. I would like the following ebuilds removed from the tree because of occasional version conficts in gpgme. mail-filter/anubis/anubis-3.6.2.ebuild mail-filter/anubis/anubis-3.6.2-r1.ebuild mail-client/sylpheed-claws/sylpheed-claws-0.9.11.ebuild mail-client/sylpheed/sylpheed-0.9.11.ebuild mail-client/elmo/elmo-1.3.2.ebuild mail-client/elmo/elmo-1.3.1-r1.ebuild mail-client/balsa/balsa-2.0.14.ebuild mail-client/balsa/balsa-2.0.15-r1.ebuild kde-base/kdepim/kdepim-3.3.0.ebuild app-crypt/seahorse/seahorse-0.6.3.ebuild app-crypt/gpgme/gpgme-0.4.7.ebuild app-crypt/gpgme/gpgme-0.4.0.ebuild app-crypt/gpgme/gpgme-0.3.16.ebuild app-crypt/gpgme/gpgme-0.3.14.ebuild Thankyou fellow devs.
*** Bug 70245 has been marked as a duplicate of this bug. ***
The affected elmo ebuilds have been removed from the tree.
balsa-2.0.15-r2 sparc tasty.
Transfered removal and keywords items in comment 14 have been place in the following individual bugs 72615, 72616, 72618, 72619, 72620 and bug 72621
