Am 22.03.2017 um 09:59 schrieb Ludwig Nussel:
Wolfgang Rosenauer wrote:
Am 20.03.2017 um 17:18 schrieb Marcus Meissner:
Note that the openSUSE Leap 42 class of distributions is designed to be easily upgradable within minor versions, so Leap 42.1 to Leap 42.2 update should be easy and seemless.
and if they are not? That list does not look too bad but it's just for the "Upgrade" component. There may be others.
What concerns me is that almost all are NEW. At least one of them made me stop ugprading my remaining 42.1 systems at least temporarily in the hope that there might be patches coming up.
So the question is how to deal with unresponsive package maintainers?
Probably :-( I'm not saying I have a solution for that. I mean it hurts Leap's reputation and given that some affected components are rather critical especially in server environments where Leap was supposed to replace Evergreen (at least in my mind) this is a problem. For example I'm pretty sure that SLE has openldap as well. How and who would deal with that component in SLE and why is there a disconnect between SLE and Leap there? Or is there none and SLE is broken the same way? (I doubt that.) IMHO we as a project should try everything to avoid that or mitigate such situations. Unresponsive maintainers can always happen unfortunately for many reasons. Probably there are or should be a few key areas where we introduce a fallback to drive things forward? As said I do not have a solution but I would love to have Leap accepted as some kind of LTE which we still have to prove that it works. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org