On Tue, Nov 22, 2016 at 7:51 PM, Simon Lees
On 11/23/2016 03:47 AM, Alberto Planas Dominguez wrote:
On Tue, 2016-11-22 at 17:43 +0100, Christian wrote:
Am 22.11.2016 um 17:29 schrieb Robert Schweikert:
As proposed I oppose the change.
I oppose the change, too.
Can we extend a bit more? As I see in monitoring[1] there are several packages that do not build in sle11 anymore. According to the page there are
* succeeded: 1386 * failed: 154 * unresolvable: 175 * broken: 3 * disabled: 239
So a significant portion of the packages are not working.
I really doubt that SLE11 users are using d:l:p anymore (but I can be wrong).
[1] https://build.opensuse.org/project/monitor/devel:languages:python
Maybe we can take a half step instead.
Keep the repo's enabled but advise maintainers that they are not obliged to keep SLE-11 building if it requires additional effort on there behalf, in that way the people that do care about having package X available on SLE-11 and that are willing to make it work can do so. Packages that are unresolvable, known to have bugs that stop them working in a significant manner or will have security issues under SLE-11 should be disabled for build on SLE-11 with the reason documented somewhere so people know what it takes to get re enabled. We could extend this further to packages not building (when someone branches the package its easy enough to see why it was disabled). These packages could then be reenabled for build if someone steps up to fix them.
From what I recall this is already the policy. The problem is that "the people that do care" aren't stepping up to do the work, but failing packages keep getting re-enabled and left failing.
SLE-11 is the only supported platform that doesn't support Python 3 and, more importantly, the only supported platform that doesn't support noarch Python packages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org