public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thelma@sys-concept.com
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] webkit-gtk build failure and masking confusion
Date: Mon, 19 Feb 2018 11:05:37 -0700	[thread overview]
Message-ID: <3698f8fd-6b1a-c2ff-d204-1f41787b6027@sys-concept.com> (raw)
In-Reply-To: <CAC_tCmqY59vZpb9Qn6UZAuYdafos2hgxV=4maT1yihueaHK0jA@mail.gmail.com>

On 02/18/2018 05:50 PM, John Blinka wrote:
> On Sun, Feb 18, 2018 at 10:40 AM allan gottlieb <gottlieb@nyu.edu> wrote:
> 
>> On Sun, Feb 18 2018, Mick wrote:
>>
>>> On Sunday, 18 February 2018 01:09:36 GMT allan gottlieb wrote:
>>
>>     Specifically excluding the buggy (old) version of webkit-gtk,
>>     portage wants me to merge a newish (testing) version of gnucash that
>>     uses a solid new version of webkit-gtk.  I have the new version of
>>     webkit-gtk, but really want to delay installing the testing gnucash.
> 
> 
> Looks like gnucash-2.7.4-r1 is now in the stable branch of portage despite
> gnucash declaring “This release is UNSTABLE and SHOULD NOT BE USED in
> production” (their caps, not mine).  I’ve masked it and reverted to
> icu58.2-r1 by masking icu-60.2.  The older icu allows
> webkit-gtk-2.4.11-r200 to build, and gives me a version of gnucash which
> I’ve used for a long time and trust.  Not going to upgrade irreversibly to
> a version which the authors themselves don’t trust.  My 2 cents.
> 
> John

It is a good point. Why Gentoo developers marked or allow to mark
gnucash-2.7 branch stable in portage when the developers
https://www.gnucash.org/download.phtml did not mark it STABLE

It seems to me one of Gentoo developer is trying to use us a guinea pigs
and the UNSTABLE "gnucash-2.7" on us.

--
Thelma.


  parent reply	other threads:[~2018-02-19 18:05 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
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 [this message]
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=3698f8fd-6b1a-c2ff-d204-1f41787b6027@sys-concept.com \
    --to=thelma@sys-concept.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