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