| 1 |
On Monday, 18 June 2018 21:28:38 BST allan gottlieb wrote: |
| 2 |
> On Mon, Jun 18 2018, Mick wrote: |
| 3 |
> > Hi Allan, |
| 4 |
> > |
| 5 |
> > On Monday, 18 June 2018 18:52:31 BST allan gottlieb wrote: |
| 6 |
> >> On Sun, Jun 17 2018, Mick wrote: |
| 7 |
> >> > On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote: |
| 8 |
> >> >> (I have been offline for a few months and apologize if this has been |
| 9 |
> >> >> covered.) |
| 10 |
> >> >> |
| 11 |
> >> >> I had not synced for about 3 months (fear of new, incompatible |
| 12 |
> >> >> gnucash) |
| 13 |
> >> >> but have now done so. Unsurprisingly my normal update world shows |
| 14 |
> >> >> many |
| 15 |
> >> >> entries and also unsurprising is a blocker (slot conflict). |
| 16 |
> > |
| 17 |
> > As a first step I suggest you go through the 'eselect news read new'. |
| 18 |
> > |
| 19 |
> > There was a profile change sometime late last year. The profile change |
| 20 |
> > enews is important and you should deal with it first. It is titled: |
| 21 |
> > |
| 22 |
> > 'New 17.0 profiles in the Gentoo repository' |
| 23 |
> > |
| 24 |
> > and it involves updating gcc as part of it and perhaps changing your |
| 25 |
> > profile if it is due to be deprecated. |
| 26 |
> |
| 27 |
> I had done the upgrade to 17.0 months ago. |
| 28 |
> 17.1 is unstable so I believe 17.0 is the right profile for me. |
| 29 |
> |
| 30 |
> > Once you've been through all this give it another spin, but use |
| 31 |
> > --backtrack=99 to see if portage resolves the conflicts. |
| 32 |
> |
| 33 |
> backtrack=99 didn't change the situation, but adding in addition |
| 34 |
> --autounmask-backtrack=y did! |
| 35 |
|
| 36 |
Interesting! What did it autounmask? |
| 37 |
|
| 38 |
|
| 39 |
> > I can't see a [B] in the list you provided, all are small blocks [b] which |
| 40 |
> > portage will deal with on its own. |
| 41 |
> |
| 42 |
> The list I provided was for my update world. That has little b's. The |
| 43 |
> only blockage I have is the slot conflict I mentioned originally. The |
| 44 |
> big B's happened when I tried |
| 45 |
> |
| 46 |
> emerge -1pDv media-video/ffmpeg |
| 47 |
|
| 48 |
Well, media-libs/x264-0.0.20130506 is no longer in the tree. media-video/ |
| 49 |
ffmpeg-3.3.6 does not require it and works fine with media-libs/ |
| 50 |
x264-0.0.20160712. This is why I suggested that manual removal and update |
| 51 |
earlier on. |
| 52 |
|
| 53 |
Unless something else is blocking ffmpeg (you've got a long update list there |
| 54 |
which might influence it) there shouldn't be a problem with my suggested |
| 55 |
workaround. Nevertheless, getting portage to pontificate and resolve the |
| 56 |
dependency graph is invariably a safer option. ;-) |
| 57 |
|
| 58 |
-- |
| 59 |
Regards, |
| 60 |
Mick |
Archives