Re: [gentoo-user] kde-4.1 SLOT in kdesvn-portage
Am Montag 22 September 2008 03:42:39 schrieb ext Jerry McBride: Hmmm maybe you guys would know I've gone the same route as you. However, I've emerge 4.1.65. It compiles fine, installs, no problems. And you don't wonder why 4.1.65 follows 4.1.1? That's 4.2-(pre?)-alpha! The next 4.1 release will be 4.1.2. Does anyone have a suggestion? Don't use alpha software. Now running 3.5.10 with no problems. But I'd really, really like to get a current kde up and running. Do as suggested earlier in this thread: Use the kde-testing overlay. Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Wanheimerstraße 68 | Web: http://www.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net signature.asc Description: This is a digitally signed message part.
[gentoo-user] kde-4.1 SLOT in kdesvn-portage
Hi, I use the kdesvn-portage overlay (the portage one, not the paludis-only one). To still stay this side of sanity, I emerged the 4.1.1 SLOT. I updated layman -S today only to find that the entire kde-4.1 SLOT has been removed. Can someone confirm? Am I actually dreaming? Anyone know why a perfectly reasonable set of ebuilds were removed? -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kde-4.1 SLOT in kdesvn-portage
Alan McKinnon wrote: Hi, I use the kdesvn-portage overlay (the portage one, not the paludis-only one). To still stay this side of sanity, I emerged the 4.1.1 SLOT. I updated layman -S today only to find that the entire kde-4.1 SLOT has been removed. Can someone confirm? Am I actually dreaming? Anyone know why a perfectly reasonable set of ebuilds were removed? I have a similar problem when I 'emerge --sync' it deletes my overlays I added with layman. Mike
Re: [gentoo-user] kde-4.1 SLOT in kdesvn-portage
Mike wrote: Alan McKinnon wrote: Hi, I use the kdesvn-portage overlay (the portage one, not the paludis-only one). To still stay this side of sanity, I emerged the 4.1.1 SLOT. I updated layman -S today only to find that the entire kde-4.1 SLOT has been removed. Can someone confirm? Am I actually dreaming? Anyone know why a perfectly reasonable set of ebuilds were removed? I have a similar problem when I 'emerge --sync' it deletes my overlays I added with layman. Mike My problem was I symlinked /usr/local to /usr so layman was installing the overlays to /usr/portage instead of /usr/local/portage and they were getting deleted on 'emerge --sync'. I changed the layman installation directory in /etc/layman/layman.cfg and solved that problem. Mike
Re: [gentoo-user] kde-4.1 SLOT in kdesvn-portage
On Sunday 21 September 2008 09:26:15 pm Mike wrote: Mike wrote: Alan McKinnon wrote: Hi, I use the kdesvn-portage overlay (the portage one, not the paludis-only one). To still stay this side of sanity, I emerged the 4.1.1 SLOT. I updated layman -S today only to find that the entire kde-4.1 SLOT has been removed. Can someone confirm? Am I actually dreaming? Anyone know why a perfectly reasonable set of ebuilds were removed? I have a similar problem when I 'emerge --sync' it deletes my overlays I added with layman. Mike My problem was I symlinked /usr/local to /usr so layman was installing the overlays to /usr/portage instead of /usr/local/portage and they were getting deleted on 'emerge --sync'. I changed the layman installation directory in /etc/layman/layman.cfg and solved that problem. Mike Hmmm maybe you guys would know I've gone the same route as you. However, I've emerge 4.1.65. It compiles fine, installs, no problems. However... I normally start my gentoobox as rc 3. When I run startx, kde loads and looks quite wonderful, but just as the desktop grabs the mouse... it locks up. The lockup is so complete, I can't switch to a console and have to reboot... Does anyone have a suggestion? Kde 4,0 actually worked ok. kde4.05 and greater have been a wash for me. No luck what so ever. Total and complete lockup. Things I've done: tried 4.1, tried 4.1.66, made sure evdev is loaded... the logs show that X dies immediately... no output... just bang... Now running 3.5.10 with no problems. But I'd really, really like to get a current kde up and running. Jerry