public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Stephen Gallagher <sgallagh@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-release] f45: Add RELEASE_TYPE field to os-release
Date: Mon, 10 Aug 2026 09:36:39 GMT [thread overview]
Message-ID: <178635459986.1.7612151803109857894.rpms-fedora-release-948427054dc7@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/fedora-release
Branch : f45
Commit : 948427054dc751d47524295f510ebbfc54fef3f5
Author : Stephen Gallagher <sgallagh@redhat.com>
Date : 2024-10-18T12:19:15-04:00
Stats : +11/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/fedora-release/c/948427054dc751d47524295f510ebbfc54fef3f5?branch=f45
Log:
Add RELEASE_TYPE field to os-release
The latest os-release specification includes support for a RELEASE_TYPE
field to indicate the "development", "stable" or "lts" status of the
installed OS.
Related: https://github.com/systemd/systemd/issues/28459
Related: https://github.com/systemd/systemd/blob/main/man/os-release.xml#L329
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
---
diff --git a/fedora-release.spec b/fedora-release.spec
index d599901..706f619 100644
--- a/fedora-release.spec
+++ b/fedora-release.spec
@@ -2,6 +2,10 @@
%define release_name Rawhide
%define is_rawhide 1
+# Define this to 1 for Branched releases prior to RC
+# or 0 for RC and stable releases
+%define is_development 1
+
%define eol_date 2025-05-13
%define dist_version 42
@@ -65,9 +69,8 @@ Summary: Fedora release files
Name: fedora-release
Version: 42
# The numbering is 0.<r> before a given Fedora Linux release is released,
-# with r starting at 1, and then just <r>, with r starting again at 1.
-# Use '%%autorelease -p' before final, and then drop the '-p'.
-Release: %autorelease -p
+# and then just <r>.
+Release: %autorelease %[0%{?is_development} ? "-p" : ""]
License: MIT
URL: https://fedoraproject.org/
@@ -1375,9 +1378,13 @@ ln -s fedora-release %{buildroot}%{_sysconfdir}/system-release
%global dist_debuginfod_url https://debuginfod.fedoraproject.org/
# -------------------------------------------------------------------------
-cat << EOF >os-release
+# Set the RELEASE_TYPE appropriately
+%define release_type %[0%{?is_development} ? "development" : "stable"]
+
+cat <<EOF >os-release
NAME="%{dist_name}"
VERSION="%{dist_version} (%{release_name}%{?prerelease})"
+RELEASE_TYPE=%{release_type}
ID=fedora
VERSION_ID=%{dist_version}
VERSION_CODENAME=""
reply other threads:[~2026-08-10 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178635459986.1.7612151803109857894.rpms-fedora-release-948427054dc7@fedoraproject.org \
--to=sgallagh@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox