Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-15 Thread Dale
meino.cra...@gmx.de wrote:
 Dale rdalek1...@gmail.com [15-03-14 09:20]:
 meino.cra...@gmx.de wrote:
 Hi,

 emerge hits me:

 Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
 gives me this:

 emerge: there are no ebuilds to satisfy kde-base/solid:4.
 (dependency required by @preserved-rebuild [argument])

 emerge itself can be called without that error.
 How can an argument to a command haves a dependency?

 How can I get out of this?

 Best regards,
 mcc





 H. 

 root@fireball / # equery list -p solid
  * Searching for solid ...
 [-P-] [ ~] kde-frameworks/solid-5.7.0:5/5.7
 root@fireball / #  

 It seems there is no 4 versions.  Do you perhaps have a 4 version listed
 in your world file that sneaked in there somehow?  If so, removing that
 may allow a upgrade.  If not, interesting problem. 

 Dale

 :-)  :-) 

 Hi Dale,

 thank you for your reply ! :)

 ...there is no 4 version in the /var/lib/portage/world file.
 So it is an interesting problem...unfortunately: ..for me; ;)

 Is there a way to find the one, which pulls this solid 4 version?


 best regards,
 mcc



I think you have this fixed already but the only thing I can think of is
to add the -t option to emerge.  Sometimes that helps, sometimes it just
makes one scratch their head on the other side. 

Dale

:-)  :-)



Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Meino . Cramer
Dale rdalek1...@gmail.com [15-03-14 09:20]:
 meino.cra...@gmx.de wrote:
  Hi,
 
  emerge hits me:
 
  Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
  gives me this:
 
  emerge: there are no ebuilds to satisfy kde-base/solid:4.
  (dependency required by @preserved-rebuild [argument])
 
  emerge itself can be called without that error.
  How can an argument to a command haves a dependency?
 
  How can I get out of this?
 
  Best regards,
  mcc
 
 
 
 
 
 
 H. 
 
 root@fireball / # equery list -p solid
  * Searching for solid ...
 [-P-] [ ~] kde-frameworks/solid-5.7.0:5/5.7
 root@fireball / #  
 
 It seems there is no 4 versions.  Do you perhaps have a 4 version listed
 in your world file that sneaked in there somehow?  If so, removing that
 may allow a upgrade.  If not, interesting problem. 
 
 Dale
 
 :-)  :-) 
 

Hi Dale,

thank you for your reply ! :)

...there is no 4 version in the /var/lib/portage/world file.
So it is an interesting problem...unfortunately: ..for me; ;)

Is there a way to find the one, which pulls this solid 4 version?


best regards,
mcc






Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Dale
meino.cra...@gmx.de wrote:
 Hi,

 emerge hits me:

 Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
 gives me this:

 emerge: there are no ebuilds to satisfy kde-base/solid:4.
 (dependency required by @preserved-rebuild [argument])

 emerge itself can be called without that error.
 How can an argument to a command haves a dependency?

 How can I get out of this?

 Best regards,
 mcc






H. 

root@fireball / # equery list -p solid
 * Searching for solid ...
[-P-] [ ~] kde-frameworks/solid-5.7.0:5/5.7
root@fireball / #  

It seems there is no 4 versions.  Do you perhaps have a 4 version listed
in your world file that sneaked in there somehow?  If so, removing that
may allow a upgrade.  If not, interesting problem. 

Dale

