https://bugzilla.novell.com/show_bug.cgi?id=215649 ------- Comment #21 from judas_iscariote@shorewall.net 2006-10-30 22:15 MST ------- Can I agree with both of you ? :-) in short: 1 the problem is **ZMD itself** , I guess this is only fixable removing zmd all together. I don't see other solution .. this is broken by design.... :-( 2. zypp has it s own problems. but it is useful and is improving.. nothing agai nst it. 3. If we like and time permits, we can put efforts on testing both zypper and Opensuseupdater , I guess the comunity can help.-.what Im not sure if developers time will permit to fix the whole bunch of problems that a hard test can reveal. 4. Yes , might not be a good idea to make such radical changes in beta stage, but we claim for real solution for this problems, even if that means a longer beta process. 5. Maybe disabling the "Syncronize with ZenWorks" button on Yast by default and not staring the zmd daeamon by default is a good **start** for the next beta, or <crazy idea> syncronize it via cron </crazy idea> ,or start the sync only when the user actually wants to use rug , rewrite zen-updater to use libzypp ,or whatever (dunno), but don't make both yast and Zenworks interact with the user at the same time...** get ZMD out of the story** that's when the problem starts to be seen by the user.... yes, certainly Im missing something else, and probably is not that easy, both technically and specially politically ;-) -- 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.