Jerry Feldman wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Sat, 04 Oct 2003 19:50:53 +0200 js wrote:

...

You can only upgrade the maintenance releases through yast, not the latest version number. To do that, you need to download the packages from suse's website. You'll have to install them manually.

Jerry Feldman wrote: You may need to download them manually, but you can upgrade them using YaST. Actually, if you use Konqueror: If you go to this URL: ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_8.2/base/.link/kdebase3.rpm

Konqueror will present you with a button, "Install package with YaST".

This is not what he meant. He wants yast to upgrade him with the update function. This won't work. The konqueror install you refer to is different entirely and can be done at the command line with... "yast -i /path/to/rpm/yadayada-1.i386.rpm" SuSE recommends this method instead of direct use of rpm because yast tracks which rpms it installs versus those installed by rpm. At least it did a couple versions ago. I assume it still does. John S.

Bernd Koepsell wrote:

On Sunday 05 October 2003 14:36, js wrote: <snip>

...

...

Konqueror will present you with a button, "Install package with YaST".

This is not what he meant. He wants yast to upgrade him with the update function. This won't work. The konqueror install you refer to is different entirely and can be done at the command line with... "yast -i /path/to/rpm/yadayada-1.i386.rpm" SuSE recommends this method instead of direct use of rpm because yast tracks which rpms it installs versus those installed by rpm. At least it did a couple versions ago. I assume it still does.

If you install from konq using the button mentioned above, it -does- install with yast, checks depends, and runs SuSEconfig. Afterward, it does show in yast as installed version number.

There is no need to install via command line, unless you want to. Installing via command line using yast command is the same as installing from konq and pressing the button to install with yast.

Also using konq, you are able to get the file description, the changelog, and list of files in rpm package.

Bernd

Perhaps I didn't make myself clear. Konq performs the install using yast in the same manner as the command line I listed above. If you install with yast -i, it does all the same checks and runs suseconfig as well. I only meant you don't need konq for that, and that the konq install does not address the original post. He wants to know how to get yast to upgrade kde to the latest version. You cannot do this with konq. You can do a manual install with yast, rpm, kpackage, or konq. The online update will only download patches, unless suse decides to add the upgrade to the list of updates (which is possible but aint likely). So again, if he wants to upgrade to 3.1.4, he will have to download the packages and install manually. John S.

Anders Johansson wrote:

On Monday 06 October 2003 02.19, js wrote:

...

So again, if he wants to upgrade to 3.1.4, he will have to download the packages and install manually.

Did you read my message in this thread? You are wrong!

You are as sutle as ever. If that is the case then I stand corrected. However, this is not a user friendly method nor is it practical to expect users to hunt through suse's ftp site to find the location of an unadvertised supplemental software tree, then change their install source to that location. There have been many posts in the past about peeople who never got yast's install/remove feature to work again after doing that though it has no doubt never happened to you. It would be far more practical for an available upgrade to advertise itself the next time that person does a manual online update. That would alleviate the problem. John S.

Good day Anders, Mandag den 6. oktober 2003 23:05 kvad Anders:

Anders Johansson wrote:

...

On Monday 06 October 2003 02.19, js wrote:

...

So again, if he wants to upgrade to 3.1.4, he will have to download the packages and install manually.

Did you read my message in this thread? You are wrong!

You are as sutle as ever.

If that is the case then I stand corrected. However, this is not a user friendly method nor is it practical to expect users to hunt through suse's ftp site to find the location of an unadvertised supplemental software tree, then change their install source to that location. There have been many posts in the past about peeople who never got yast's install/remove feature to work again after doing that though it has no doubt never happened to you. It would be far more practical for an available upgrade to advertise itself the next time that person does a manual online update. That would alleviate the problem.

There has also been many post in the past from people whose KDE was rendered more or less useless after a manual install. The original poster wanted to know how to use YaST for upgrading KDE, and he was told how. Advertising unofficial unsupported upgrades will only make them easier to find. If the upgrades contain bugs that take down YaST then the method of upgrading does not matter. YaST will have been taken down when the bugs are installed. Best regards :o) Johnny :o)

On Monday 06 October 2003 23.05, js wrote:

Anders Johansson wrote:

...

On Monday 06 October 2003 02.19, js wrote:

...

So again, if he wants to upgrade to 3.1.4, he will have to download the packages and install manually.

Did you read my message in this thread? You are wrong!

You are as sutle as ever.

Well, perhaps I should have phrased it better, it just bothered me that you repeated "it isn't possible" even after I had pointed out that it is

If that is the case then I stand corrected. However, this is not a user friendly method nor is it practical to expect users to hunt through suse's ftp site to find the location of an unadvertised supplemental software tree, then change their install source to that location.

I didn't say "change", I said "add". You can have more than one. As for its being unadvertised, well, I agree, I wish there were more official updates, but that's SuSE policy, I don't think it's going to change

There have been many posts in the past about peeople who never got yast's install/remove feature to work again after doing that though it has no doubt never happened to you.

Actually no, it hasn't. However, I just did what I consider to be a cool thing :) I patched the kernel with the lufs patch (http://lufs.sourceforge.net), then I mounted ftp://ftp.gwdg.de on my local file system. Then I used the "mount directory as channel" feature in ximian's red carpet, and voila, I get the upgrades listed when I start red carpet and I won't have to mess up YaST (potentially) to do it Worth a try, no? I know the kernel patching may seem difficult, but it's really not Install kernel-sources.rpm cd /usr/src/linux make cloneconfig patch -p1 < /path/to/patchfile make xconfig select LUFS from miscellaneous file systems save and exit make modules make copy lufs.o from /usr/src/linux/fs/lufs/ to /lib/modules/2.4.20-4GB (or whichever kernel you're running) compile and install lufsd from the lufs web site follow the instructions in the README on how to mount an ftp server I'm not sure if this is good practice or how much it burdens the ftp server (doesn't *look* like much), or even if it's the simplest way to go about it, but the end result sure is cool :) Of course, even better would be to rewrite red carpet to use gnome-vfs, that would probably be the "correct" thing to do

On Saturday 04 October 2003 03:16 pm, Anders Johansson wrote:

On Saturday 04 October 2003 18.35, Harry Giles wrote:

...

Is it possible? I am running 8.1 with the stock version, and I am looking for an easy way to do this. I searched the support database, but couldn't find anything on upgrading KDE.

ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_8.1/yast-sour ce

set that as an installation source in yast (or preferably use the corresponding directory from one of the mirrors). Then you should see the kde files when you do a "update complete system".

This has not been updated for 3.1.4 though. If you look at the timestamps on the directories created you can see that the kde folders like base and development were modified late september, however the yast-source has not been modified since july :(