public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Novensiles divi Flamen <noven@sincorp.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gnucash 2.0.4 guile upgrade conflict
Date: Fri, 2 Mar 2007 09:10:05 +1030	[thread overview]
Message-ID: <200703020910.05203.noven@sincorp.org> (raw)
In-Reply-To: <20070301174024.0A56A13DFEBE@bareflix.com>

On Fri, 2 Mar 2007 04:10:23 Chris Bare wrote:
> I have gnucash 2.0.4 installed, and when trying to do my normal emerge
> sync; emerge -uD world, I get a conflict with guile
>
> ('ebuild', '/', 'dev-scheme/guile-1.6.7', 'merge') pulled in by
>   ('ebuild', '/', 'dev-scheme/slib-3.1.1', 'merge')
>
> ('ebuild', '/', 'dev-scheme/guile-1.8.1-r1', 'nomerge') (no parents)
>
> apparently gnucash requires guile 1.8.1 while slib requires guile 1.6.7.
> unfortunately, gnucash also requires slib, so I seem to be stuck.
>
> Has anyone figure out a work-around for this, or do I just need to wait for
> the devels to resolve it? I realize gnucash 2.0.4 and 2.0.5 are ~x86 so
> this is one of the risks I take, but they have some important bug fixes. --
> Chris Bare
> chris@bareflix.com

I run a fully ~x86 system, I had to limit guile and slib to the stable version 
by adding
dev-scheme/slib -~x86
dev-scheme/guile -~x86
to /etc/portage/package.keywords. This works for gnucash 2.04

- Noven
-- 
>-- Novensiles divi Flamen --<
>---- Miles Militis Fons ----<
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-03-01 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 17:40 [gentoo-user] gnucash 2.0.4 guile upgrade conflict Chris Bare
2007-03-01 18:24 ` Bo Ørsted Andresen
2007-03-01 22:40 ` Novensiles divi Flamen [this message]
2007-03-02 10:09   ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200703020910.05203.noven@sincorp.org \
    --to=noven@sincorp.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox