From: allan gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] webkit-gtk build failure and masking confusion
Date: Sat, 17 Feb 2018 20:09:36 -0500 [thread overview]
Message-ID: <87371zt86n.fsf@nyu.edu> (raw)
In-Reply-To: <CAC_tCmqRv9_h5uoLDQ5seiBh_=Xy5W9BDtYeCRFHfXy1-6hEew@mail.gmail.com> (John Blinka's message of "Sat, 17 Feb 2018 15:23:13 -0500")
On Sat, Feb 17 2018, John Blinka wrote:
> Hi, all,
>
> A recent update demanded that I rebuild webkit-gtk-2.4.11-r200.
> Unfortunately I cannot get this package to rebuild.
>
> In my experience, this particular version of webkit-gtk has always
> been a very fragile build. I've put way too much time into wrestling
> with it and I'd like to get rid of it. There's a newer version:
> webkit-gtk-2.18.6, which builds with no problems.
>
> The only package on my system that needs webkit-gtk is gnucash. All
> of the stable ebuilds for gnucash contain this line
> >=net-libs/webkit-gtk-1.2:2
> And all of the versions of webkit-gtk in portage satisfy this condition.
I am in the same situation and I believe a number of other are as well.
The old webkit-gtk is approaching end-of-life and the new gnucash that
uses the new webkit-gtk is (they say) soon to become gentoo stable.
NOTE. The new gnucash uses a new database format so you should back up
your old database before updating gnucash (see the news item).
I am waiting for the new gnucash to become stable (and will probably
wait a little more). I back up the gnucash database daily. I would be
quite put out if gnucash was unavailable for even a modest time period.
What I do in the meantime is
emerge --update --pretend @world
and then manually
emerge -1 all packages mentioned except webkit-gtk
I do a similar procedure for
emerge @preserved rebuild
allan
next prev parent reply other threads:[~2018-02-18 1:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 20:23 [gentoo-user] webkit-gtk build failure and masking confusion John Blinka
2018-02-17 20:38 ` Neil Bothwick
2018-02-17 23:20 ` John Blinka
2018-02-18 2:14 ` Neil Bothwick
2018-02-18 2:30 ` allan gottlieb
2018-02-18 4:07 ` Jack
2018-02-18 9:52 ` Neil Bothwick
2018-02-19 16:52 ` Peter Humphrey
2018-02-18 1:09 ` allan gottlieb [this message]
2018-02-18 8:51 ` Mick
2018-02-18 9:49 ` Neil Bothwick
2018-02-18 15:41 ` allan gottlieb
2018-02-18 15:39 ` allan gottlieb
2018-02-19 0:50 ` John Blinka
2018-02-19 1:42 ` allan gottlieb
2018-02-19 18:05 ` thelma
2018-02-19 18:59 ` Neil Bothwick
2018-02-19 19:40 ` allan gottlieb
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=87371zt86n.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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