openSUSE 11.2
KDE Version 4.3.1 (KDE 4.3.1) “release 6”
On KDE.org it says that KDE 4.3.3 has been released with lots and lots of bugfixes so i wonder how i can update to that version…
Thanks!
Add repo: Index of /repositories/KDE:/43/openSUSE_11.2
then: zypper dup -r <repo_name>
Add these repositories
Then open Yast Software Management, Click view by pattern. Choose the KDE4 Base System, then click Package>All in this list>Update Unconditionally. Then choose KDE4 Desktop Environment, then click Package>All in this list>Update Unconditionally.
Caf will probably be writing a how-to for us 11.2 users.
Take Care,
Ian
- How do i add a repo like that?
zypper ar "http://download.opensuse.org/repositories/KDE:/43/openSUSE_11.2" KDE43
zypper ref
zypper dup -r KDE43
That hard? 
<repo_name> is the name of the repo you gave it, in our case KDE43 (or an alias)… to see repo names, do zypper lr
ok… 
thanks
What is the main difference between the two repo’s:
Index of /repositories/KDE:/43/openSUSE_11.2
-AND-
Index of /repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_Factory
One says KDE 4.3.x and the other says 4.3 + Patches? What about upgrading to 4.4 when it’s eventually released?
main diff is that 43 repo keeps packages a bit more stable while factory can change up to 3 times/day and often does not guarantee stability
Hi, I’ve just moved to openSUSE yesterday from Kubuntu. Quite liking it;)
Can you tell me why 11.2 installs 4.3.1 by default and not 4.3.3? Will 4.3.3 be pushed through the standard updates? Is it recommended to add the repository to get KDE updates or stick with the standard repos only?
Thanks.
Because only 4.3.1 was available when they did version freezing in the build service before pushing out 11.2 some time later
No, SUSE does not provide version upgrades through its default Update repository. This is to minimize breakage and maintenance overhead of multiple versions. If you want newer version of packages, you’d have to add extra repos, like the one above if you want KDE 4.3.3
Why: because of version freeze in development phase. KDE4 4.3.2 and 4.3.3 appeared afterwards. They do that to have the chance to completely optimize and stabilize the KDE4 version that comes with the official release.
4.3.3 will not be pushed through standard updates. Updates and patches for 4.3.1 will though.
Whether you want to update to 4.3.3 (and later) is up to you. In the posts above it’s pretty well described how to.
Since you just moved to openSUSE, I’d say, you stick to the installed versions first and spend some time reading about Yast. This wonderful tool makes a big difference to the *buntu’s, once you get to know it.
If you do want to upgrade, follow instructions from one of the posts above. I’d go for the 43 repos.
Welcome to the forums BTW
Just noticed a chip is faster than a knurpht’s brain…
Sounds good to me! Coming from Ubuntu, I’m just making my first baby steps into openSUSE, KDE, and into RPM package management. YaST is new to me as well, so I almost feel like I’m learning all over again!
When I do this, I get this error:
Problem: nothing provides libmysqlclient.so.16()(64bit) needed by amarok-2.2.1-41.1.x86_64
Solution 1: keep amarok-2.1.1-7.6.x86_64
Solution 2: break amarok by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c):
But if I do
sudo zypper dup
I get what appears to be no problems, should I avoid zypper dup, and do as you say with the “-r” switch?
zypper dup, without the -r switch, acts on ALL repositories thus it’ll pull the newest packages of ALL repos you have in your list. The -r switch tells it to only grab the newes from the repository you provided, thus when upgrading KDE, it is recommended to use -r along with its repo name, eg zypper dup -r KDE43
libmysqlclient should already be in the OSS repository… install it
Thank you for the reply.
I’d like to install the newest packages from all the repositories, and when I run zypper dup, it offers to install libmysqlclient.
So if I just do zypper dup, will that be okay?
Well, I usually don’t recommend to install all new versions of every single package you have on your system as it can cause problems (though not always). For this case specifically, just do zypper in libmysqlclient and then zypper dup -r KDE43
Also, you should keep your repository to a minimum, unless you really need to add another one which gives you what you need/want… I have only the following repos
- OSS
- non-OSS
- Update
- KDE43
- Packman
I’ve been doing that ask you suggest, now when I run zypper dup -r KDE43 it says it has to downgrade some packages…
The following packages are going to be downgraded:
choqok ksmolt libgpod4 libgpod-tools libmtp8 libredland0
The following packages are going to be reinstalled:
libepub0 libgadu libmsn0_1 libotr2 libpolkit-qt0 libqimageblitz4 libraptor1 librasqal1 libsoprano4 libssh3 libstrigi0
soprano soprano-backend-redland strigi yakuake
This is normal? Again, zypper dup only affers to install about 3 or 4 new packages, and change vendor on a bunch cause of the new repo
Yes, this is normal and can happen. Downgrading a package does not always mean that it is a program version downgrade. Often, packagers repackage a program multiple times and based on what changes they did that forced them to repackage, they can increase or (in this case) decrease the RPM version number but keep the program version number the same… example:
package foobar-1.2.3-3.0.rpm → foobar-1.2.3-2.0.rpm
as you can see, the program’s version is in botch cases 1.2.3, only the RPM buildversion has changed from 3 to 2, thus this is also counted as a type of downgrade. The reasons for downgrading or upgrading an RPM version can be multiple, and one of them is that something wasn’t done right while packaging so a rebuild is needed which, based on changes, increases or decreases this number
Ahh, that makes sense! Thank you!
I went and did zypper dup and it (so far) is working out fine, KDE 4.3.3! Yay!
Thank you for the advise and replies to my questions Micro.
The “-r” is… I don’t think it would make any harm to just remove it. It will cause problems like the mysql one.
“–from” does the same but correctly.