Re: [gentoo-desktop] Trying to install gnucash - g-wrap failure

[Daniel Gryniewicz]

On Tue, 2007-02-27 at 08:36 -0500, mail wrote:
> On Mon, 2007-02-26 at 18:05 -0600, Boyd Stephen Smith Jr. wrote:
> > On Monday 26 February 2007, mail <lists@×××××.net> wrote about 'Re:
> > [gentoo-desktop] Trying to install gnucash - g-wrap failure':
> > > On Sat, 2007-02-24 at 04:47 -0600, Boyd Stephen Smith Jr. wrote:
> > > > On Friday 23 February 2007 16:43, Boyd Stephen Smith Jr. wrote:
> > > > > On Friday 23 February 2007, mail <lists@×××××.net> wrote about 'Re:
> > > > >
> > > > > [gentoo-desktop] Trying to install gnucash - g-wrap failure':
> > > > > > Thanks,
> > > > > > but none of the masking or keywords work. It seems that
> > > > > > gnucash is dead.
> > > > > > I wonder why it is in portage at all?
> > > >
> > > > Nope. app-office/gnucash is not dead:
> > > >
> > > > I had to install the following packages to get gnucash working:
> > >
> > > glib is 2.5 installed so I don't know why gnucash needs a broken 1.2?
> >
> > Because those two versions are anywhere near source or binary compatible.
> > Glib changed significantly between 1.x and 2.x, so that programs written
> > against 1.x have to be non-trivially ported to 2.x.
> >
> > I'm also not sure if there is any way to support 1.x and 2.x of glib from
> > the same codebase.  If not, that would make migration doubly difficult.
> >
> > > I
> > > tried every combination of keywords and masks and use flags so far in
> > > this thread on 2 different computers and I get errors that the packages
> > > can't be installed, and I keep running into the same bug as the top of
> > > this thread. Am I missing something?
> >
> > Yes.  Clearly, you are incapable of following our directions without a bit
> > more guidance or doing any independent research on the problem.  I can
> > provide that guidance for the low price of 28.50 USD an hour, with a
> > minimum charge of 4 hours; you'll have gnucash installed at the end or no
> > charge at all.  To get started, I'll need your payment information and the
> > contents of /etc/portage/package.* and /etc/make.conf and the output
> > of 'emerge --info', 'ls /etc/portage', 'ls -d /etc/make.profile'; I
> > believe the list would prefer you send this information with private
> > email.
> >
> > For a more expensive, but very reasonable 42.75 USD an hour, you can just
> > give me root access to your Gentoo box(es) and I'll fix them all.  While
> > you do take a bit of a risk (I can do anything with root access, right?),
> > since my access is part of a business arragement my liability for damage I
> > cause, especially intentionally, just went up 10x (or more), at least in
> > my jurisdiction.
> >
> > > If this is a but, won't it be
> > > fixed in some new version of portage?
> >
> > There *a* bug covered at the top of the thread.  It is (1) not a bug with
> > portage, but rather a single package and (2) not likely to get fix since
> > that version of the package depends on (broken) glib 1.x.
> >
>
> Thanks Boyd, for your generous offer! I will take a bit more time and
> read through the gentoo docs again. If I run out of time, I will take
> you up on that!
>
> Thanks again
> rick
>

Try this:

echo =app-office/gnucash-2.0.5 >> /etc/portage/package.keywords
echo dev-libs/g-wrap-1.9.6-r1 >> /etc/portage/package.keywords
echo =dev-scheme/slib-3.1.1-r1 >> /etc/portage/package.keywords
echo =gnome-extra/gtkhtml-3.12.2 >> /etc/portage/package.keywords
echo =gnome-extra/yelp-2.16.2 >> /etc/portage/package.keywords
echo =x11-libs/goffice-0.2.1 >> /etc/portage/package.keywords
echo =dev-scheme/guile-1.8.1-r1 >> /etc/portage/package.keywords
echo =gnome-base/gail-1.9.3 >> /etc/portage/package.keywords
echo =gnome-base/libgnomeprintui-2.12.1 >> /etc/portage/package.keywords
echo =net-libs/libsoup-2.2.99 >> /etc/portage/package.keywords
echo =gnome-base/libgnomeprint-2.12.1 >> /etc/portage/package.keywords
echo =net-print/libgnomecups-0.2.2 >> /etc/portage/package.keywords
emerge -av gnucash


That should work, I would think...

A little background, but you should read
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
http://gentoo-wiki.com/TIP_package.keywords
for more information.

Packages can be in one of 4 states: package masked, -keyword, keyword
masked, or stable.  

Package masked means the package has an entry
in /usr/portage/profiles/package.mask or /etc/portage/package.mask, and
the developer (or admin) thinks the package is broken for some reason.
Use at your own risk, and only if you *know* what you're doing.

-keyword (-amd64, -x86, whatever) means that the package is known broken
on that architecture.  It won't work for you, so don't try it unless you
know how to fix it.  This is common for binary-only packages, which only
run on one (or two) arches.

~keyword means the package is "unstable".  It is in the process of being
tested.  There may or may not be known bugs with the package.  Every
package must spend at least 30 days in ~arch before it can become
stable, to shake out bugs.  Some people (me included) run entire systems
of ~arch versions.  This is done by setting
"ACCEPT_KEYWORDS=~arch" (where arch is x86 or amd64 or whatever)
in /etc/make.conf.  Do this if you want bleeding edge software, and are
willing to test and report bugs.

keyword (x86, amd64, and so on, with no - and no ~) means the package is
stable on that arch.  It has been tested, and went at least 30 days with
no bugs before going stable.  This is what you run if you don't change
anything on your system, and what most people *should* run.

Packages that are not stable are called "masked".  You can unmask
individual packages with files in /etc/portage:
with /etc/portage/package.keywords if it's unstable, or
with /etc/portage/package.unmask if it's package.masked.

Daniel

-- 
gentoo-desktop@g.o mailing list