On Tue, Sep 6, 2016 at 8:56 PM, Achim Gratz
If the version is actually the same and only the build number is lower, then yes, I'd expect this to be normal.
Well at the end of the checking for conflicts in zypper dup, it reported tens of file conflicts certain files blocking from one package old to a file from the new to be installed packages. I escaped the zypper dup there and didn't upgrade. It looks too weird to me. The warning read, if to be continued files will be replaced and losing previous content. Is this normal? Is beta1 42.2 rather a huge step backwards in software versions of packages and will only get more current than 42.1 when it actually goes rtm and afterwards? About those build numbers and versions, the most prominent things I remember were that upgrade to beta1 would bring mozilla firefox in again as version 42.0 or 41.0 even and libreoffice at 5.0.something, googlechromium downgrading again to some 47 or so from 51 or even 52 on the 42.1 leap and other stuff. There are lot of libraries that have been getting security fixes in the recent weeks and months. I wonder if beta1 is then actually supposed to be fit for daily use, it looks rather risky and more like a trap if anyone would use these seriously downgraded and outdated versions compared to 42.1. Seems more like a trap to me and users should be warned I guess. And those were only a few package names that I could remember. There are many more things that I can think of such as libraries for openssl openssh and more. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org