Re: [gentoo-user] Problem with emerge --update
Thank you Alan. Just as an information, if it happens to something else: I've installed successfully the split ebuilds. However, after the upgrade, I had to disable UXA: with UXA Xorg didn't even start (it crashes). However (as glxgears says), FPS jumped from 500 to 1300... Thank you all, Massimiliano
Re: [gentoo-user] Problem with emerge --update
On Tuesday 30 June 2009 23:17:02 Massimiliano Ziccardi wrote: It's far preferable to let people like yourself suffer the consequences of not reading documentation Touched :-) However, I read the documentation. It's just that this is my first gentoo installation: I didn't get I had to uninstall the older version of the software to upgrade to the new one. You get to learn those tricks as you go along. Normally, one just upgrades and portage takes care of the install old one, install new one step. But KDE split and monolithic ebuilds covering the same KDE package are different in this regard - they are incompatible and cannot co-exist on the same machine. Especially when it says 'We still provide monolithic ebuilds for 3.5 (up till 3.5.9) and they are ***cleanly interoperable*** with the split ones.' That's a strange statement for the document to make. Split and monolithic can interoperate as long as you keep them cleanly separated. Take an example - kdepim and kdegames. Both have full monolithic and split ebuilds. You might decide you do indeed want all of kdepim [1] but not all the games. So you could emerge kdepim and selectively pick the few split-ebuild games you do want. What you can't do is also try to emerge kmail - that clashes with the kmail that kdepim wants to put there. [1] Here you would actually use kdepim-meta in the real world (it pulls in all the kdepim split ebuilds), but this is a demonstration, not a list of accurate install instructions. However, I think now I understand how it works a little bit more (but not too much ;-) ). One more thing: couldn't those 'stable users' read the documentation too, and unmask the obsolete package (if they were masked)? Think about this. You are asking users who have been doing something one way for years, to all of a sudden have their packages masked, their systems broken, expect them to go and find documentation (the location of which is not easy to provide at that time), unmask stuff and continue. Why? And for what benefit? The way it is done is the best possible way for all the users. Existing users continue as they did, new users get to make a choice first (which is something they have to do anyway). Massimiliano -- alan dot mckinnon at gmail dot com
[gentoo-user] Problem with emerge --update
Hi all!! I tried today : emerge --update --deep world but I get the following error: [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) I'm not very expert about emerge, have you any idea about this error? Can I solve it in some way? (Please, don't ask me to uninstall kdebase :-) ) Thank you, Massimiliano
Re: [gentoo-user] Problem with emerge --update
Massimiliano Ziccardi wrote: Hi all!! I tried today : emerge --update --deep world but I get the following error: [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) I'm not very expert about emerge, have you any idea about this error? Can I solve it in some way? (Please, don't ask me to uninstall kdebase :-) ) Thank you, Massimiliano The monolithic packages are obsolete - please switch to split packages: http://www.gentoo.org/proj/en/desktop/kde/kde-split-ebuilds.xml AllenJB
Re: [gentoo-user] Problem with emerge --update
On Dienstag 30 Juni 2009, Massimiliano Ziccardi wrote: Hi all!! I tried today : emerge --update --deep world but I get the following error: [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) I'm not very expert about emerge, have you any idea about this error? Can I solve it in some way? (Please, don't ask me to uninstall kdebase :-) ) Thank you, Massimiliano yes, it is related to the fact that monolithic ebuilds are phased out. Search the archive, you will find a lot about it. Also looking into the kde guide on gentoo.org might help you.
Re: [gentoo-user] Problem with emerge --update
Massimiliano Ziccardi writes: emerge --update --deep world but I get the following error: [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) I'm not very expert about emerge, have you any idea about this error? Can I solve it in some way? (Please, don't ask me to uninstall kdebase Maybe this large thread gives some insights. http://www.mail-archive.com/gentoo-am...@lists.gentoo.org/msg11168.html Wonko
Re: [gentoo-user] Problem with emerge --update
On Tuesday 30 June 2009 14:40:20 Massimiliano Ziccardi wrote: Hi all!! I tried today : emerge --update --deep world but I get the following error: [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) I'm not very expert about emerge, have you any idea about this error? Can I solve it in some way? (Please, don't ask me to uninstall kdebase :-) ) You cannot install kdelibs and kdebase simultaneously. One is a monolithic package, the other is a split ebuilf. There is an article on the doc site about this, search for KDE split ebuild guide. And you MUST uninstall kdebase to use kde-3.5.10. Monolithic ebuilds are not supported for 3.5.10. Or you could stick with 3.5.9 and mask 3.5.10 -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Problem with emerge --update
I'm installing the split ebuild ( Very long operation.. x-/ ). Wouldn't be better to mask the kdebase monolithic ebuild, so that unexperienced gentoo linux users as I am would not spend useless hours installing it? Thanks again for your prompt help, Massimiliano On Tue, Jun 30, 2009 at 3:22 PM, Alex Schuster wo...@wonkology.org wrote: Massimiliano Ziccardi writes: emerge --update --deep world but I get the following error: [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) I'm not very expert about emerge, have you any idea about this error? Can I solve it in some way? (Please, don't ask me to uninstall kdebase Maybe this large thread gives some insights. http://www.mail-archive.com/gentoo-am...@lists.gentoo.org/msg11168.html Wonko
Re: [gentoo-user] Problem with emerge --update
On Tuesday 30 June 2009 17:41:35 Massimiliano Ziccardi wrote: I'm installing the split ebuild ( Very long operation.. x-/ ). Wouldn't be better to mask the kdebase monolithic ebuild, so that unexperienced gentoo linux users as I am would not spend useless hours installing it? No. That's a bad idea. Stable users have been using monolithic ebuilds for ages. You can't just take that away from them. It's far preferable to let people like yourself suffer the consequences of not reading documentation - split ebuilds have been available and documented since at around 2006 IIRC -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Problem with emerge --update
It's far preferable to let people like yourself suffer the consequences of not reading documentation Touched :-) However, I read the documentation. It's just that this is my first gentoo installation: I didn't get I had to uninstall the older version of the software to upgrade to the new one. Especially when it says 'We still provide monolithic ebuilds for 3.5 (up till 3.5.9) and they are ***cleanly interoperable*** with the split ones.' However, I think now I understand how it works a little bit more (but not too much ;-) ). One more thing: couldn't those 'stable users' read the documentation too, and unmask the obsolete package (if they were masked)? Massimiliano
[gentoo-user] Problem after emerge --update --deep world
Hi all, This issue is related to my desktop. Bear with me while I give some background details. A couple of months ago, I followed the MySQL Upgrade Guide to upgrade MySQL. At that time, some configuration files were changed. I don't know specifically if those changes had anything to do with a problem that developed. The problem was that when I logged out of KDE and chose to either restart or shutdown the computer, neither of these occurred. The monitor would shut off, but not the computer. A week or so ago, I did the gcc upgrade using the GCC Upgrade Guide and much to my pleasure, the problem of not being able to reboot or shutdown when I selected those choices from the menu on KDE logout disappeared. On Sunday, I started an 'emerge --update --deep world'. A number of kde 3.4.3 packages were pulled in (I orginally emerged kde-meta). The update went fine. At the end, I ran etc-update and 4 configuration files related to kde were updated. The files were: klipperrc, ksslcalist, kdmrc, and libkleopatrarc. Now, after the update, I again cannot reboot or shutdown when I select either of the choices from the menu on KDE logout. I figured that kdmrc, might be a logical file to be causing the problem and I *did* find a Shutdown section in this file with the lines related to shutdown and reboot commented out. I removed the '#' and used the suggested defaults - /sbin/halt and /sbin/reboot. Well, this didn't solve the problem, so I tried editing the related lines to /etc/init.d/shutdown.sh and /etc/init.d/reboot.sh. This didn't solve the problem either. So, in a nutshell, I still cannot shutdown or reboot when I select these from the menu on KDE logout. Any ideas here? Regards, Colleen -- gentoo-user@gentoo.org mailing list
