From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Boost and boost-build out of step
Date: Wed, 12 Oct 2016 10:37:11 +0100 [thread overview]
Message-ID: <2918398.W3mL5XdJRd@peak> (raw)
In-Reply-To: <20161012102315.087b026e@digimed.co.uk>
On Wednesday 12 Oct 2016 10:23:15 Neil Bothwick wrote:
> On Wed, 12 Oct 2016 10:06:34 +0100, Peter Humphrey wrote:
> > For about a week my daily update has complained thus:
> >
> > !!! All ebuilds that could satisfy "=dev-util/boost-build-1.62*" have
> > been masked. !!! One of the following masked packages is required to
> > complete your request:
> > - dev-util/boost-build-1.62.0-r1::gentoo (masked by: )
> >
> > (dependency required by "dev-libs/boost-1.62.0-r1::gentoo" [ebuild])
> >
> >
> > The ebuild of dev-util/boost-build-1.62.0-r1 includes 'RESTRICT="test"'.
> >
> > I have just been waiting for this to be sorted out, but no change yet.
> > I can upgrade boost-build by specifying USE=test on the command
> > line, but is that a good idea?
>
> This seems to be a fairly regular occurrence with boost. AFAIR I got
> round it with
>
> emerge -1a =dev-libs/boost-1.62.0-r1 =dev-util/boost-build-1.62.0-r1
>
> I didn't mess with USE.
This is now even weirder. I did upgrade boost-build, then emerging boost
wanted to rebuild 11 other packages - including kdepimlibs, and I do not
want to break KMail, nor even bruise it. So I didn't emerge boost.
Then, after downgrading boost-build again, emerge -1a boost succeeded in
upgrading boost-build, without the USE flag, and is now proceeding with the
other 11.
How does that work?
--
Rgds
Peter
prev parent reply other threads:[~2016-10-12 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 9:06 [gentoo-user] Boost and boost-build out of step Peter Humphrey
2016-10-12 9:23 ` Neil Bothwick
2016-10-12 9:37 ` Peter Humphrey [this message]
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=2918398.W3mL5XdJRd@peak \
--to=peter@prh.myzen.co.uk \
--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