https://bugzilla.novell.com/show_bug.cgi?id=351018 Cristian Rodriguez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=351018 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=351018#c1 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |pallotta@inwind.it --- Comment #1 from Stefan Hundhammer 2008-01-02 04:15:51 MST --- It's impossible to tell what happened here without logs. In general, the YaST2 software management (and the underlying libzypp) query the RPM data base to find out which packages are installed - just like you could do on the command line with "rpm -q <pkg-name>". That means the package status you see in the software management dialogs really displays the status as the system knows it, not some artificial status information that bypasses the lower system levels. That status display can be trusted. To me this is very likely one of those scenarios: (1) Are you sure the status that was reported after the failed installation attempt was "keep installed" (blue check mark), not "install" (black check mark)? And that it was not installed at all before? (2) Situations like yours might be confusing: Active update repository, but currently not reachable. When you install a package that is available in a newer version from the update repository, you will get that newer version by default, not the older version shipped on CD/DVD. Of course, if the update repository is not reachable, you will get an error message when the package installation is actually being performed. In this case, you will have NO version of that package installed afterwards. The system will not try to install the older version instead if the updated version is not available. OTOH, the error situation is quite similar (and thus easy to confuse with) a failed online update: If there is an older version of a package installed and there is a patch for that package (i.e., a newer version of that package contained in a patch on the update repository), you will also get an error message that tells you that installation of that package failed. But since you already had an older version of that package installed, of course you will still have that older version of that package installed after the error. In general, if you know that your internet connection is slow or generally not very well available, you might want to disable the update repository during the times you know you have no working internet connection. If you have no internet connection at all on that machine, this is not a problem since you won't get any information from update repositories in the first place, i.e. the package management will never even know that there are newer versions of anything available, so you won't ever get this error scenario. Only if there is an initial internet connection and the update repository gets initialized, the package management fetches information about available updates (creating a repository cache), and any subsequent package installation will check if there is any newer version available from the update repository. OTOH, having that information makes little sense if it cannot be used because the updated packages cannot be fetched. Please check if the problem scenarios above match your problem. If you are positive that none fits, please attach y2logs - see also http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_aske... http://en.opensuse.org/Bug_Reporting_FAQ#What_does_that_NEEDINFO_bug_status_... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.