On 11/22/2016 10:52 AM, Todd Rme wrote:
I propose we remove the SLE 11 repository from devel:languages:python. Most spec files require special workaround to build at all with this target and it requires backporting a bunch of system-critical packages that no other release requires, and even then many packages fail to build. And the scheduler punishes the repo for having failures.
The amount of effort needed to keep basic, key dependencies working is growing constantly. And these workarounds means that it will be essentially infeasible to support it in the upcoming single spec file system, which means most key packages will no longer be able to support it anyway.
Anyone who really needs specific packages can always link to them and build them in their home repo.
So I think we should go ahead and remove it. Once it is removed, packages that are updated can have the workarounds deleted
I agree that it is a pain. I also agree that going forward things will become ever more painful. However the approach of "link to the project" where needed is not really a good solution either. If we drop SLE_11 builds and then remove the special SLE_11 handling in the spec file the person that has linked to the package MUST carry a local diff in addition to the link to re-add the SLE_11 special handling. Chances are that the local diff will be broken every time the package in d:l:p gets updated. Consequently people will probably make copies meaning a possibly significant increase of builds in OBS. So if we turn of SLE_11 in d:l:p we should agree to keep the SLE_11 special code in the spec files until EOL of SLE_11, sometime in 2019, rather than penalizing those that need/want to help users that still use SLE_11, for whatever reason. As proposed I oppose the change. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo