https://bugzilla.novell.com/show_bug.cgi?id=246928 visnov@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kkaempf@novell.com |screening@forge.provo.novell| |.com | Component|YaST2 |libzypp QAContact|jsrain@novell.com |kkaempf@novell.com -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=246928 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net ------- Comment #2 from schubi@novell.com 2007-02-21 02:47 MST ------- Sorry, I cannot see in the logfile that xine-lib will be downgarded. Can you reproduce it ? If yes please attach a testcase described here: http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_d... -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=246928 robin.listas@telefonica.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|robin.listas@telefonica.net | ------- Comment #4 from robin.listas@telefonica.net 2007-02-21 07:06 MST ------- Created an attachment (id=120307) --> (https://bugzilla.novell.com/attachment.cgi?id=120307&action=view) Screenshot of what Yast wants to install Here it is seen how it wants to "downgrade" xine-lib. I will later try to repeat the procedure increasing log verbosity, as sugested. Notice that I don't install what it suggests, so maybe it doesn't show in the log. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=246928 ------- Comment #6 from robin.listas@telefonica.net 2007-02-21 08:28 MST ------- Created an attachment (id=120324) --> (https://bugzilla.novell.com/attachment.cgi?id=120324&action=view) dependency resolver test case logs Ok! There you have. That was easy, didn't have to restart Yast. I think the info it collects is way to extense, it gets previous logs, from other days, that do not pertain to this problem. Bigger size for you. May I suggest the rpm-qa file could have more info? There are rpms there I know I compiled and installed three or four years ago (I always upgrade the system), and that info is not shown. It might be interesting for you, once you collect "rpm -qa". I'm curious about the "evms-engine.log" file: it shows errors like this: Feb 17 04:42:38 nimrodel _2_ DosSegMgr: isa_valid_partition_record: error, partition starts below 1024 cyls but ends above it and ending CHS field is not MAX values Should I worry about that? fdisk doesn't report errors with my partitions... or is it something totally different and unimportant? -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=246928 ------- Comment #8 from robin.listas@telefonica.net 2007-03-09 18:30 MST ------- (Status changed to new so you can read my comment. Feel free to close it, I won't comment unless asked) Ok. I think, though, that Yast should not even try to do anything at all for a package in protected status. I have solved the issue for me increasing my rpm version number to "xine-ui-0.99.4-900" and "xine-lib-1.1.4-900". There must be a better method to install a private package and force Yast to respect it even if Yast has a newer version. I thought that is what "protected" meant! Ref "evms-engine.log", I know not what I have to report. I don't even know what evms is, I don't use any program of that name. I only know what I already said, and you already have the whole file. Please fill the bug report yourself, or tell me what more info you need from me. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=246928 schubi@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Comment #10 from schubi@novell.com 2007-03-12 01:45 MST ------- You do not have to reopen the bug. I am still getting this information although the bug is cloesed ;-) As I have already said in comment#7/comment#4 we are only installing the patch ( only the framework) and not the concerning packages. Please file a report to the maintainer of evms (CGAO@novell.com). A copy of comment #6 should be enough. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=246928#c12 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@ij.net --- Comment #12 from Felix Miata 2007-06-22 14:28:20 MST --- My / partition has limited freespace, so I don't want to add new or unnecessary stuff. I depend on smbfs, so didn't want a new kernel to force me to install sources, recompile to get the missing release module, and run out of freespace on /. So I: 1-opened YaST Control Center 2-clicked Software Management 3-selected package groups 4-clicked zzz All 5-scrolled down to kernel-default 6-right clicked 7-selected Protected 8-selected kerry 9-right clicked 10-selected all in this list 11-selected update if newer version available 12-clicked Accept YaST then proceeded to update what it thought needed updating, and to delete 2.6.18.2-34 and install the latest kernel version. I am not happy about this. IMO the protection from upgrade remains broken. One of the nicest things about Mandriva is urpmi won't replace any kernel automatically. Kernel upgrade there only happens by explicit request. I wish SUSE/YaST was as intelligent. Then I could update whenever updates were available instead of putting it off for months at a time to avoid YaST stupidity. -- 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=246928 User schubi@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=246928#c14 Stefan Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #14 from Stefan Schubert 2008-04-25 07:52:24 MST --- We have implemented the locking machanism for 11.0 completely new. So it should work now. -- 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.