:-)  :-) 



Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Meino . Cramer
Alan McKinnon alan.mckin...@gmail.com [15-03-14 09:48]:
 On 14/03/2015 09:36, meino.cra...@gmx.de wrote:
  Hi,
  
  emerge hits me:
  
  Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
  gives me this:
  
  emerge: there are no ebuilds to satisfy kde-base/solid:4.
  (dependency required by @preserved-rebuild [argument])
  
  emerge itself can be called without that error.
  How can an argument to a command haves a dependency?
  
  How can I get out of this?
 
 
 It's portage's insanely obtuse output that is getting you confused, but
 the error is with an ebuild, not portage.
 
 First, there is not such package as solid with SLOT=4:
 
 # eix -e solid
 * kde-frameworks/solid
  Available versions:  (5) (~)5.7.0(5/5.7)
{debug doc nls test}
  Homepage:http://www.kde.org/
  Description: Framework providing platform independent
 hardware discovery, abstraction, and management
 
 
 Then, all that dependency required by... output from portage is an
 effort to show you what is pulling a package in, and it starts at the
 beginning. Portage knows it's dealing with whatever is in the
 @preserved-rebuild set, and that set has packages in it. Each of those
 packages may have other deps, and so on.
 
 In your case, it seems to be solid-actions-kcm that's causing it
 
 # grep -r kde-base/solid:4 /var/portage/
 /var/portage/kde-base/solid-actions-kcm/solid-actions-kcm-4.11.14.ebuild:
  !kde-base/solid:4
 
 
 
 I have no idea if this will work, but here's what I'd do:
 
 skip @preserved-rebuild for now, and run
 revdep-rebuild
 emerge -a --depclean
 
 So if that changes things. Also make sure neither solid nor
 solid-actions-kcm are in world, they should be deps pulled in automatically.
 
 Also move /var/lib/portage/preserved_libs_registry out of the way if it
 has junk in it and let revdep-rebuild fix things.
 
 Finally, you did sync ran emerge world recently, right?
 
 
 
 
 
 
 
 -- 
 Alan McKinnon
 alan.mckin...@gmail.com
 
 

Hi Alan,

thanks for your reply ! :)

...interesting...one needs to use grep to resolve a problem of 
portage ;)


Things are going even more worst (correct English???...uh, sound like
german English...;;;))):

revdep-rebuild runs fine and found nothing to rebuild.
depclean stops its work and said:

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/kglobalaccel-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/krosspython-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * media-sound/kmidimon-0.7.5
 * 
 *   dev-qt/qtgui:4 pulled in by:
 * media-sound/drumstick-0.5.0
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * media-video/kaffeine-1.2.2-r1
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/solid-runtime-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/kactivities-4.13.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/kquitapp-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/ktouch-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * net-libs/libktorrent-1.3.1
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/renamedlg-plugins-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/keditbookmarks-4.14.3
 * 
 *   =dev-qt/qtgui-4.6.3:4 pulled in by:
 * dev-libs/libdbusmenu-qt-0.9.2
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/kwalletd-4.14.3-r1
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/plasma-runtime-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * media-plugins/kipi-plugins-4.4.0
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/kfile-4.14.3
 * 
 *   dev-qt/qtgui:4 pulled in by:
 * sys-kernel/kccmp-0.3
 * 
 *   ~dev-qt/qtgui-4.8.5[-aqua,-debug] pulled in by:
 * dev-qt/qtmultimedia-4.8.5
 * 
 *   ~dev-qt/qtgui-4.8.5[-aqua,-debug,-egl,qt3support] pulled in by:
 * dev-qt/qtopengl-4.8.5
 * 
 *   dev-qt/qtgui:4 pulled in by:
 * media-sound/qjackctl-0.3.10
 * 
 *   =dev-qt/qthelp-4.8.5:4 pulled in by:
 * dev-qt/qt-creator-2.8.1
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/katepart-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/khotkeys-4.11.14
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/knewstuff-4.14.3
 * 
 *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
 * kde-base/kdesu-4.14.3
 * 
 *   

Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Alan McKinnon
On 14/03/2015 09:36, meino.cra...@gmx.de wrote:
 Hi,
 
 emerge hits me:
 
 Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
 gives me this:
 
 emerge: there are no ebuilds to satisfy kde-base/solid:4.
 (dependency required by @preserved-rebuild [argument])
 
 emerge itself can be called without that error.
 How can an argument to a command haves a dependency?
 
 How can I get out of this?


It's portage's insanely obtuse output that is getting you confused, but
the error is with an ebuild, not portage.

First, there is not such package as solid with SLOT=4:

# eix -e solid
* kde-frameworks/solid
 Available versions:  (5) (~)5.7.0(5/5.7)
   {debug doc nls test}
 Homepage:http://www.kde.org/
 Description: Framework providing platform independent
