On Sun, 2016-06-26 at 11:30 +0200, Eric Schirra wrote:
Am Sa 25 Jun 2016, 22:51:41 schrieb Jan Engelhardt:
On Saturday 2016-06-25 20:59, Eric Schirra wrote:
Why was devel:languages:python/openSUSE_13.1 removed?
I think openSUSE_13.1 is Evergreen.
https://www.youtube.com/watch?v=lz3whk4E_IA 24:45-25:10 Of course you should watch the whole thing to get the larger context.
Okay i have seen it. And when i understand right, i can not agree with it. Richard speek from future stable package and i can he understand, but this is not the point of view for me. And not my suit.
I live in the present and with distris 13.1, 13.2 and leap 42.1 When i need packages or create one i need it for those versions. Tumbleweed and especially Factory is for me an 'by-product'.
So Evergreen is 13.1. When i will use 13.1 i need package for 13.1. And when i can not build these package, because other (for me now python) is missing, i can not use evergreen. So there is no need for evergreen. Why it gives evergreen then?
Would it have helped if the python packages you need were in 13.1 proper and you didn't need to use devel:languages:python?
What should i do now? Upgrade to 42.1? No time for that. Brings other errors and problems. 13.1 is running very well. Use a other distro with really LTS?
Random OBS projects != distro. If you want to talk about distro, stick to the official distro packages.
I don't want this. Waht should i do now?
I can understand development but i can also understand users. And for my opinion users must the point of view. Not the developments. Without users, no developents needed. Development and developers are the service provider for users.
I'm told that volunteer based developers are primarily service providers for themselves. Unless they give you an SLA or explicit some form of commitment even if best effort, all bets are off. On the other hand the openSUSE distro does strive to provide some level of service to it's users.
Not reverse order.
And a little note to the video. Almost anytime a question had a dissenting opinion from Richard, the question was not answered and the next question was taken. This is not right for me.
Actually Richard is trying to help specifically users like you from hitting the issue you just hit. The issue you have right now is one (of several) of the challenges we are trying to solve with the openSUSE:Backports projects for SLE-12. The various OBS projects have their own standards on what, how, and how long they will support particular target builds. They come and go and there isn't any form of standardization here (and I don't argue there should be). That's not nice for most end users and we have had some SLE customer bit by this as well. With the Backports project we plan to keep all binaries available for the life of the distro even if the "upstream" packagers have moved away from supporting it in their rolling OBS project. It's one of the reasons that it's hard to recommend SLE users to use or count on packages built in the various OBS projects. I think what Richard's point was is that for same reasons we shouldn't recommend it for openSUSE users either. That begs the question of where should extra packages go that will have a dependable, persistent, standardized life cycle that end users can count on for whatever release of openSUSE they use old or new? -Scott -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org