| 1 |
On Tue, Nov 21, 2017 at 8:36 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> On 21/11/2017 15:03, Mick wrote: |
| 3 |
>> I see that <media-libs/gst-plugins-bad-1.11.90:1.0 is blocking media-libs/gst- |
| 4 |
>> plugins-base-1.12.3, so I removed various gst-plugins and net-libs/farstream, |
| 5 |
>> emerged -1 media-libs/gst-plugins-base-1.12.3, but portage continues to |
| 6 |
>> complain, with backtrack=99 or not. |
| 7 |
>> |
| 8 |
> |
| 9 |
> There's no obvious reason why portage should select |
| 10 |
> media-libs/gst-plugins-bad-1.10.5, and gst-plugins has updated cleanly |
| 11 |
> for me for months now. By I'm on ~arch and your packages are arch. Can |
| 12 |
> we re-check the obvious? |
| 13 |
> |
| 14 |
> emerge --sync up to date? |
| 15 |
|
| 16 |
The package was not correctly stabilized, and this was reported and |
| 17 |
corrected. Re-sync and the problem will go away. |
| 18 |
|
| 19 |
-- |
| 20 |
Rich |
Archives