On Fri, Feb 16, 2018 at 10:41:53AM +0100, Dominique Leuenberger / DimStar wrote:
Anyway, the stones started moving and the current way being worked on is:
rpmlint will accept SPDX-3-.0 as the main license strings. The few SPDX-2.0 strings that would be no longer available are added to the list of allowed licenses.
So that means a spec file with GPL-3.0+ is as valid as GPL-3.0-or- later.
Glad to hear that.
obs-service-format_spec_file will rewrite the license to SPDX-3.0 format.
Very unhappy to hear this, though.
This will result in 'old' distros (anyhting released prior to Leap 15) to 'warn' about invalid licenses, but outside of the openSUSE:* namespace, invalid licenses are a warning only and can be ignored. License strings are only enforced inside the openSUSE:* namespace (this is not new)
What I do quite often is e.g. osc checkout openSUSE:Factory $package cd openSUSE:Factory/${package} osc build ... --alternative-project openSUSE:Leap:42.3:Update Such build would fail when your plan is implemented.
This is the cleanest solution forward I can think of, allowing TW/{SLE,Leap}15 to move forward, and not breaking every spec file we curretnly have. Over time I expect the spec files in TW to have moved to SPDX-3.0 - that's when I'll revisit rpmlint changes and possibly no longer accepting SPDX-2.0 identifiers. But this is not goint to be int he next few weeks.
What I would prefer would be to either stick with 2.0 identifiers in specfiles or make sure 3.0 identifiers would be also accepted when building against those projects which currently enforce SPDX-2.0 identifiers for License tag. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org