Bug ID | 1182925 |
---|---|
Summary | suse-release / suse-release-oss is missleading as SLE does have such provide at all |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.2 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Patterns |
Assignee | lubos.kocman@suse.com |
Reporter | lubos.kocman@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Hello Neal Gompa recently raised question about suse-release Provides in Leap/SLE as 15 SP3 Backports fail on installcheck while openSUSE Leap release package (still) has such provides. Background: Seems like from SLE point of view there could have been a package in the past. But generally in SLE15 code base sle never provided suse-release. See line 107 https://build.suse.de/package/view_file/SUSE:SLE-15-SP3:GA/000package-groups/SLES-release.spec.in?expand=1 # create /etc/SuSE-release - deprecated, FATE#316268 # no longer build, in case you wonder Why do I suggest removal? My problem is that it seems to provide expectation that all SUSE family products and project have suse-release and that is not the case. Could we get rid of these misleading provides (suse-release, suse-release-oss)? https://en.opensuse.org/openSUSE:Packaging_guidelines https://en.opensuse.org/openSUSE:Packaging_for_Leap These articles do not reference them at all. I did grep all of openSUSE:Leap:15.3 and openSUSE:Backports:SLE-15-SP3 and this was the result: lkocman@localhost:/mnt/obs> grep suse-release openSUSE*/*/*.spec openSUSE:Leap:15.3/000release-packages/Leap-release.spec:Provides: suse-release = %{version}-%{release} openSUSE:Leap:15.3/000release-packages/Leap-release.spec:Provides: suse-release-oss = %{version}-%{release}