Alan McKinnon wrote: > > > > 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 > >
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 :-) :-)
