| 1 |
On 13/07/2016 23:41, James wrote: |
| 2 |
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes: |
| 3 |
> |
| 4 |
>> |
| 5 |
>> On 13/07/2016 20:25, James wrote: |
| 6 |
>>>> |
| 7 |
>>> So, today I ran a sync and upgrade to a gentoo workstation:: |
| 8 |
>>> emerge -uvDNp world |
| 9 |
>>> |
| 10 |
>>> These are the packages that would be merged, in order: |
| 11 |
>>> Calculating dependencies... done! |
| 12 |
>>> Total: 0 packages, Size of downloads: 0 KiB |
| 13 |
>>> WARNING: One or more updates/rebuilds have been skipped due to a dependency |
| 14 |
>>> conflict: |
| 15 |
>>> |
| 16 |
>>> media-libs/jasper:0 |
| 17 |
>>> |
| 18 |
>>> (media-libs/jasper-1.900.1-r9:0/0::gentoo, ebuild scheduled for merge) |
| 19 |
>>> conflicts with |
| 20 |
>>> media-libs/jasper:0/0=[abi_x86_32(-),abi_x86_64(-)] required by |
| 21 |
>>> (x11-libs/gdk-pixbuf-2.32.3:2/2::gentoo, installed) |
| 22 |
>>> |
| 23 |
>>> media-libs/jasper:=[abi_x86_32(-),abi_x86_64(-)] required by |
| 24 |
>>> (x11-libs/gdk-pixbuf-2.32.3:2/2::gentoo, installed) |
| 25 |
>> |
| 26 |
>> This is not a blocker. |
| 27 |
>> |
| 28 |
>> Read the warning, it says an update or rebuild was skipped due to a |
| 29 |
>> dependency conflict. In your casejasper-1.900.1-r9 was not done due to |
| 30 |
>> gdk-pixbuf requirements. Presumably, what you already have keeps pixbuf |
| 31 |
>> happy |
| 32 |
>> |
| 33 |
>> Blockers in that output usually have "!!" annotations at the beginning. |
| 34 |
> |
| 35 |
> Ah excellent point, but the build did not move forward with:: |
| 36 |
> ' emerge -uvDN world' either. With the --tree it did move forward with |
| 37 |
> the build update. In the first attempt usually the packages to be built |
| 38 |
> are listed, conflicts or blockers. |
| 39 |
|
| 40 |
But you didn't run |
| 41 |
emerge -uvDN world |
| 42 |
You ran |
| 43 |
emerge -uvDNp world |
| 44 |
why won't move forward, ever |
| 45 |
|
| 46 |
> |
| 47 |
> None of these 3 packages where listed in the first attempt to see |
| 48 |
> what needs to be built:: |
| 49 |
> Not 'sys-devel/llvm', nor 'sys-devel/clang', nor 'media-libs/mesa'. |
| 50 |
> |
| 51 |
> <snip> |
| 52 |
> |
| 53 |
>>>>>> Emerging (1 of 3) sys-devel/llvm-3.7.1-r3::gentoo |
| 54 |
> |
| 55 |
>>> I did nothing manual in between. Explanations? |
| 56 |
>> portage is doing what's expected. You don't have -a in the command line |
| 57 |
>> and there's nothing stopping portage from moving forward with the build. |
| 58 |
>> SO it moved forward with the build. |
| 59 |
> |
| 60 |
> Yes, nothing to do with 'media-libs/jasper' nor 'gdk-pixbuf'. So I guess the |
| 61 |
> --tree option got rid of the these (conflicts issues. My point is that this |
| 62 |
> is remarkably better than how things worked in the past (but not certain |
| 63 |
> when these enhancements were made). |
| 64 |
|
| 65 |
But you introduced two significant changes in you command line |
| 66 |
removed -N |
| 67 |
added -t |
| 68 |
|
| 69 |
|
| 70 |
It's unsurprising you got different behaviour |
Archives