Hello all. I recently migrated 2 systems from ArchLinux to openSUSE and dup-ed to Tumbleweed. Now, I want to make absolutely certain that I have RTFM, and that I’m not missing crucial pieces of information about the state and preferred methods of keeping things in order.
I have subscribed to the Factory Mailing List,
I have read the Tumbleweed Portal,
I have read the first few pages of the forums here.
What else do I need to cover to be as well informed as I can be? Is there a set of links that would prove useful to someone new to openSUSE/zypper/etc that might be more difficult to locate.
btw: most folks agree that it is best to have some good grounding in
openSUSE before jumping into Tumbleweed, but evidently you wanna be
out on the edge…
On 06/14/2013 08:06 PM, SquidGuy wrote:
> If I had a totally stable distro, I’d be bored.
funny! so, i hope it is challenging enough for you to stay awake, but
not so much you quit, mad…and stomp off…some do muttering
something like “Linux is Linux but openSUSE is different and i’m
going back to Brand X.”
I found it useful to give a different priority to the tumbleweed repos.
Currently I have Tumbleweed and Tumbleweed-Packman at priority 98, and everything else at the default 99. Note that a lower numeric value is a higher priority.
When I disable the 12.3 “KDE new” repo, this is the result.
3 packages to upgrade, 226 to downgrade, 229 to change vendor.
I chose kdebase4-runtime to show the stats. Besides the KDE version wanting to be downgraded from 4.10.4-431.1 to 4.10.3-1.30.9, all the accompanying libraries, along with the akonadi’s, soprano’s and virtuoso’s et.al., are (of course) also going to be downgraded.
kdebase4-runtime - The KDE Runtime Components
x86_64
Alternate Version Installed Version
Version: 4.10.3-1.30.9 4.10.4-431.1
Build Time: Mon 27 May 2013 12:22:04 PM EDT Sat 01 Jun 2013 03:02:43 PM EDT
Install Time: Tue 04 Jun 2013 10:39:36 PM EDT
Source Package: kdebase4-runtime-4.10.3-1.30.9 kdebase4-runtime-4.10.4-431.1
To me it seems like 12.3 has the most recent version. Does this sound right to you? I know there’s dangers keeping both repos enabled, but, I’ve been running it this way for a few months without any problems. Besides, I wouldn’t be running Tumbleweed and siduction (Debian Sid based) if I didn’t like adventure.
If you need further information, let me know.
Thanks.
Edit: Sorry, I’m not used to the formatting in the forum. I tried to make columns, and I failed.
Right, but this has nothing to do with “KDE extra”.
It’s just that Current-Updates has KDE 4.10.3 at the moment and “KDE new” has 4.10.4 to which you apparently have upgraded some days ago.
In about 2 weeks (maybe a few days less) Current-Updates will have 4.10.4 as well.
After the update to 4.10.5 in about a month, both of them will stay at 4.10.5 as there will be no more 4.10.x KDE release afterwards.
So I don’t really see the need to keep that repo. You will get exactly the same through Current-Updates, just a few weeks later (and better tested).
And at the end of July at the latest, that “KDE new” repo will be superfluous for you anyway. I’d also guess that Tumbleweed will update KDE to 4.11 some time later, so then “KDE new” will even be obsolete because it will stay at 4.10.5.
But anyway, do what you like. I just wanted to mention that there could be problems…
Thanks again for the info. It’s nice to know that KDE will be upgraded in “KDE Extra” soon. I look forward to disabling the “KDE New” repo. It’s also interesting that Current-Updates was the problem. I’m still getting use to finding where to look for info. This was sort of a learning experience. Thanks.
No, KDE itself is not part of the “KDE Extra” repo. “KDE Extra” is just for “KDE applications not available in the core distribution”.
KDE will be upgraded in Current-Update.
And later on, to 4.11 and beyond, in “openSUSE Tumbleweed” I guess. At least that’s what always has been done before and is done now still with GNOME. (With KDE it’s not necessary at the moment, because the 4.10.x updates are released through Current-Updates anyway)
It’s also interesting that Current-Updates was the problem.
Well, that’s not exactly true, it wasn’t Current-Updates that was the problem.
The problem was that you added the “KDE new” repo (actually called KDE:Release:410), which has a (slightly) newer KDE, and upgraded your KDE to the one from that repo.
When you then remove that repo again, your KDE will be downgraded to the older one of course, because the newer one isn’t available anymore.
