Fix client specs for suse #10553
Fix client specs for suse #10553
Conversation
m-bucher
force-pushed
the
fix_client_specs_for_suse
branch
3 times, most recently
from
4823dc1
to
84b5a87
Compare
| %if 0%{?rhel} > 7 || 0%{?fedora} || 0%{?suse_version} | ||
| mv ygg_worker %{name}-%{version} | ||
| %endif |
There was a problem hiding this comment.
Not sure about this one. I assume this has to do with the different contents of %{gobuild}, resulting in differently named binaries 🤔
m-bucher
force-pushed
the
fix_client_specs_for_suse
branch
from
84b5a87
to
ee66c02
Compare
m-bucher
force-pushed
the
fix_client_specs_for_suse
branch
from
ee66c02
to
087cb24
Compare
| Summary: Message dispatch agent for cloud-connected systems | ||
| %if 0%{?suse_version} |
There was a problem hiding this comment.
For what it's worth, Red Hat is also moving to SPDX tags. We haven't started the bulk migration, but see https://communityblog.fedoraproject.org/important-changes-to-software-license-information-in-fedora-packages-spdx-and-more/ for more. https://docs.fedoraproject.org/en-US/legal/update-existing-packages/ is the official Fedora way, but RHEL is planning the same. I just don't know for sure where that migration currently is. IIRC we've been asked internally to start changing.
It would be my preference to keep things simple. Can we change all the license tags for the client packages at once?
|
#11116 was merged, fixing ygg_worker |
|
now #11118 |
|
Thanks @evgeni for finishing this. |
Fix some client spec-file problems on SUSE 15 build.
Also OpenSUSE Build Service checks some stuff like
Licensestring to be compatible with https://spdx.org/licenses/