https://bugzilla.suse.com/show_bug.cgi?id=1230958 https://bugzilla.suse.com/show_bug.cgi?id=1230958#c15 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #15 from Stefan Hundhammer <shundhammer@suse.com> --- I am pretty sure that wasn't intentional. Also, in our internal chat where I raised this, I received an answer that they try their best to make sure that 'zypper up' / 'zypper dup' works flawlessly. But 'yast2 sw_single' isn't anything near as sophisticated as the corresponding zypper commands: For that 'Update if newer version available' action, it simply iterates over the packages and sets each one to 'Update' if there is a newer version. It relies on the libzypp dependency resolver to tell you any potential problems. And that's what it did, which drowned you in errors. Anyway, it's good that we now have this bug report, and that it now includes instructions how to handle this particular problem, and the section about rolling releases. We are aware of this particular problem, and of the problem of conflicting package versions in general. Slowroll is also still in its very early stages; a lot of infrastructure and checks that could be done are not yet available. I am optimistic that this will come in the future. Following the Open Source mantra of "release early, release often", this is parts of the lessons learned on our side. It's good to have an engaged community that participates in this. Having said that, AFAICS this is as far as we can handle this here. There is no really good bug resolution for this; it would be something along the lines of "we try to be better in the future". So for now, I am closing this as "WORKSFORME" to avoid having to involve another dozen of people who could just repeat what I already wrote. -- You are receiving this mail because: You are on the CC list for the bug.