Am Mittwoch, 2. Januar 2008 schrieb Robin H. Johnson:
> On Tue, Jan 01, 2008 at 10:21:35PM +0100, Wolfgang Illmeyer wrote:
> To restate it more clearly from your paragraph above:
> kmail DEPENDS on gpgme built-with gnupg-2
> psiDEPENDS on gpgme built-with gnupg-1
> basket D
, because both basket and kmail use gpgme and I
haven't found out how to use both versions of gpg simultaneously with gpgme.
I guess this problem could already be solved, if somebody actually cared to
slot gpg2.
/Wolfgang
Am Dienstag, 1. Januar 2008 schrieb Wolfgang Illmeyer:
> Hi.
> Wh
Hi.
While I'm writing this, I'm trying to do a "client-side" slotting of gpg2
myself, because when I run gpg 1.x, Psi and Basket work, and when I run 2.x
kmail works, but never all three at the same time.
Please stop your arguments about wether or not to slot or and just let me use
my applicatio
I did spell it right:
# emerge -pv ebook-binutils
Aron Griffis wrote:
Wolfgang Illmeyer wrote:[Thu Jun 30 2005, 12:40:21PM EDT]
Calculating dependencies -
emerge: there are no ebuilds to satisfy "dev-uitl/kdevelop".
Try spelling it right.
--
Aron Griffis
Gentoo Linux
already synced twice today, but the error didn't go away...
Mark Loeser wrote:
Wolfgang Illmeyer wrote:
BTW:
# emerge -pv ebook-binutils
These are the packages that I would merge, in order:
Calculating dependencies -
emerge: there are no ebuilds to satisfy "dev-uit
BTW:
# emerge -pv ebook-binutils
These are the packages that I would merge, in order:
Calculating dependencies -
emerge: there are no ebuilds to satisfy "dev-uitl/kdevelop".
I can't find no dev-uitl/kdevelop... somebody should put that into the
portage tree ;)
Wolfgang
Mike Frysinger wrot
Hi,
I've installed kde-meta 3.4.0 and I just did an emerge -p kde-meta, and
it wants to install 252 ebuilds. If I do an emerge -up kde-meta, it
wants to install 331 ebuilds.
In the discussion about kde split ebuilds, it was promised that the
split ebuilds would enable us to update only the prog
Robin H. Johnson wrote:
>/sbin/fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu
>
>If that doesn't fix it, you get to keep the pieces.
>
>
I did that together with emerge gcc glibc binutils right after changing
the CHOST, everything but python-stuff worked
>Changing the CHOST
Hi,
A few months ago I changed my CHOST in make.conf from i386-pc-linux-gnu
to i686-pc-linux-gnu. Everything went ok until I had to install some
python package; the old chost was hardcoded somewhere in
/usr/lib/python2.3 or similar and therefore it still wanted to use the
i386-toolchain when build