hardware discovery, abstraction, and management


Then, all that dependency required by... output from portage is an
effort to show you what is pulling a package in, and it starts at the
beginning. Portage knows it's dealing with whatever is in the
@preserved-rebuild set, and that set has packages in it. Each of those
packages may have other deps, and so on.

In your case, it seems to be solid-actions-kcm that's causing it

# grep -r kde-base/solid:4 /var/portage/
/var/portage/kde-base/solid-actions-kcm/solid-actions-kcm-4.11.14.ebuild:
 !kde-base/solid:4



I have no idea if this will work, but here's what I'd do:

skip @preserved-rebuild for now, and run
revdep-rebuild
emerge -a --depclean

So if that changes things. Also make sure neither solid nor
solid-actions-kcm are in world, they should be deps pulled in automatically.

Also move /var/lib/portage/preserved_libs_registry out of the way if it
has junk in it and let revdep-rebuild fix things.

Finally, you did sync ran emerge world recently, right?







-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Alan McKinnon
On 14/03/2015 11:10, meino.cra...@gmx.de wrote:
 Alan McKinnon alan.mckin...@gmail.com [15-03-14 09:48]:
 On 14/03/2015 09:36, meino.cra...@gmx.de wrote:
 Hi,

 emerge hits me:

 Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
 gives me this:

 emerge: there are no ebuilds to satisfy kde-base/solid:4.
 (dependency required by @preserved-rebuild [argument])

 emerge itself can be called without that error.
 How can an argument to a command haves a dependency?

 How can I get out of this?


 It's portage's insanely obtuse output that is getting you confused, but
 the error is with an ebuild, not portage.

 First, there is not such package as solid with SLOT=4:

 # eix -e solid
 * kde-frameworks/solid
  Available versions:  (5) (~)5.7.0(5/5.7)
{debug doc nls test}
  Homepage:http://www.kde.org/
  Description: Framework providing platform independent
 hardware discovery, abstraction, and management


 Then, all that dependency required by... output from portage is an
 effort to show you what is pulling a package in, and it starts at the
 beginning. Portage knows it's dealing with whatever is in the
 @preserved-rebuild set, and that set has packages in it. Each of those
 packages may have other deps, and so on.

 In your case, it seems to be solid-actions-kcm that's causing it

 # grep -r kde-base/solid:4 /var/portage/
 /var/portage/kde-base/solid-actions-kcm/solid-actions-kcm-4.11.14.ebuild:
  !kde-base/solid:4



 I have no idea if this will work, but here's what I'd do:

 skip @preserved-rebuild for now, and run
 revdep-rebuild
 emerge -a --depclean

 So if that changes things. Also make sure neither solid nor
 solid-actions-kcm are in world, they should be deps pulled in automatically.

 Also move /var/lib/portage/preserved_libs_registry out of the way if it
 has junk in it and let revdep-rebuild fix things.

 Finally, you did sync ran emerge world recently, right?


 
 Hi Alan,
 
 thanks for your reply ! :)


No problem.

Huge amounts of portage output snipped below, but I think you are trying
to have stable Qt4 and unstable Qt5 on the same system. That doesn't
work currently, I'll walk through my reasoning so you can see what's
going on:

 
 ...interesting...one needs to use grep to resolve a problem of 
 portage ;)

Hah yes, that's quite funny.
I wanted to see what the ebuilds actually say, not what portage tools
think they say :-)


 
 
 Things are going even more worst (correct English???...uh, sound like
 german English...;;;))):
 
 revdep-rebuild runs fine and found nothing to rebuild.
 depclean stops its work and said:
 
 Calculating dependencies... done!
  * Dependencies could not be completely resolved due to
  * the following required packages not being installed:
  * 
  *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
  * kde-base/kglobalaccel-4.14.3

[... huge snip]

Basically, of this part really means that you need Qt:4
It *can* co-exist with Qt5, I have them both installed here.

 Since packages are missing I tried:
 emerge --update --newuse --deep --with-bdeps=y @world --tree --keep-going -v
 
 
 which prints:
 These are the packages that would be merged, in reverse order:
 
 Calculating dependencies... done!

[...snip...]

 [blocks B  ] dev-qt/qtgui-4.8.6:4 (dev-qt/qtgui-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtsql-4.8.6:4 (dev-qt/qtsql-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtcore-4.8.6:4 (dev-qt/qtcore-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qthelp-4.8.6:4 (dev-qt/qthelp-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtopengl-4.8.6:4 (dev-qt/qtopengl-4.8.6:4 is 
 blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qt3support-4.8.6:4 (dev-qt/qt3support-4.8.6:4 is 
 blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtsvg-4.8.6:4 (dev-qt/qtsvg-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtmultimedia-4.8.6:4 (dev-qt/qtmultimedia-4.8.6:4 
 is blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtdeclarative-4.8.6:4 
 (dev-qt/qtdeclarative-4.8.6:4 is blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/designer-4.8.6:4 (dev-qt/designer-4.8.6:4 is 
 blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qttest-4.8.6:4 (dev-qt/qttest-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtxmlpatterns-4.8.6:4 
 (dev-qt/qtxmlpatterns-4.8.6:4 is blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtwebkit-4.8.6:4 (dev-qt/qtwebkit-4.8.6:4 is 
 blocking dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtdbus-4.8.6:4 (dev-qt/qtdbus-4.8.6:4 is blocking 
 dev-qt/qtchooser-0_p20150102)
 [blocks B  ] dev-qt/qtscript-4.8.6:4 (dev-qt/qtscript-4.8.6:4 is 
 blocking dev-qt/qtchooser-0_p20150102)

[... snip big list of what wants Qt stuff]


Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Andreas K. Huettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Samstag, 14. März 2015, 08:36:16 schrieb meino.cra...@gmx.de:
 Hi,
 
 emerge hits me:
 
 Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
 gives me this:
 
 emerge: there are no ebuilds to satisfy kde-base/solid:4.
 (dependency required by @preserved-rebuild [argument])
 
 emerge itself can be called without that error.
 How can an argument to a command haves a dependency?
 
 How can I get out of this?
 
 Best regards,
 mcc

Seems like you haven't done a depclean for a veeery long time. Not good.

emerge --depclean --ask

the very very first thing to do...

- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0

iQJ8BAEBCgBmBQJVBCvBXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNzlCRDk4QzA4RENBRkYzQUEwRjQzMDlF
QkU2QTMzNkJFMTkwMzlDAAoJEOvmoza+GQOcKBYQALL/y9//W8D0sQAR5VZFhtlR
y8KkPvQsGtGBEcPx1JhsZsBYShYAU9khUGEIgYARhBMXLSPt8RsllUs7kMm0TTS+
fxyJ8fvS4J8Gp3tkzDtItIJZx539ODL//Ji12Ka7RJqxry3GIzo6BwnEzaycfuZz
XZ5rbYMWK6Kkmk7BcD2K0x3z8zBRlcqRcTKp69TuL32QbomSRazK/8Oac8utnPIY
h1AFtzMugxzin1NXjAD7kywOd4Icxa4N73hiKtPuwiv/n5FkxrbrRRVwaegbbPEI
KAunsaGDhF3YLVrZkNp8CKknp8Pa/Pzm5aw6lTRMinewZsAMkyTo8YajfO2ANRVx
KV7t1IyP9PASsof0ujv7SptXbzIkDYg7y1/css4vVIl58PldNKD/NwhHqOiKZZO2
86Phi8tPrJZTWTloc0bDccUKVqrChiTmpX1O83KR7jrZ7vWqvK3bbW8+ipye0tWp
fk/AqSP7DhfNrIH/SkBHQt8hCXRtAJvUF3nLJ0XXci6NVi8QxCC1nPCk/ewzMVLH
9+WXfIwg671Qa6J3x+R6WTmK3tsGyLYPY2W7CnK95BpeGNghtmbL2xnyoo060mmN
q06YVFMqK77deen12FT0VNa+G3dE8HWov2OScL4ImoKqEfpRnsqvyvWchPs9vC7t
sGgjJAuop5OtIC+9YhFQ
=ps4T
-END PGP SIGNATURE-



Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Meino . Cramer
Andreas K. Huettel dilfri...@gentoo.org [15-03-14 13:48]:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512
 
 Am Samstag, 14. März 2015, 08:36:16 schrieb meino.cra...@gmx.de:
  Hi,
  
  emerge hits me:
  
  Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
  gives me this:
  
  emerge: there are no ebuilds to satisfy kde-base/solid:4.
  (dependency required by @preserved-rebuild [argument])
  
  emerge itself can be called without that error.
  How can an argument to a command haves a dependency?
  
  How can I get out of this?
  
  Best regards,
  mcc
 
 Seems like you haven't done a depclean for a veeery long time. Not good.
 
 emerge --depclean --ask
 
 the very very first thing to do...
 
 - -- 
 
 Andreas K. Huettel
 Gentoo Linux developer 
 dilfri...@gentoo.org
 http://www.akhuettel.de/
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0
 
 iQJ8BAEBCgBmBQJVBCvBXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNzlCRDk4QzA4RENBRkYzQUEwRjQzMDlF
 QkU2QTMzNkJFMTkwMzlDAAoJEOvmoza+GQOcKBYQALL/y9//W8D0sQAR5VZFhtlR
 y8KkPvQsGtGBEcPx1JhsZsBYShYAU9khUGEIgYARhBMXLSPt8RsllUs7kMm0TTS+
 fxyJ8fvS4J8Gp3tkzDtItIJZx539ODL//Ji12Ka7RJqxry3GIzo6BwnEzaycfuZz
 XZ5rbYMWK6Kkmk7BcD2K0x3z8zBRlcqRcTKp69TuL32QbomSRazK/8Oac8utnPIY
 h1AFtzMugxzin1NXjAD7kywOd4Icxa4N73hiKtPuwiv/n5FkxrbrRRVwaegbbPEI
 KAunsaGDhF3YLVrZkNp8CKknp8Pa/Pzm5aw6lTRMinewZsAMkyTo8YajfO2ANRVx
 KV7t1IyP9PASsof0ujv7SptXbzIkDYg7y1/css4vVIl58PldNKD/NwhHqOiKZZO2
 86Phi8tPrJZTWTloc0bDccUKVqrChiTmpX1O83KR7jrZ7vWqvK3bbW8+ipye0tWp
 fk/AqSP7DhfNrIH/SkBHQt8hCXRtAJvUF3nLJ0XXci6NVi8QxCC1nPCk/ewzMVLH
 9+WXfIwg671Qa6J3x+R6WTmK3tsGyLYPY2W7CnK95BpeGNghtmbL2xnyoo060mmN
 q06YVFMqK77deen12FT0VNa+G3dE8HWov2OScL4ImoKqEfpRnsqvyvWchPs9vC7t
 sGgjJAuop5OtIC+9YhFQ
 =ps4T
 -END PGP SIGNATURE-
 

Yes I know. Thats why I doing it after every update ...

Best
mcc





Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Meino . Cramer
Alan McKinnon alan.mckin...@gmail.com [15-03-14 10:39]:
 On 14/03/2015 11:10, meino.cra...@gmx.de wrote:
  Alan McKinnon alan.mckin...@gmail.com [15-03-14 09:48]:
  On 14/03/2015 09:36, meino.cra...@gmx.de wrote:
  Hi,
 
  emerge hits me:
 
  Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
  gives me this:
 
  emerge: there are no ebuilds to satisfy kde-base/solid:4.
  (dependency required by @preserved-rebuild [argument])
 
  emerge itself can be called without that error.
  How can an argument to a command haves a dependency?
 
  How can I get out of this?
 
 
  It's portage's insanely obtuse output that is getting you confused, but
  the error is with an ebuild, not portage.
 
  First, there is not such package as solid with SLOT=4:
 
  # eix -e solid
  * kde-frameworks/solid
   Available versions:  (5) (~)5.7.0(5/5.7)
 {debug doc nls test}
   Homepage:http://www.kde.org/
   Description: Framework providing platform independent
  hardware discovery, abstraction, and management
 
 
  Then, all that dependency required by... output from portage is an
  effort to show you what is pulling a package in, and it starts at the
  beginning. Portage knows it's dealing with whatever is in the
  @preserved-rebuild set, and that set has packages in it. Each of those
  packages may have other deps, and so on.
 
  In your case, it seems to be solid-actions-kcm that's causing it
 
  # grep -r kde-base/solid:4 /var/portage/
  /var/portage/kde-base/solid-actions-kcm/solid-actions-kcm-4.11.14.ebuild:
   !kde-base/solid:4
 
 
 
  I have no idea if this will work, but here's what I'd do:
 
  skip @preserved-rebuild for now, and run
  revdep-rebuild
  emerge -a --depclean
 
  So if that changes things. Also make sure neither solid nor
  solid-actions-kcm are in world, they should be deps pulled in 
  automatically.
 
  Also move /var/lib/portage/preserved_libs_registry out of the way if it
  has junk in it and let revdep-rebuild fix things.
 
  Finally, you did sync ran emerge world recently, right?
 
 
  
  Hi Alan,
  
  thanks for your reply ! :)
 
 
 No problem.
 
 Huge amounts of portage output snipped below, but I think you are trying
 to have stable Qt4 and unstable Qt5 on the same system. That doesn't
 work currently, I'll walk through my reasoning so you can see what's
 going on:
 
  
  ...interesting...one needs to use grep to resolve a problem of 
  portage ;)
 
 Hah yes, that's quite funny.
 I wanted to see what the ebuilds actually say, not what portage tools
 think they say :-)
 
 
  
  
  Things are going even more worst (correct English???...uh, sound like
  german English...;;;))):
  
  revdep-rebuild runs fine and found nothing to rebuild.
  depclean stops its work and said:
  
  Calculating dependencies... done!
   * Dependencies could not be completely resolved due to
   * the following required packages not being installed:
   * 
   *   =dev-qt/qtgui-4.8.5:4[accessibility,dbus(+)] pulled in by:
   * kde-base/kglobalaccel-4.14.3
 
 [... huge snip]
 
 Basically, of this part really means that you need Qt:4
 It *can* co-exist with Qt5, I have them both installed here.
 
  Since packages are missing I tried:
  emerge --update --newuse --deep --with-bdeps=y @world --tree --keep-going -v
  
  
  which prints:
  These are the packages that would be merged, in reverse order:
  
  Calculating dependencies... done!
 
 [...snip...]
 
  [blocks B  ] dev-qt/qtgui-4.8.6:4 (dev-qt/qtgui-4.8.6:4 is blocking 
  dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtsql-4.8.6:4 (dev-qt/qtsql-4.8.6:4 is blocking 
  dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtcore-4.8.6:4 (dev-qt/qtcore-4.8.6:4 is 
  blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qthelp-4.8.6:4 (dev-qt/qthelp-4.8.6:4 is 
  blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtopengl-4.8.6:4 (dev-qt/qtopengl-4.8.6:4 is 
  blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qt3support-4.8.6:4 (dev-qt/qt3support-4.8.6:4 
  is blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtsvg-4.8.6:4 (dev-qt/qtsvg-4.8.6:4 is blocking 
  dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtmultimedia-4.8.6:4 
  (dev-qt/qtmultimedia-4.8.6:4 is blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtdeclarative-4.8.6:4 
  (dev-qt/qtdeclarative-4.8.6:4 is blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/designer-4.8.6:4 (dev-qt/designer-4.8.6:4 is 
  blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qttest-4.8.6:4 (dev-qt/qttest-4.8.6:4 is 
  blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtxmlpatterns-4.8.6:4 
  (dev-qt/qtxmlpatterns-4.8.6:4 is blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtwebkit-4.8.6:4 (dev-qt/qtwebkit-4.8.6:4 is 
  blocking dev-qt/qtchooser-0_p20150102)
  [blocks B  ] dev-qt/qtdbus-4.8.6:4 (dev-qt/qtdbus-4.8.6:4 is 
  

Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Alan McKinnon
On 14/03/2015 14:50, meino.cra...@gmx.de wrote:
 Hi Alan,
 
 ...finally... :)
 
 I found the one application, which creates all this mess:
 media-sound/sonic-visualiser
 
 I removed that one (emerge -C) and everything works.
 It seems, that that package is in conflict with the 'rest of the
 world' ;)


It all starts to make sense now.

sonic-visualiser has a hard dependency on Qt5

-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] cannot emerge @preserved-rebuild due to removed package...

2015-03-14 Thread Andreas K. Huettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Samstag, 14. März 2015, 13:51:03 schrieb meino.cra...@gmx.de:
 Andreas K. Huettel dilfri...@gentoo.org [15-03-14 13:48]:
  Am Samstag, 14. März 2015, 08:36:16 schrieb meino.cra...@gmx.de:
   Hi,
   
   emerge hits me:
   
   Whiletrying to reolve a lot of blockers, emerge @preserved-rebuild
   gives me this:
   
   emerge: there are no ebuilds to satisfy kde-base/solid:4.
   (dependency required by @preserved-rebuild [argument])
  
  Seems like you haven't done a depclean for a veeery long time. Not good.
  
  emerge --depclean --ask
  
  the very very first thing to do...
  
 
 Yes I know. Thats why I doing it after every update ...
 

Sure? Because there was a kde-base/solid package long ago...

The preserved-rebuild output indicates that it's still on your system, and 
that preserved-rebuild needs to rebuild it... However, the ebuild and the 
package itself are long gone from the tree, so portage doesnt know how to 
rebuild it.  [It's been so long, I dont know what exactly replaced it 
anymore.]

Maybe you have some self-made or overlay ebuilds that depend on kde-
base/solid? This would be a reason why it hasnt been removed on depclean... 

- -- 

Andreas K. Huettel
Gentoo Linux developer 
dilfri...@gentoo.org
http://www.akhuettel.de/

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0

iQJ8BAEBCgBmBQJVBDG4XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNzlCRDk4QzA4RENBRkYzQUEwRjQzMDlF
QkU2QTMzNkJFMTkwMzlDAAoJEOvmoza+GQOctpsP/2kcy1dWlu4Uxc4Dbpb65/Vj
9qfAjl9NsaWlgLk/aPJGV4ozKyO7pgqXKj/BBO+g0wtK9/RtKS2GJ32HVli0YVzO
T9fAHbdUi5qUCRZqfYO7/STZM8GpwOJz34/F1bqf/lRtqlXz+f6+qCCaDLbwlEeQ
tIZW3kxjufCvCeMOWpkZilIZ3KgaoqTVp5CLFDO0iUgDefXaQ49vTE6WYv7gEK11
UefEia19603gZDemDcK5bEOBTfPqn+bucnD/is+Blke8JSxKYotiSMamdRsj6QAq
aAFsZJjg7nRYvuUx8g9E/uceVPsjtOWzjI83jhfS0vQkCGWp5CANmLACXEKPxkX5
VZ+8bXOvHunMk3hXhY6C4FeoNIL0HLm96vYRyNec3lv+bHGbZ6pwxno00UrR/+IB
CprkAbI0paj6pgy2Xs5ruCyKFC+9YbngOjHahnMTcMUcHKOUOxLI526fI/kXXA3s
u8l6v9idvvsyHbuuLzTCAxHPN8nhKjUKoFBm1Ga0Ojsaprad64ETA5jJzvu8cBdt
SChd11wnj55alkMSd66YxJxuqWxQkMh/HB+HSmt4w/R50ZMhoapda+PmDkHdDZi1
TEiwbdi1sqMZzBx5rx2UxLE2I89J6bc3kkpIir3DGtuNJDi2m3svVQmvjlZLzXyR
tIMhnl0soHlBmJUEHI8P
=ENta
-END PGP SIGNATURE-