From: Chris Bare <chris@bareflix.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] gnucash 2.0.4 guile upgrade conflict
Date: Thu, 1 Mar 2007 12:40:23 -0500 (EST) [thread overview]
Message-ID: <20070301174024.0A56A13DFEBE@bareflix.com> (raw)
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
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-03-01 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:40 Chris Bare [this message]
2007-03-01 18:24 ` [gentoo-user] gnucash 2.0.4 guile upgrade conflict Bo Ørsted Andresen
2007-03-01 22:40 ` Novensiles divi Flamen
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=20070301174024.0A56A13DFEBE@bareflix.com \
--to=chris@bareflix.com \
--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