Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
On Wednesday 25 October 2000 22:35, you wrote: > > Gerald Williams wrote: > > On Wednesday 25 October 2000 10:39, you wrote: > > > > Gerald Williams wrote: > > > > > > > > On Wednesday 25 October 2000 06:51, you wrote: > > > > > > Thanks. It still also resides in SOME (very few) kde mirrors. > > > > > > > > > > Here's the big question...did you actually install it and get it > > > > > working? > > > > > > > > I did, and it works okay > > [...] > > > > > While you do need to update a few, again, a few files, it's not a > > > > major problem. You do NOT need the latest glibc from cooker or the > > > > latest gcc2.96 compiler. FUD does not help. Nuff said. > > > > > > Not fud, it is a factual description of what is happening with my > > > system. > > > > If you had said the above, the first time, I probably would not have > > replied. It is screwed up on your system--ok, but don't go on about it > > being totally broken. Try upgrading your qt to the correct version and > > try again. If you want to continue, take it off list. > > My qt IS updated. The latest qt2 packages were the first I upgraded > since KDE is absolutely dependent upon it. > > Few questions. What version of libstdc++ do you have? What > version of menu? What version of rpm? libstdc++-2.95.2-7mdk menu-2.1.5-42mdk rpm-3.0.5-25mdk glibc-2.1.3-15mdk pam-0.72-12mdk qt2-2.2.1-1mdk > I believe these packages are the only logical possible problems, > at least in my case. During rpm install of most of the KDE > packages and the install of qt2, my /usr/bin/update-menus > crashes/core dumps. This binary is supplied by menu. Menu > requires the appropriate libstdc++ (I believe). It also, > obviously, ties into the rpm install process. > > I am HOPING it is merely something simple like libstdc++, > that all I need to do is install the proper version. During > an attempt to build qt2 source several days ago, the build > would fail because the configure script couldn't find > libstdc++. Bizarre, because libstdc++ is right there in > /usr/lib, which is in my /etc/ld.so.conf file, and I have > run ldconfig in an attempt to make sure it is "known" about. > > praedor I believe there is a newer qt build than the one I have installed, and my system is really a hybrid of Mandrake 7.1, 7.2, and cooker. I switched over from 1.1.2 completely at the 1.93 beta because I wanted to use Koffice. I also completely deleted all of kde1.1.2 before installing the new files in /usr. I've had a problem with no sound and a problem with Wordperfect Office 2000 not working. I'm still trying to sort out the wpo problem. I should add I'm running the 2.2.17 kernel and xfree86 4.01. I'm sure your problem is something simple...most problems are when you finally figure them out. Jerry -- Gerald Williams -- Words Matter! Bangkok, Thailand Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
RE: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Did you delete your .kde directory, or at least the config directory within it ?? I deleted my .kde directory and then kde2rc2 came right up and functioned correctly. -Original Message- From: Praedor Tempus [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 25, 2000 12:40 PM To: [EMAIL PROTECTED] Subject: Re: [expert] Nice. Kill off kde STABLE 2.0 immediately "Ron Johnson, Jr." wrote: [...] > > You could try. When I did the attempt, the indications were that > > it would REPLACE your kde-1.1.2. In my experience, it did replace > > everything except kdebase-1.1.2. EVERYTHING else was replaced. > > > > This led to a double kdebase which was real screwy. I uninstalled > > the kdebase-1.1.2 manually and reinstalled kde 2.0. It worked > > I'm confused. Isn't EVERYTHING *supposed* to be replaced? When I did the install, I had kde-1.1.2 installed. After the installation, kde and kdm were REAL squirrelly. Kdm would let me start kde but nothing else. The panel in kde was blank and nothing in the menus worked. During my troubleshooting, I did an "rpm -qa | grep kde" and found that ALL the kde-1.1.2 rpms had been replaced except for kdebase-1.1.2. In that one instance, I had both kdebase-1.1.2 AND kdebase-2.0-1 installed. Oops. I manually removed the kdebase-1.1.2 rpm and reinstalled kde-2.0 (all rpms) again. This time, kdm was better behaved, though it wouldn't start "failsafe". Kde was better, with proper icons, though the panel was, again, nearly useless. About half the items I tried in the kde menus did not work. That was my experience. The ONE kdebase-1.1.2 rpm did not get replaced when I did it. I had to remove it myself. As a result of this, I suggest that it would be better to FIRST remove ALL the kde-1.1.2 rpms and then install all the kde-2.0 rpms rather than depend upon them to properly replace your old kde rpms. As for the other problems I've had, I am still trouble- shooting. Hopefully, by the end of the day I will have it fixed and running. I really don't care for gnome very much. praedor [...] > > Give it a shot and let me know... I am always wondering if there > > is some small squirrelly thing wrong with my system. > > praedor > > What do u mean: nearly useless. > > Ron > -- > +--+ > | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | > | Jefferson, LA USA WWW : [EMAIL PROTECTED] | > | http://ronandheather.dhs.org | > +--+ > > > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list. Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
RE: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
According to the KDE developers, it is suggested that you de-install kde 1.1.x, and then install kde2. Or so they told me over the weekend! -Original Message- From: Ron Johnson, Jr. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 25, 2000 11:49 AM To: [EMAIL PROTECTED] Subject: Re: [expert] Nice. Kill off kde STABLE 2.0 immediately Praedor Tempus wrote: > > "Ron Johnson, Jr." wrote: > > > > What if we trailing-edge types totally deinstall our 1.1.x > > systems, then try to install kde2 from source? > > > > You could try. When I did the attempt, the indications were that > it would REPLACE your kde-1.1.2. In my experience, it did replace > everything except kdebase-1.1.2. EVERYTHING else was replaced. > > This led to a double kdebase which was real screwy. I uninstalled > the kdebase-1.1.2 manually and reinstalled kde 2.0. It worked I'm confused. Isn't EVERYTHING *supposed* to be replaced? > better, such as that goes, but it was nearly useless. It just looked > a little better at being useless. > > Give it a shot and let me know... I am always wondering if there > is some small squirrelly thing wrong with my system. > praedor What do u mean: nearly useless. Ron -- +--+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA WWW : [EMAIL PROTECTED] | | http://ronandheather.dhs.org | +--+ Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
RE: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
I installed the tar files for rc2, and all is fine. If I recall, I also installed (rpm -i) qt-2.2.1. For some reason the -Uvh didn't work for qt2. -Original Message- From: Praedor Tempus [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 25, 2000 11:36 AM To: [EMAIL PROTECTED] Subject: Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately Gerald Williams wrote: > > On Wednesday 25 October 2000 10:39, you wrote: > > > > Gerald Williams wrote: > > > On Wednesday 25 October 2000 06:51, you wrote: > > > > > Thanks. It still also resides in SOME (very few) kde mirrors. > > > > > > > > Here's the big question...did you actually install it and get it > > > > working? > > > > > > I did, and it works okay [...] > > > While you do need to update a few, again, a few files, it's not a major > > > problem. You do NOT need the latest glibc from cooker or the latest > > > gcc2.96 compiler. FUD does not help. Nuff said. > > > > Not fud, it is a factual description of what is happening with my > > system. > > If you had said the above, the first time, I probably would not have > replied. It is screwed up on your system--ok, but don't go on about it > being totally broken. Try upgrading your qt to the correct version and try > again. If you want to continue, take it off list. My qt IS updated. The latest qt2 packages were the first I upgraded since KDE is absolutely dependent upon it. Few questions. What version of libstdc++ do you have? What version of menu? What version of rpm? I believe these packages are the only logical possible problems, at least in my case. During rpm install of most of the KDE packages and the install of qt2, my /usr/bin/update-menus crashes/core dumps. This binary is supplied by menu. Menu requires the appropriate libstdc++ (I believe). It also, obviously, ties into the rpm install process. I am HOPING it is merely something simple like libstdc++, that all I need to do is install the proper version. During an attempt to build qt2 source several days ago, the build would fail because the configure script couldn't find libstdc++. Bizarre, because libstdc++ is right there in /usr/lib, which is in my /etc/ld.so.conf file, and I have run ldconfig in an attempt to make sure it is "known" about. praedor Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
"Ron Johnson, Jr." wrote: [...] > > You could try. When I did the attempt, the indications were that > > it would REPLACE your kde-1.1.2. In my experience, it did replace > > everything except kdebase-1.1.2. EVERYTHING else was replaced. > > > > This led to a double kdebase which was real screwy. I uninstalled > > the kdebase-1.1.2 manually and reinstalled kde 2.0. It worked > > I'm confused. Isn't EVERYTHING *supposed* to be replaced? When I did the install, I had kde-1.1.2 installed. After the installation, kde and kdm were REAL squirrelly. Kdm would let me start kde but nothing else. The panel in kde was blank and nothing in the menus worked. During my troubleshooting, I did an "rpm -qa | grep kde" and found that ALL the kde-1.1.2 rpms had been replaced except for kdebase-1.1.2. In that one instance, I had both kdebase-1.1.2 AND kdebase-2.0-1 installed. Oops. I manually removed the kdebase-1.1.2 rpm and reinstalled kde-2.0 (all rpms) again. This time, kdm was better behaved, though it wouldn't start "failsafe". Kde was better, with proper icons, though the panel was, again, nearly useless. About half the items I tried in the kde menus did not work. That was my experience. The ONE kdebase-1.1.2 rpm did not get replaced when I did it. I had to remove it myself. As a result of this, I suggest that it would be better to FIRST remove ALL the kde-1.1.2 rpms and then install all the kde-2.0 rpms rather than depend upon them to properly replace your old kde rpms. As for the other problems I've had, I am still trouble- shooting. Hopefully, by the end of the day I will have it fixed and running. I really don't care for gnome very much. praedor [...] > > Give it a shot and let me know... I am always wondering if there > > is some small squirrelly thing wrong with my system. > > praedor > > What do u mean: nearly useless. > > Ron > -- > +--+ > | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | > | Jefferson, LA USA WWW : [EMAIL PROTECTED] | > | http://ronandheather.dhs.org | > +--+ > > > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list. Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Praedor Tempus wrote: > > "Ron Johnson, Jr." wrote: > > > > What if we trailing-edge types totally deinstall our 1.1.x > > systems, then try to install kde2 from source? > > > > You could try. When I did the attempt, the indications were that > it would REPLACE your kde-1.1.2. In my experience, it did replace > everything except kdebase-1.1.2. EVERYTHING else was replaced. > > This led to a double kdebase which was real screwy. I uninstalled > the kdebase-1.1.2 manually and reinstalled kde 2.0. It worked I'm confused. Isn't EVERYTHING *supposed* to be replaced? > better, such as that goes, but it was nearly useless. It just looked > a little better at being useless. > > Give it a shot and let me know... I am always wondering if there > is some small squirrelly thing wrong with my system. > praedor What do u mean: nearly useless. Ron -- +--+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA WWW : [EMAIL PROTECTED] | | http://ronandheather.dhs.org | +--+ Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Gerald Williams wrote: > > On Wednesday 25 October 2000 10:39, you wrote: > > > > Gerald Williams wrote: > > > On Wednesday 25 October 2000 06:51, you wrote: > > > > > Thanks. It still also resides in SOME (very few) kde mirrors. > > > > > > > > Here's the big question...did you actually install it and get it > > > > working? > > > > > > I did, and it works okay [...] > > > While you do need to update a few, again, a few files, it's not a major > > > problem. You do NOT need the latest glibc from cooker or the latest > > > gcc2.96 compiler. FUD does not help. Nuff said. > > > > Not fud, it is a factual description of what is happening with my > > system. > > If you had said the above, the first time, I probably would not have > replied. It is screwed up on your system--ok, but don't go on about it > being totally broken. Try upgrading your qt to the correct version and try > again. If you want to continue, take it off list. My qt IS updated. The latest qt2 packages were the first I upgraded since KDE is absolutely dependent upon it. Few questions. What version of libstdc++ do you have? What version of menu? What version of rpm? I believe these packages are the only logical possible problems, at least in my case. During rpm install of most of the KDE packages and the install of qt2, my /usr/bin/update-menus crashes/core dumps. This binary is supplied by menu. Menu requires the appropriate libstdc++ (I believe). It also, obviously, ties into the rpm install process. I am HOPING it is merely something simple like libstdc++, that all I need to do is install the proper version. During an attempt to build qt2 source several days ago, the build would fail because the configure script couldn't find libstdc++. Bizarre, because libstdc++ is right there in /usr/lib, which is in my /etc/ld.so.conf file, and I have run ldconfig in an attempt to make sure it is "known" about. praedor Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Praedor Tempus wrote: > > For further evidence, there is the FACT that all but one or two sites > have > removed the rpms for kde 2.0 from them. That is a stone-cold, > undeniable fact. > There is no FUD here, only objective description of what I see. It > matches > what some others have indicated themselves in this mailing list. It > also matches > well with what you can find in newsgroups. > > Cooker, as of this evening (and last I checked) no longer carries > kde-2.0 rpms. > Mandrake 7.2beta doesn't carry them. sunsite.uio.no, the primary Mandrake mirror, certainly at this very moment carries KDE 2.0 in their 7.2beta tree. Further, kdegraphics, kdegraphics-devel, qt2, qt2-doc, and qt2-devel have just been updated with new Mandrake patch levels. -- Regards, Ron. [AU] Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
On Wednesday 25 October 2000 10:39, you wrote: > > Gerald Williams wrote: > > On Wednesday 25 October 2000 06:51, you wrote: > > > > Thanks. It still also resides in SOME (very few) kde mirrors. > > > > > > Here's the big question...did you actually install it and get it > > > working? > > > > I did, and it works okay > > > > > After downloading and installing, all was wrong with the world. > > > First, installing it, even with menu-3.0.5-43mdk installed, it > > > segfaults during the rpm install on /usr/bin/upgrade-menus. Both qt2 > > > and kde rpms segfault > > > it. Once it IS all installed, the systqt2installerror.txtem is > > > broken. SOME things work, most > > > do not. > > > > While you do need to update a few, again, a few files, it's not a major > > problem. You do NOT need the latest glibc from cooker or the latest > > gcc2.96 compiler. FUD does not help. Nuff said. > > Not fud, it is a factual description of what is happening with my > system. If you had said the above, the first time, I probably would not have replied. It is screwed up on your system--ok, but don't go on about it being totally broken. Try upgrading your qt to the correct version and try again. If you want to continue, take it off list. Jerry -- Gerald Williams -- Words Matter! Bangkok, Thailand Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Gerald Williams wrote: > > On Wednesday 25 October 2000 06:51, you wrote: > > > > Thanks. It still also resides in SOME (very few) kde mirrors. > > > > Here's the big question...did you actually install it and get it > > working? > > I did, and it works okay > > > After downloading and installing, all was wrong with the world. First, > > installing it, even with menu-3.0.5-43mdk installed, it segfaults during > > the rpm install on /usr/bin/upgrade-menus. Both qt2 and kde rpms > > segfault > > it. Once it IS all installed, the systqt2installerror.txtem is broken. SOME >things work, > > most > > do not. > > While you do need to update a few, again, a few files, it's not a major > problem. You do NOT need the latest glibc from cooker or the latest gcc2.96 > compiler. FUD does not help. Nuff said. Not fud, it is a factual description of what is happening with my system. As for gcc, you do not NEED to have gcc but then, you will not be doing any compiling if you don't have it. I have a fully updated 7.1 system. I have menu-2.1.5-43mdk installed. That is as high as I can go without upgrading glibc to 2.1.95 (or higher). The problem? OK, installing qt2, the updated one that is required for kde 2.0 results in this: qt2 ## var/tmp/rpm-tmp.59425: line 2: 14222 Segmentation fault (core dumped) /usr/bin/update-menus qt2-devel ## var/tmp/rpm-tmp.93066: line 1: 14224 Segmentation fault (core dumped) /usr/bin/update-menus This problem is with menu. If menu-2.1.5-36mdk is not ok, and menu-2.1.5-43mdk is not ok, and menu-2.1.5-43mdk is not ok (I have gone thru each and every one of them trying to fix THIS particular problem), then that leaves one more possibility... menu-4.0. Menu-4.0 REQUIRES glibc-2.1.95. Glibc-2.1.95 WILL screw up your system UNLESS you are already running 7.2beta or Cooker. Neither of these is a logical nor reasonable system to run if you want ANY reliability. They are betas and even alphas for a reason. They are NOT finished products. They DO have problems yet to be worked out. I get the above errors also installing most of the kde 2.0 rpms. The resulting kde setup is buggy as hell. KDM starts up and works...sortof. I can get to kde and gnome, but I cannot get to failsafe. The kde session I get is all but useless. There are icons on the desktop, as per normal, harddrive/mount icons, printer icon, startup folder icon, home icon, trash icon, etc. Not a one of the drive icons works. Clicking on them neither mounts the drive nor opens the kfm file browser to see what is on the mount. Instead, a dialog comes up asking what app I want to use to open it (!?). The kmenu contains some items in it and half of them are non-functional INSPITE of the fact that they are installed. The run item in the kmenu is totally non-functional. Entering ANY command results in no action whatsoever. The panel settings menu item does absolutely nothing. For further evidence, there is the FACT that all but one or two sites have removed the rpms for kde 2.0 from them. That is a stone-cold, undeniable fact. Yesterday, after the announcement of the release, the rpms were EVERYWHERE. Today, they are hard to come by. There is very likely a good reason for that. There is nothing bizarre about my system. It is Mandrake 7.1 with updates brought on via MandrakeUpdate. There are few items built by myself WITHOUT error and installed without error and they work perfectly (the kernel, for instance). There is no FUD here, only objective description of what I see. It matches what some others have indicated themselves in this mailing list. It also matches well with what you can find in newsgroups. Cooker, as of this evening (and last I checked) no longer carries kde-2.0 rpms. It is kde-1.99. Mandrake 7.2beta doesn't carry them. I do not believe I saw 2.0 rpms in rawhide either (and it was there previously). The 2.0 rpms are no longer in MOST of the kde mirror sites. They were in all of them yesterday (I checked a large number of them as I tried to find a site that was available). praedor Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
I just downloaded it from ftp.kde.org . You can also download it from one of it's mirrors if the server is full. Marcus On Tue, 24 Oct 2000, you wrote: > > Real nice. Yesterday, kde releases, finally, the stable, > final kde-2.0. Yesterday you could download it from > mandrake cooker, from rpmfind, from every mirror > known to man. Today? > > It's totally gone. Vanished. NO mirror has it. It > no longer exists. Has ANYONE downloaded the set? > > Could you upload it to a mirror somewhere so people > can actually get it again? > > praedor Content-Type: text/plain; name="message.footer" Content-Transfer-Encoding: 8bit Content-Description: Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
"Ron Johnson, Jr." wrote: > > What if we trailing-edge types totally deinstall our 1.1.x > systems, then try to install kde2 from source? > You could try. When I did the attempt, the indications were that it would REPLACE your kde-1.1.2. In my experience, it did replace everything except kdebase-1.1.2. EVERYTHING else was replaced. This led to a double kdebase which was real screwy. I uninstalled the kdebase-1.1.2 manually and reinstalled kde 2.0. It worked better, such as that goes, but it was nearly useless. It just looked a little better at being useless. Give it a shot and let me know... I am always wondering if there is some small squirrelly thing wrong with my system. praedor Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
On Wednesday 25 October 2000 06:51, you wrote: > > Thanks. It still also resides in SOME (very few) kde mirrors. > > Here's the big question...did you actually install it and get it > working? I did, and it works okay > After downloading and installing, all was wrong with the world. First, > installing it, even with menu-3.0.5-43mdk installed, it segfaults during > the rpm install on /usr/bin/upgrade-menus. Both qt2 and kde rpms > segfault > it. Once it IS all installed, the system is broken. SOME things work, > most > do not. While you do need to update a few, again, a few files, it's not a major problem. You do NOT need the latest glibc from cooker or the latest gcc2.96 compiler. FUD does not help. Nuff said. Jerry -- Gerald Williams -- Words Matter! Bangkok, Thailand Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
What if we trailing-edge types totally deinstall our 1.1.x systems, then try to install kde2 from source? Ron Praedor Tempus wrote: > > Thanks. It still also resides in SOME (very few) kde mirrors. > > Here's the big question...did you actually install it and get it > working? > > After downloading and installing, all was wrong with the world. First, > installing it, even with menu-3.0.5-43mdk installed, it segfaults during > the rpm install on /usr/bin/upgrade-menus. Both qt2 and kde rpms > segfault > it. Once it IS all installed, the system is broken. SOME things work, > most > do not. > > Looking deeper into it, even though I got NO dependency missing > messages, > it appears that you HAVE to "upgrade" just about every rpm on your > system > to 7.2beta or Cooker level - all because you need to upgrade menu, > apparently, > even beyond menu-2.1.5-43mdk, because of the segfaults on > upgrade-menus. To > upgrade menu, to 4.0, which is all that is left, you must upgrade glibc > to > glibc-2.1.95 or 2.1.96. Doing THIS will break all the other rpms on > your > system, so you must upgrade them as well. > > It APPEARS that the "stable" kde 2.0 cannot be used except on an > unstable, > beta-only distro like 7.2beta or Cooker. There is a README I read on > one > mirror yesterday that indicated you could run kde 2.0 on other mandrake > versions, but you had to upgrade a few rpms (pam, menu, a COUPLE > others). > Problem is, it is NOT a few rpms. As I described above, to "simply" > upgrade > menu alone requires an entire cascade of other upgrades to satisfy > dependencies. > > At least with RedHat, though they offer glibc-2.1.95 (and 2.1.96) they > ALSO > have a glibc-compat rpm NOT for OLD glibc, but for the previous glibc > that > was in RedHat 6.2, which is essentially 2.1.3. No such beast exists for > Mandrake so if you upgrade glibc to upgrade menu to install kde 2.0, you > break everything. In for a penny, in for a pound. > > praedor > > philomena wrote: > > > > here's one... > > > > http://ftp.sourceforge.net/pub/mirrors/kde/stable/2.0/distribution/rpm/Mandrake/ > > > > Praedor Tempus wrote: > > > > > > Real nice. Yesterday, kde releases, finally, the stable, > > > final kde-2.0. Yesterday you could download it from > > > mandrake cooker, from rpmfind, from every mirror > > > known to man. > [...] -- +--+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA WWW : [EMAIL PROTECTED] | | http://ronandheather.dhs.org | +--+ Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Thanks. It still also resides in SOME (very few) kde mirrors. Here's the big question...did you actually install it and get it working? After downloading and installing, all was wrong with the world. First, installing it, even with menu-3.0.5-43mdk installed, it segfaults during the rpm install on /usr/bin/upgrade-menus. Both qt2 and kde rpms segfault it. Once it IS all installed, the system is broken. SOME things work, most do not. Looking deeper into it, even though I got NO dependency missing messages, it appears that you HAVE to "upgrade" just about every rpm on your system to 7.2beta or Cooker level - all because you need to upgrade menu, apparently, even beyond menu-2.1.5-43mdk, because of the segfaults on upgrade-menus. To upgrade menu, to 4.0, which is all that is left, you must upgrade glibc to glibc-2.1.95 or 2.1.96. Doing THIS will break all the other rpms on your system, so you must upgrade them as well. It APPEARS that the "stable" kde 2.0 cannot be used except on an unstable, beta-only distro like 7.2beta or Cooker. There is a README I read on one mirror yesterday that indicated you could run kde 2.0 on other mandrake versions, but you had to upgrade a few rpms (pam, menu, a COUPLE others). Problem is, it is NOT a few rpms. As I described above, to "simply" upgrade menu alone requires an entire cascade of other upgrades to satisfy dependencies. At least with RedHat, though they offer glibc-2.1.95 (and 2.1.96) they ALSO have a glibc-compat rpm NOT for OLD glibc, but for the previous glibc that was in RedHat 6.2, which is essentially 2.1.3. No such beast exists for Mandrake so if you upgrade glibc to upgrade menu to install kde 2.0, you break everything. In for a penny, in for a pound. praedor philomena wrote: > > here's one... > > http://ftp.sourceforge.net/pub/mirrors/kde/stable/2.0/distribution/rpm/Mandrake/ > > Praedor Tempus wrote: > > > > Real nice. Yesterday, kde releases, finally, the stable, > > final kde-2.0. Yesterday you could download it from > > mandrake cooker, from rpmfind, from every mirror > > known to man. [...] Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
[expert] Niiiiice. Kill off kde STABLE 2.0 immediately
Real nice. Yesterday, kde releases, finally, the stable, final kde-2.0. Yesterday you could download it from mandrake cooker, from rpmfind, from every mirror known to man. Today? It's totally gone. Vanished. NO mirror has it. It no longer exists. Has ANYONE downloaded the set? Could you upload it to a mirror somewhere so people can actually get it again? praedor Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] Niiiiice. Kill off kde STABLE 2.0 immediately
here's one... http://ftp.sourceforge.net/pub/mirrors/kde/stable/2.0/distribution/rpm/Mandrake/ Praedor Tempus wrote: > > Real nice. Yesterday, kde releases, finally, the stable, > final kde-2.0. Yesterday you could download it from > mandrake cooker, from rpmfind, from every mirror > known to man. Today? > > It's totally gone. Vanished. NO mirror has it. It > no longer exists. Has ANYONE downloaded the set? > > Could you upload it to a mirror somewhere so people > can actually get it again? > > praedor > > > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list. Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.