Re: [gentoo-user] kde-apps/libksane blocker
Dale wrote:
> New but somewhat related problem.
>
>
> Calculating dependencies... done!
> [ebuild U ~] kde-apps/kde-meta-16.04.1:5::gentoo [15.12.3:5::gentoo]
> 0 KiB
> [ebuild U ~] kde-apps/kde-apps-meta-16.04.1:5::gentoo
> [15.12.3-r3:5::gentoo] USE="nls -accessibility -minimal -pim -sdk" 0 KiB
> [ebuild U ~] kde-apps/kdenetwork-meta-16.04.1:5::gentoo
> [15.12.3-r1:5::gentoo] USE="ppp telepathy%*" 0 KiB
> [ebuild N~]kde-apps/plasma-telepathy-meta-16.04.1:5::gentoo
> USE="nls -gstreamer" 0 KiB
> [ebuild N~] kde-apps/ktp-accounts-kcm-16.04.1:5::gentoo
> USE="-debug -experimental" 0 KiB
> [ebuild N~] kde-apps/kaccounts-providers-16.04.1:5::gentoo
> USE="-debug" 0 KiB
> [ebuild N ]
> net-im/telepathy-connection-managers-2-r2::gentoo USE="irc xmpp yahoo
> zeroconf -gadu -icq -meanwhile -msn -sip -sipe -steam" 0 KiB
> [ebuild N ]net-voip/telepathy-gabble-0.18.3::gentoo
> USE="gnutls -jingle -plugins {-test}" 0 KiB
>
> Total: 8 packages (3 upgrades, 5 new), Size of downloads: 0 KiB
>
>
> And the build.log, relevant part.
>
>
> /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
> -std=gnu99 -DHAVE_CONFIG_H -I. -I..-Wall -Wextra
> -Wdeclaration-after-statement -Wshadow -Wstrict-prototypes
> -Wmissing-declarations -Wmissing-prototypes -Wsign-compare
> -Wnested-externs -Wpointer-arith -Wformat-security -Winit-self
> -Wno-missing-field-initializers -Wno-deprecated-declarations
> -Wno-unused-parameter -I.. -I.. -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread
> -I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky
> -I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky/wocky
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread
> -I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I ../lib -I ../lib
> -DG_LOG_DOMAIN=\"gabble\"
> -DPLUGIN_DIR=\"/usr/lib64/telepathy/gabble-0/plugins\" -march=native
> -O2 -pipe -c -o muc-factory.lo muc-factory.c
> libtool: compile: x86_64-pc-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H
> -I. -I.. -Wall -Wextra -Wdeclaration-after-statement -Wshadow
> -Wstrict-prototypes -Wmissing-declarations -Wmissing-prototypes
> -Wsign-compare -Wnested-externs -Wpointer-arith -Wformat-security
> -Winit-self -Wno-missing-field-initializers -Wno-deprecated-declarations
> -Wno-unused-parameter -I.. -I.. -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread
> -I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky
> -I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky/wocky
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread
> -I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I ../lib -I ../lib
> -DG_LOG_DOMAIN=\"gabble\"
> -DPLUGIN_DIR=\"/usr/lib64/telepathy/gabble-0/plugins\" -march=native -O2
> -pipe -c muc-factory.c -fPIC -DPIC -o .libs/muc-factory.o
> /bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
> -std=gnu99 -DHAVE_CONFIG_H -I. -I..-Wall -Wextra
> -Wdeclaration-after-statement -Wshadow -Wstrict-prototypes
> -Wmissing-declarations -Wmissing-prototypes -Wsign-compare
> -Wnested-externs -Wpointer-arith -Wformat-security -Winit-self
> -Wno-missing-field-initializers -Wno-deprecated-declarations
> -Wno-unused-parameter -I.. -I.. -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread
> -I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky
> -I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky/wocky
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread
> -I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I ../lib -I ../lib
> -DG_LOG_DOMAIN=\"gabble\"
> -DPLUGIN_DIR=\"/usr/lib64/telepathy/gabble-0/plugins\" -march=native
> -O2 -pipe -c -o muc-tube-dbus.lo muc-tube-dbus.c
> muc-channel.c: In function ‘gabble_muc_channel_can_be_closed’:
> muc-channel.c:1650:11: error: ‘GabbleMucChannelPrivate’ has no member
> named ‘calls’
>if (priv->calls != NULL
Re: [gentoo-user] kde-apps/libksane blocker
On 30/05/2016 22:12, Dale wrote: > Daniel Frey wrote: >> On 05/29/2016 08:20 PM, 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. >>> >>> >>> >>> >>> >>> As you can see, none of them are keyworded so it should be able to use >>> the latest packages. I just synced a hour or so ago so this may be more >>> up to date than you may have on your system. It's why I am including >>> the info here. >>> >>> Is it possible I caught the tree in the middle of a update and I need to >>> sync again? Is my old eyes missing something obvious? Or, is it what I >>> think, a conflict that can't yet be solved because of a hard dependency? >>> >>> Looking for thoughts, ideas, suggestions. >>> >>> Dale >>> >>> :-) :-) >>> >>> >> Are you using plasma? I was but it was crashing every 10 seconds so I >> went back to kde4 and masked all kde-related packages >4.15. I also >> disabled the wallpapers. >> >> I just installed a scanner yesterday (ironically) and I didn't see this >> issue when rebuilding. >> >> Dan >> >> > > > Yea, I switched a while back and so far, it works OK. It is a bit > different and my clock on the little panel thingy at the bottom of the > screen winks at me from time to time. Other than that tho, it works OK. > > Most likely, you are still using the older versions. This just might be > a actual bug but before I file one, I want to hear from someone else who > can confirm it. > > Dale > > :-) :-) > > P. S. I hate breaking down a lawn mower tire when it is 92F outside > with some humidity. Also, I live under a large hill, no wind. I guess > it could be 98F tho. o_O > It could be worse. You could live in Africa and deal with roads at temp 42 C :-) -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] kde-apps/libksane blocker
Daniel Frey wrote: > On 05/29/2016 08:20 PM, 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. >> >> >> >> >> >> As you can see, none of them are keyworded so it should be able to use >> the latest packages. I just synced a hour or so ago so this may be more >> up to date than you may have on your system. It's why I am including >> the info here. >> >> Is it possible I caught the tree in the middle of a update and I need to >> sync again? Is my old eyes missing something obvious? Or, is it what I >> think, a conflict that can't yet be solved because of a hard dependency? >> >> Looking for thoughts, ideas, suggestions. >> >> Dale >> >> :-) :-) >> >> > Are you using plasma? I was but it was crashing every 10 seconds so I > went back to kde4 and masked all kde-related packages >4.15. I also > disabled the wallpapers. > > I just installed a scanner yesterday (ironically) and I didn't see this > issue when rebuilding. > > Dan > > Yea, I switched a while back and so far, it works OK. It is a bit different and my clock on the little panel thingy at the bottom of the screen winks at me from time to time. Other than that tho, it works OK. Most likely, you are still using the older versions. This just might be a actual bug but before I file one, I want to hear from someone else who can confirm it. Dale :-) :-) P. S. I hate breaking down a lawn mower tire when it is 92F outside with some humidity. Also, I live under a large hill, no wind. I guess it could be 98F tho. o_O
Re: [gentoo-user] kde-apps/libksane blocker
On 05/29/2016 08:20 PM, 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. > > > > > > As you can see, none of them are keyworded so it should be able to use > the latest packages. I just synced a hour or so ago so this may be more > up to date than you may have on your system. It's why I am including > the info here. > > Is it possible I caught the tree in the middle of a update and I need to > sync again? Is my old eyes missing something obvious? Or, is it what I > think, a conflict that can't yet be solved because of a hard dependency? > > Looking for thoughts, ideas, suggestions. > > Dale > > :-) :-) > > Are you using plasma? I was but it was crashing every 10 seconds so I went back to kde4 and masked all kde-related packages >4.15. I also disabled the wallpapers. I just installed a scanner yesterday (ironically) and I didn't see this issue when rebuilding. Dan
Re: [gentoo-user] kde-apps/libksane blocker
New but somewhat related problem.
Calculating dependencies... done!
[ebuild U ~] kde-apps/kde-meta-16.04.1:5::gentoo [15.12.3:5::gentoo]
0 KiB
[ebuild U ~] kde-apps/kde-apps-meta-16.04.1:5::gentoo
[15.12.3-r3:5::gentoo] USE="nls -accessibility -minimal -pim -sdk" 0 KiB
[ebuild U ~] kde-apps/kdenetwork-meta-16.04.1:5::gentoo
[15.12.3-r1:5::gentoo] USE="ppp telepathy%*" 0 KiB
[ebuild N~]kde-apps/plasma-telepathy-meta-16.04.1:5::gentoo
USE="nls -gstreamer" 0 KiB
[ebuild N~] kde-apps/ktp-accounts-kcm-16.04.1:5::gentoo
USE="-debug -experimental" 0 KiB
[ebuild N~] kde-apps/kaccounts-providers-16.04.1:5::gentoo
USE="-debug" 0 KiB
[ebuild N ]
net-im/telepathy-connection-managers-2-r2::gentoo USE="irc xmpp yahoo
zeroconf -gadu -icq -meanwhile -msn -sip -sipe -steam" 0 KiB
[ebuild N ]net-voip/telepathy-gabble-0.18.3::gentoo
USE="gnutls -jingle -plugins {-test}" 0 KiB
Total: 8 packages (3 upgrades, 5 new), Size of downloads: 0 KiB
And the build.log, relevant part.
/bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
-std=gnu99 -DHAVE_CONFIG_H -I. -I..-Wall -Wextra
-Wdeclaration-after-statement -Wshadow -Wstrict-prototypes
-Wmissing-declarations -Wmissing-prototypes -Wsign-compare
-Wnested-externs -Wpointer-arith -Wformat-security -Winit-self
-Wno-missing-field-initializers -Wno-deprecated-declarations
-Wno-unused-parameter -I.. -I.. -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread
-I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky
-I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky/wocky
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -I ../lib -I ../lib
-DG_LOG_DOMAIN=\"gabble\"
-DPLUGIN_DIR=\"/usr/lib64/telepathy/gabble-0/plugins\" -march=native
-O2 -pipe -c -o muc-factory.lo muc-factory.c
libtool: compile: x86_64-pc-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H
-I. -I.. -Wall -Wextra -Wdeclaration-after-statement -Wshadow
-Wstrict-prototypes -Wmissing-declarations -Wmissing-prototypes
-Wsign-compare -Wnested-externs -Wpointer-arith -Wformat-security
-Winit-self -Wno-missing-field-initializers -Wno-deprecated-declarations
-Wno-unused-parameter -I.. -I.. -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread
-I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky
-I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky/wocky
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -I ../lib -I ../lib
-DG_LOG_DOMAIN=\"gabble\"
-DPLUGIN_DIR=\"/usr/lib64/telepathy/gabble-0/plugins\" -march=native -O2
-pipe -c muc-factory.c -fPIC -DPIC -o .libs/muc-factory.o
/bin/sh ../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc
-std=gnu99 -DHAVE_CONFIG_H -I. -I..-Wall -Wextra
-Wdeclaration-after-statement -Wshadow -Wstrict-prototypes
-Wmissing-declarations -Wmissing-prototypes -Wsign-compare
-Wnested-externs -Wpointer-arith -Wformat-security -Winit-self
-Wno-missing-field-initializers -Wno-deprecated-declarations
-Wno-unused-parameter -I.. -I.. -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread
-I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky
-I/var/tmp/portage/net-voip/telepathy-gabble-0.18.3/work/telepathy-gabble-0.18.3/lib/ext/wocky/wocky
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread
-I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0
-I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -I ../lib -I ../lib
-DG_LOG_DOMAIN=\"gabble\"
-DPLUGIN_DIR=\"/usr/lib64/telepathy/gabble-0/plugins\" -march=native
-O2 -pipe -c -o muc-tube-dbus.lo muc-tube-dbus.c
muc-channel.c: In function ‘gabble_muc_channel_can_be_closed’:
muc-channel.c:1650:11: error: ‘GabbleMucChannelPrivate’ has no member
named ‘calls’
if (priv->calls != NULL || priv->call_requests != NULL
^
muc-channel.c:1650:34: error: ‘GabbleMucChannelPrivate’ has no member
named ‘call_requests’
if (priv->calls != NULL || priv->call_requests
Re: [gentoo-user] kde-apps/libksane blocker
Alan McKinnon wrote: > > > > There is only one problem here: > > kde-apps/libksane-16.04.1 blocks any version of > > 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 > > OK. Between your post and Neil's reply, success. I'm not real sure which hit best but it gave me ideas to try and run with since I was stuck. I'm not even sure what all I tried now either. However, here is the output of that nifty grep command. root@fireball / # grep -r ksane /etc/portage /etc/portage/package.accept_keywords/package.accept_keywords:=kde-apps/ksaneplugin-16.04.1 ~amd64 /etc/portage/package.accept_keywords/package.accept_keywords:=kde-apps/libksane-15.08.3-r1 /etc/portage/package.accept_keywords/package.accept_keywords:=kde-apps/libksane-16.04.1 ~amd64 /etc/portage/package.use/package.use:kde-apps/libksane minimal root@fireball / # I did have more than that but I removed everything related and started over. That was the end result, after emerge spit out some more stuff. I think I had something in there that may have been needed prior to this but was causing a problem now. Neil's reply gave me that hint. And then a package fails to build. Now to see what that is all about. :/ Thanks much to both you and Neil. :-) If only that other Alan would listen to you two. ROFL Dale :-) :-)
Re: [gentoo-user] kde-apps/libksane blocker
On Mon, 30 May 2016 05:08:47 -0500, Dale wrote:
> 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.
>
>
> [nomerge ] kde-apps/kdenetwork-meta-16.04.1:5::gentoo
> [15.12.3-r1:5::gentoo] USE="ppp telepathy%*"
> [ebuild U ~] kde-apps/kget-16.04.1:4/16.04::gentoo
> [15.12.3:4/15.12::gentoo] USE="handbook sqlite webkit (-aqua)
> -bittorrent -debug -gpg -mms" 1,057 KiB
> [ebuild U ~] kde-apps/kppp-16.04.1:4/16.04::gentoo
> [15.12.3:4/15.12::gentoo] USE="handbook (-aqua) -debug" 684 KiB
> [ebuild U ~] kde-apps/zeroconf-ioslave-16.04.1:4/16.04::gentoo
> [15.12.3:4/15.12::gentoo] USE="(-aqua) -debug" 26 KiB
> [nomerge ] kde-apps/kdegraphics-meta-16.04.1:5::gentoo
> [15.12.3:5::gentoo] USE="scanner"
> [ebuild N~] kde-apps/kolourpaint-16.04.1:4/16.04::gentoo
> USE="handbook scanner (-aqua) -debug" 0 KiB
> [ebuild U ~]
> kde-apps/kdegraphics-mobipocket-16.04.1-r1:4/16.04::gentoo
> [15.12.3:4/15.12::gentoo] USE="(-aqua) -debug" 15 KiB
> [ebuild U ~] kde-apps/svgpart-16.04.1:4/16.04::gentoo
> [15.12.3:4/15.12::gentoo] USE="(-aqua) -debug" 9 KiB
> [ebuild N~] kde-apps/ksaneplugin-16.04.1:4/16.04::gentoo
> USE="(-aqua) -debug" 0 KiB
> [ebuild N ] kde-apps/libksane-15.08.3:4/15.08::gentoo
^^^
> USE="minimal (-aqua) -debug" 0 KiB
[snip]
> [blocks B ] (" kde-apps/libksane-16.04.1)
Here's your problem, 16.04.1 can only co-exists with 15.03.3-r1 or
higher, but you are trying to install 15.03.3. The -r1 version is
testing, it hasn't been stabilised yet. Try adding it to
package.accept_keywords.
If that fixes it, file a stabilisation bug.
--
Neil Bothwick
Modulation in all things.
pgpmSOCWK4o6p.pgp
Description: OpenPGP digital signature
Re: [gentoo-user] kde-apps/libksane blocker
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 ]
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-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
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
Re: [gentoo-user] kde-apps/libksane blocker
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-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.
[nomerge ] kde-apps/kdenetwork-meta-16.04.1:5::gentoo
[15.12.3-r1:5::gentoo] USE="ppp telepathy%*"
[ebuild U ~] kde-apps/kget-16.04.1:4/16.04::gentoo
[15.12.3:4/15.12::gentoo] USE="handbook sqlite webkit (-aqua)
-bittorrent -debug -gpg -mms" 1,057 KiB
[ebuild U ~] kde-apps/kppp-16.04.1:4/16.04::gentoo
[15.12.3:4/15.12::gentoo] USE="handbook (-aqua) -debug" 684 KiB
[ebuild U ~] kde-apps/zeroconf-ioslave-16.04.1:4/16.04::gentoo
[15.12.3:4/15.12::gentoo] USE="(-aqua) -debug" 26 KiB
[nomerge ] kde-apps/kdegraphics-meta-16.04.1:5::gentoo
[15.12.3:5::gentoo] USE="scanner"
[ebuild N~] kde-apps/kolourpaint-16.04.1:4/16.04::gentoo
USE="handbook scanner (-aqua) -debug" 0 KiB
[ebuild U ~]
kde-apps/kdegraphics-mobipocket-16.04.1-r1:4/16.04::gentoo
[15.12.3:4/15.12::gentoo] USE="(-aqua) -debug" 15 KiB
[ebuild U ~] kde-apps/svgpart-16.04.1:4/16.04::gentoo
[15.12.3:4/15.12::gentoo] USE="(-aqua) -debug" 9 KiB
[ebuild N~] kde-apps/ksaneplugin-16.04.1:4/16.04::gentoo
USE="(-aqua) -debug" 0 KiB
[ebuild N ] kde-apps/libksane-15.08.3:4/15.08::gentoo
USE="minimal (-aqua) -debug" 0 KiB
[nomerge ] kde-apps/kget-16.04.1:4/16.04::gentoo
[15.12.3:4/15.12::gentoo] USE="handbook sqlite webkit (-aqua)
-bittorrent -debug -gpg -mms"
[ebuild U ] kde-apps/libkonq-15.12.3:4/15.12::gentoo
[15.08.3:4/15.08::gentoo] USE="(-aqua) -debug {-test} (-minimal%)" 0 KiB
[nomerge ] kde-apps/kdenetwork-meta-16.04.1:5::gentoo
[15.12.3-r1:5::gentoo] USE="ppp telepathy%*"
[ebuild U ~] kde-apps/krfb-16.04.1:5::gentoo [15.12.3:5::gentoo]
USE="handbook -debug -doc" 318 KiB
[nomerge ] kde-apps/kdegraphics-meta-16.04.1:5::gentoo
[15.12.3:5::gentoo] USE="scanner"
[ebuild U ~] kde-apps/kruler-16.04.1:5::gentoo [15.12.3:5::gentoo]
USE="X handbook -debug" 121 KiB
[ebuild N~] kde-apps/libksane-16.04.1:5::gentoo USE="-debug" 0 KiB
[nomerge ] kde-apps/ktp-accounts-kcm-16.04.1:5::gentoo
USE="-debug -experimental"
[nomerge ] net-im/telepathy-connection-managers-2-r2::gentoo
USE="irc xmpp yahoo zeroconf -gadu -icq -meanwhile -msn -sip -sipe -steam"
[ebuild N ] net-voip/telepathy-gabble-0.18.3::gentoo
USE="-gnutls -jingle -plugins {-test}" 0 KiB
[nomerge ] kde-apps/kolourpaint-16.04.1:4/16.04::gentoo
USE="handbook scanner (-aqua) -debug"
[nomerge ]
Re: [gentoo-user] kde-apps/libksane blocker
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 ]
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
* 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
[gentoo-user] kde-apps/libksane blocker
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.
[ebuild U ~] kde-apps/kde-l10n-16.04.1:5::gentoo [15.12.3:5::gentoo]
USE="handbook -debug" LINGUAS="-ar -ast% -bg -bs -ca -ca@valencia -cs
-da -de -el -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -he -hi -hr -hu
-ia -id -is -it -ja -kk -km -ko -lt -lv -mr -nb -nds -nl -nn -pa -pl -pt
-pt_BR -ro -ru -sk -sl -sr -sv -tr -ug -uk -wa -zh_CN -zh_TW" 0 KiB
[ebuild U ~] kde-apps/kde4-l10n-16.04.1:4/16.04::gentoo
[15.12.3-r1:4/15.12::gentoo] USE="handbook minimal (-aqua) {-test%}"
LINGUAS="-ar -ast% -bg -bs -ca -ca@valencia -cs -da -de -el -en_GB -eo
-es -et -eu -fa -fi -fr -ga -gl -he -hi -hr -hu -ia -id -is -it -ja -kk
-km -ko -lt -lv -mr -nb -nds -nl -nn -pa -pl -pt -pt_BR -ro -ru -sk -sl
-sr -sv -tr -ug -uk -wa -zh_CN -zh_TW" 0 KiB
[blocks b ] =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)
I'm not so worried about the procps thing right now, although it keeps
popping up. The libksane one has me puzzled. Here is some info on the
packages that are in question:
root@fireball / # equery list -p ksaneplugin skanlite kolourpaint
kdegraphics-meta
* Searching for ksaneplugin ...
[-P-] [ ] kde-apps/ksaneplugin-4.14.3:4/4.14
[-P-] [ ] kde-apps/ksaneplugin-15.08.3:4/15.08
[IP-] [ ] kde-apps/ksaneplugin-15.12.3:4/15.12
[-P-] [ ] kde-apps/ksaneplugin-16.04.1:4/16.04
* Searching for skanlite ...
[IP-] [ ] kde-misc/skanlite-1.1-r1:4
[-P-] [ ] kde-misc/skanlite-2.0:5
* Searching for kolourpaint ...
[-P-] [ ] kde-apps/kolourpaint-4.14.3:4/4.14
[-P-] [ ] kde-apps/kolourpaint-15.08.3:4/15.08
[IP-] [ ] kde-apps/kolourpaint-15.12.3:4/15.12
[-P-] [ ] kde-apps/kolourpaint-16.04.1:4/16.04
* Searching for kdegraphics-meta in kde-apps ...
[-P-] [ ] kde-apps/kdegraphics-meta-4.14.3:4
[-P-] [ ~] kde-apps/kdegraphics-meta-15.08.3:5
[IP-] [ ] kde-apps/kdegraphics-meta-15.12.3:5
[-P-] [ ] kde-apps/kdegraphics-meta-16.04.1:5
root@fireball / #
As you can see, none of them are keyworded so it should be able to use
the latest packages. I just synced a hour or so ago so this may be more
up to date than you may have on your system. It's why I am including
the info here.
Is it possible I caught the tree in the middle of a update and I need to
sync again? Is my old eyes missing something obvious? Or, is it what I
think, a conflict that can't yet be solved because of a hard dependency?
Looking for thoughts, ideas, suggestions.
Dale
:-) :-)
