Trying to update KDE via Synaptic...can't do it.
I keep getting an error when trying to update from KDE 3.0 to 3.1. After everything downloads, I get an rpm error. I've tried it 4 times and removing packages from cache 2 of those times. Nada. I seem to remember that I could do it with apt-get, but cant' remember the command. Can anyone help? Thanks, Tom --- Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com
* Tom Nielsen (tom@neuro-logic.com) [030302 20:16]: ->I keep getting an error when trying to update from KDE 3.0 to 3.1. After ->everything downloads, I get an rpm error. I've tried it 4 times and ->removing packages from cache 2 of those times. Nada. -> ->I seem to remember that I could do it with apt-get, but cant' remember ->the command. Can anyone help? SuSE changed which packages some programs come in and as a result when Synaptic runs apt it gets errors of things conflicting when they should not. Because these programs are in completely different packages then they were before..apt can not upgrade them safely so it quits. I would just open and xterm and run "apt-get upgrade" because it's already downloaded the packages so it won't try to do so again. It will just try to upgrade your system with the packages that it's downloaded already. It will tell you what the conflicts are...and I would remove only the few packages that are being the major PITA. One of the major offenders is pixieplus-kde...this one always bitches because they put pixieplus into another package. There are a few more but I don't remember them off hand. Cheers! -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
On Sun, Mar 02, 2003 at 08:44:35PM -0800, Ben Rosenberg wrote: : * Tom Nielsen (tom@neuro-logic.com) [030302 20:16]: : ->I keep getting an error when trying to update from KDE 3.0 to 3.1. After : ->everything downloads, I get an rpm error. I've tried it 4 times and : ->removing packages from cache 2 of those times. Nada. : -> : ->I seem to remember that I could do it with apt-get, but cant' remember : ->the command. Can anyone help? : : SuSE changed which packages some programs come in and as a result when : Synaptic runs apt it gets errors of things conflicting when they should : not. Because these programs are in completely different packages then : they were before..apt can not upgrade them safely so it quits. I would : just open and xterm and run "apt-get upgrade" because it's already : downloaded the packages so it won't try to do so again. It will just try : to upgrade your system with the packages that it's downloaded already. : It will tell you what the conflicts are...and I would remove only the : few packages that are being the major PITA. One of the major offenders : is pixieplus-kde...this one always bitches because they put pixieplus : into another package. There are a few more but I don't remember them off : hand. Try 'apt-get dist-upgrade'. 'dist-upgrade' is what you want to use when portions of packages get shuffled around. Oh, and as a precusor. For those that will be install XFree86 4.3.0 via apt, you'll need to do a little more. 'apt-get -o rpm::options::=--replacefiles dist-upgrade' The "-o rpm::options::=--replacefiles" is necessary since some of the XFree86-* files were previously part of the aaa_base package. --Jerry ps--does anyone know where to submit feedback for the SuSE apt4rpm page. It might be useful to put these tidbits of info up there. Open-Source software isn't a matter of life or death... ...It's much more important than that!
* Jerry A! (jerry@thehutt.org) [030302 21:07]: -> ->'apt-get -o rpm::options::=--replacefiles dist-upgrade' -> ->The "-o rpm::options::=--replacefiles" is necessary since some of the ->XFree86-* files were previously part of the aaa_base package. Well, I just ran this as you suggested Jerry and it appeared to work fine, but when I run SuSEconfig and it gets to Xft making it's cache files it sits and sits and sits. It's been "doing it's thing" for about 30 minutes at like 98% CPU usage. I do have about 210M of fonts if that's the cause..but I'm wondering if you had any issues with this update? -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
On Sun, Mar 02, 2003 at 11:40:12PM -0800, Ben Rosenberg wrote: : * Jerry A! (jerry@thehutt.org) [030302 21:07]: : -> : ->'apt-get -o rpm::options::=--replacefiles dist-upgrade' : -> : ->The "-o rpm::options::=--replacefiles" is necessary since some of the : ->XFree86-* files were previously part of the aaa_base package. : : Well, I just ran this as you suggested Jerry and it appeared to work : fine, but when I run SuSEconfig and it gets to Xft making it's cache : files it sits and sits and sits. It's been "doing it's thing" for about : 30 minutes at like 98% CPU usage. I do have about 210M of fonts if : that's the cause..but I'm wondering if you had any issues with this : update? I noticed that 4.3.0 didn't like the old SaX2-generated XF86Config. It would cause X to wedge when it started up. Didn't even think of checking if it did the same when it regenerated the font cache. My solution was to run xf86config4 and cut-n-paste the "FontPath" elements from the old XF86Config. Also, you'll want to go back and manually add various modules (extmod, v4l, glx, etc) and remove the part about disabling "extmod". About 10 minutes worth of work. But after that, SuSEconfig regenerated the font caches correctly and X has been working flawlessly for the past few hours. Hope this helps. --Jerry Open-Source software isn't a matter of life or death... ...It's much more important than that!
* Jerry A! (jerry@thehutt.org) [030303 00:13]: -> ->I noticed that 4.3.0 didn't like the old SaX2-generated XF86Config. It ->would cause X to wedge when it started up. Didn't even think of ->checking if it did the same when it regenerated the font cache. -> ->My solution was to run xf86config4 and cut-n-paste the "FontPath" ->elements from the old XF86Config. Also, you'll want to go back and ->manually add various modules (extmod, v4l, glx, etc) and remove the part ->about disabling "extmod". -> ->About 10 minutes worth of work. But after that, SuSEconfig regenerated ->the font caches correctly and X has been working flawlessly for the past ->few hours. Well, X and sax2 ran fine until I upgrade to the latest sax2. SaX2 now won't start but X runs fine with the acception of direct rendering. No matter what I do I can not get it to enable direct rendering. And every program that I start via xterm complains with this .. "libGL error: InitDriver failed" I don't *need* this on the machine I have in the office so I don't much care, but I would note to any of you in home userland that this may be an issue. My video card is a Radeon 7500. *shrug* Oh well..I've waste enough time regarding this today. latah. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
participants (3)
-
Ben Rosenberg -
Jerry A! -
Tom Nielsen