On 30/05/2016 12:08, Dale wrote:
Alan McKinnon wrote:
On 30/05/2016 05:20, Dale wrote:
Howdy,

I'm trying to do a update and have this last blocker that I can't figure
out.  I fixed another one but this one doesn't make sense to me.  Here
is the relevant output.


Portage is abusing your pixels (using too many). Here's the important
bits:

[blocks B      ] <kde-apps/libksane-15.08.3-r1:4
("<kde-apps/libksane-15.08.3-r1:4" is blocking
kde-apps/libksane-16.04.1)

This is the only important blocker ("blocks B")

procps stuff that followed is just a long explanation of why portage
kept procps back and didn't upgrade

Yea, I included more than what was needed and I already worked around
procps.  It's gone already.


   * Error: The above package list contains packages which cannot be
   * installed at the same time on the same system.

The asterisks indicate this is part relevant to hard blockers and
failures. (bangs ! indicate info or warnings, not errors)

    (kde-apps/libksane-15.08.3:4/15.08::gentoo, installed) pulled in by
      >=kde-apps/libksane-4.14.3:4[aqua=]
(>=kde-apps/libksane-4.14.3:4[-aqua]) required by
(kde-apps/ksaneplugin-16.04.1:4/16.04::gentoo, ebuild scheduled for
merge)
      >=kde-apps/libksane-4.14.3:4[aqua=]
(>=kde-apps/libksane-4.14.3:4[-aqua]) required by
(kde-apps/kolourpaint-16.04.1:4/16.04::gentoo, ebuild scheduled for
merge)

    (kde-apps/libksane-16.04.1:5/5::gentoo, ebuild scheduled for merge)
pulled in by
      >=kde-apps/libksane-14.12.0:5 required by
(kde-misc/skanlite-2.0:5/5::gentoo, ebuild scheduled for merge)
      >=kde-apps/libksane-16.04.1 required by
(kde-apps/kdegraphics-meta-16.04.1:5/5::gentoo, ebuild scheduled for
merge)



So this is really a clash between KDE4 stuff and KDE5 stuff, and
nothing is demanding a certain maximum version, so upgrades should in
theory be clean. I'm not at a Gentoo machine right now so can't give
exact info, but do this:

eix libksane
- is 15.08.3-r1 the latest version in :4? If not, upgrade it manually
and continue.
- does 15.08.3-r1 have a minimal USE? If so, set it on. This often
removes the clash with :5

If all else fails, quickpkg and unmerge all libksane version, emerge
world and let portage fix whatever it needs to.

/alanm



I removed all libksane versions and it still pukes.  I then did a equery
list *sane* and -C'd all that too.  None of that will cause a crash or
anything.  Anyway, it still isn't happy.  After doing all that, I had a
thought.  Add the -t option.  It didn't help much but at least I finally
thought of it.  lol  Here is the current upset pixels with the -t added
in.

[snip]

[blocks B      ] <kde-apps/libksane-15.08.3-r1:4
("<kde-apps/libksane-15.08.3-r1:4" is blocking kde-apps/libksane-16.04.1)

Total: 45 packages (31 upgrades, 11 new, 2 in new slots, 1 reinstall, 3
uninstalls), Size of downloads: 16,615 KiB
Conflict: 5 blocks (1 unsatisfied)

  * Error: The above package list contains packages which cannot be
  * installed at the same time on the same system.

   (kde-apps/libksane-15.08.3:4/15.08::gentoo, ebuild scheduled for
merge) pulled in by
     >=kde-apps/libksane-4.14.3:4[aqua=]
(>=kde-apps/libksane-4.14.3:4[-aqua]) required by
(kde-apps/ksaneplugin-16.04.1:4/16.04::gentoo, ebuild scheduled for merge)
     >=kde-apps/libksane-4.14.3:4[aqua=]
(>=kde-apps/libksane-4.14.3:4[-aqua]) required by
(kde-apps/kolourpaint-16.04.1:4/16.04::gentoo, ebuild scheduled for merge)

   (kde-apps/libksane-16.04.1:5/5::gentoo, ebuild scheduled for merge)
pulled in by
     >=kde-apps/libksane-14.12.0:5 required by
(kde-misc/skanlite-2.0:5/5::gentoo, ebuild scheduled for merge)
     >=kde-apps/libksane-16.04.1 required by
(kde-apps/kdegraphics-meta-16.04.1:5/5::gentoo, ebuild scheduled for merge)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):



To me, it seems two packages want one version and two other packages
want the other and both can't be there at the same time.  Right now, I
can't quite find the right key to unlock this thing.  By the way, I did
sync again just to be sure.  I also set the minimal USE flag in
package.use for that too.



There is only one problem here:

kde-apps/libksane-16.04.1 blocks any version of <kde-apps/libksane-15.08.3-r1 (note the less than)

But portage wants to install kde-apps/libksane-15.08.3 which triggers the block.

You need to find out why portage isn't giving you the latest libksane:4

- do you have kde-apps/libksane-15.08.3-r1 in your tree? If not, resync
- is this an arch or ~arch machine? If arch, do you have any unmasks for libksane:5?

grep -r ksane /etc/portage


If all else fails,
emerge =kde-apps/libksane-15.08.3-r1
and inspect the error closely. That will tell you why portage decided to not give you that version

Reply via email to