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
How does that work?