When I select online update in Yast, a dialog pops up telling me:
No Update Repository Configured Yet. Run configuration workflow now?
I cannot figure out how to set this up. If I click “Yes” then “Finish”, I get a mostly blank YaST2 window with cancel and accept buttons. But the windows are all empty, so there is nothing to accept. And the next time I run online update, it again tells me “No Update Repository Configured Yet.”
Very confusing.
And the advanced, register scenario is even worse. The Novell website comes up with a “continue” button that doesn’t do anything…
in your list of repos, then you have the update repo. With Milestones and release candidates, the update repo doesn’t really do anythng until the final release.
You can get updates from the factory repos and from 11.2-oss and 11.2 non-oss.
Most things seem to work better on openSUSE than on Ubuntu, but this is one exception I have seen so far. This process works consistently and fairly clearly on Ubuntu from alpha to beta to release. (The only catch is that when partial updates are offered, accepting them can be problematic…) On openSUSE I do not yet understand it even after reading the help. I guess it will take some trial and error, which is what I’m doing now
Why is YaST showing no updates available for me when I’m running 11.2 milestone 8 and RC1 is out?
I am new to OpenSuse’s package management myself but I had success using the above command. I think technically the system update tool is not really meant to do anything until the final release because you are testing a development build and supplying bug reports on that particular snapshot.
Now, I have a couple more questions. When I open YaST control center, I see both “Online Update” and “Software Management”. What is the difference?
Both open a YaST2 application that looks exactly the same. Most of the menu choices are the same. But “Online Update” is empty, while “Software Management” Installation Summary suggests 4 packages I can upgrade.
question 1: why are there two identical looking tools that seem to duplicate functionality, yet simultaneously offer different results?
question 2: why would “Software Management” offer me 32 bit packages when I am running a 64 bit system? It offers me 32 bit flash, but I have 64 bit flash installed. I know I can block those packages, but I would like to know what exactly is going on. Is this just one of those pre-release things or is there a lesson here?
question 1: why are there two identical looking tools that seem to duplicate functionality, yet simultaneously offer different results?
I think these are different tabs within the package management system.
question 2: why would “Software Management” offer me 32 bit packages when I am running a 64 bit system? It offers me 32 bit flash, but I have 64 bit flash installed. I know I can block those packages, but I would like to know what exactly is going on. Is this just one of those pre-release things or is there a lesson here?
I am not sure about this one. I am running the 32 bit version and grabbed Flash from the Adobe downloads page and installed it using OpenSuse’s package manager. Flash is the only package that is not from the factory repo on my system. I have not added the packman repo yet to keep the upgrade path simple right now.
How did you install Flash on your system? If you have added repos to the system, this might be the problem you are experiencing. Sorry I do not have a definite answer for this.
Online Update opens to Patches, you can actually move it’s initial view to one that will match Software Management. Try the tabs along the top.
Flash player is still only supplied in _32bit and requires nspluginwrapper also.
FYI: I do all my Updating and Package management via Software Management. Never use the Online Updates or the Updater Applet (That gets removed from start up)
I tried all the tabs and some other options and I could not make the two “match”. I’ll keep exploring. And thanks for confirming that these are indeed the identical app with different startup parameters. That removes some confusion.
I find myself in a funny situation. I installed milestone 8 with the intention to just wipe it out and install something else when I was finished testing.
But now that I have it installed, I’m finding that I don’t want to change it. I am not even feeling the need to move to RC1. This is already one of the best OS experiences I have ever enjoyed. There is nothing on my computer (afaik) that is not working exactly like I want to to work.
That old saying, “If it ain’t broke, don’t fix it” has me thinking I’ll just stay here for a while. And that’s very unexpected from a pre-release OS.
EDIT: actually, I’ll probably keep experimenting and when I screw something up really badly, I’ll just install RC1 fresh.
That old saying, “If it ain’t broke, don’t fix it” has me thinking I’ll just stay here for a while. And that’s very unexpected from a pre-release OS.
I thought the same thing! I am not used to running something I don’t have to spend hours fixing. I did upgrade to RC 1 though. The only bug I have noticed was digiKam crashes on exit. I submitted the generated bug report but I have no idea how to verify that the developers got it. The final release should be really nice!
