| 1 |
On Wednesday 12 Oct 2016 10:23:15 Neil Bothwick wrote: |
| 2 |
> On Wed, 12 Oct 2016 10:06:34 +0100, Peter Humphrey wrote: |
| 3 |
> > For about a week my daily update has complained thus: |
| 4 |
> > |
| 5 |
> > !!! All ebuilds that could satisfy "=dev-util/boost-build-1.62*" have |
| 6 |
> > been masked. !!! One of the following masked packages is required to |
| 7 |
> > complete your request: |
| 8 |
> > - dev-util/boost-build-1.62.0-r1::gentoo (masked by: ) |
| 9 |
> > |
| 10 |
> > (dependency required by "dev-libs/boost-1.62.0-r1::gentoo" [ebuild]) |
| 11 |
> > |
| 12 |
> > |
| 13 |
> > The ebuild of dev-util/boost-build-1.62.0-r1 includes 'RESTRICT="test"'. |
| 14 |
> > |
| 15 |
> > I have just been waiting for this to be sorted out, but no change yet. |
| 16 |
> > I can upgrade boost-build by specifying USE=test on the command |
| 17 |
> > line, but is that a good idea? |
| 18 |
> |
| 19 |
> This seems to be a fairly regular occurrence with boost. AFAIR I got |
| 20 |
> round it with |
| 21 |
> |
| 22 |
> emerge -1a =dev-libs/boost-1.62.0-r1 =dev-util/boost-build-1.62.0-r1 |
| 23 |
> |
| 24 |
> I didn't mess with USE. |
| 25 |
|
| 26 |
This is now even weirder. I did upgrade boost-build, then emerging boost |
| 27 |
wanted to rebuild 11 other packages - including kdepimlibs, and I do not |
| 28 |
want to break KMail, nor even bruise it. So I didn't emerge boost. |
| 29 |
|
| 30 |
Then, after downgrading boost-build again, emerge -1a boost succeeded in |
| 31 |
upgrading boost-build, without the USE flag, and is now proceeding with the |
| 32 |
other 11. |
| 33 |
|
| 34 |
How does that work? |
| 35 |
|
| 36 |
-- |
| 37 |
Rgds |
| 38 |
Peter |
Archives