On 13/07/2016 23:41, James wrote:
Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
On 13/07/2016 20:25, James wrote:
So, today I ran a sync and upgrade to a gentoo workstation::
emerge -uvDNp world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 KiB
WARNING: One or more updates/rebuilds have been skipped due to a dependency
conflict:
media-libs/jasper:0
(media-libs/jasper-1.900.1-r9:0/0::gentoo, ebuild scheduled for merge)
conflicts with
media-libs/jasper:0/0=[abi_x86_32(-),abi_x86_64(-)] required by
(x11-libs/gdk-pixbuf-2.32.3:2/2::gentoo, installed)
media-libs/jasper:=[abi_x86_32(-),abi_x86_64(-)] required by
(x11-libs/gdk-pixbuf-2.32.3:2/2::gentoo, installed)
This is not a blocker.
Read the warning, it says an update or rebuild was skipped due to a
dependency conflict. In your casejasper-1.900.1-r9 was not done due to
gdk-pixbuf requirements. Presumably, what you already have keeps pixbuf
happy
Blockers in that output usually have "!!" annotations at the beginning.
Ah excellent point, but the build did not move forward with::
' emerge -uvDN world' either. With the --tree it did move forward with
the build update. In the first attempt usually the packages to be built
are listed, conflicts or blockers.
But you didn't run
emerge -uvDN world
You ran
emerge -uvDNp world
why won't move forward, ever
None of these 3 packages where listed in the first attempt to see
what needs to be built::
Not 'sys-devel/llvm', nor 'sys-devel/clang', nor 'media-libs/mesa'.
<snip>
Emerging (1 of 3) sys-devel/llvm-3.7.1-r3::gentoo
I did nothing manual in between. Explanations?
portage is doing what's expected. You don't have -a in the command line
and there's nothing stopping portage from moving forward with the build.
SO it moved forward with the build.
Yes, nothing to do with 'media-libs/jasper' nor 'gdk-pixbuf'. So I guess the
--tree option got rid of the these (conflicts issues. My point is that this
is remarkably better than how things worked in the past (but not certain
when these enhancements were made).
But you introduced two significant changes in you command line
removed -N
added -t
It's unsurprising you got different behaviour
