Bug 2049054

Summary:	Make sure version of systemd as reported in systemctl --version starts with number
Product:	Red Hat Enterprise Linux 9	Reporter:	Michal Sekletar <msekleta>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jamacku, mabellon, rskvaril, systemd-maint-list
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-250-3.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 15:57:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Sekletar 2022-02-01 12:32:10 UTC

Description of problem:
Previously some customers (e.g. SAP) expressed their frustration about the change we did upstream in terms of how we report our version. 

Let's not break "compatibility" (in quotes because version string was never part of our official compatibility promise) unnecessarily and keep the version reporting the same as it was in RHEL-8.

Version-Release number of selected component (if applicable):
systemd-250-1

How reproducible:
always

Steps to Reproduce:
1. systemctl --version

Expected results:
systemd 250 (v250-1.el9)

Additional info:
Strictly speaking we wouldn't need to do any explicit change here and just rely on output of tools/meson-vcs-tag.sh during the build (which seem to produce the correct result) but it is often better to be explicit than implicit to prevent accidental breakage.

Comment 5 errata-xmlrpc 2022-05-17 15:57:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: systemd), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3979