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: Include empty VERSION_CODENAME= field in os-release
Date: Mon, 10 Aug 2026 09:34:45 GMT [thread overview]
Message-ID: <178635448518.1.5866238161862963152.rpms-fedora-release-a5c97f9992cf@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/fedora-release
Branch : f45
Commit : a5c97f9992cf32acd4ca733537c1f99927fc053b
Author : Stephen Gallagher <sgallagh@redhat.com>
Date : 2018-12-12T13:39:32-05:00
Stats : +1/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/fedora-release/c/a5c97f9992cf32acd4ca733537c1f99927fc053b?branch=f45
Log:
Include empty VERSION_CODENAME= field in os-release
/etc/os-release now supports a VERSION_CODENAME field that should
contain the codename of a release if any exists. Fedora does not
use a codename, so it should be set to the empty string.
This is because some tools (such as https://github.com/nir0s/distro
for Python) attempt to interpret first the VERSION_CODENAME and
then subsequently fall back to parsing the VERSION field for a
codename within parentheses. This means that the tools will return
a different value of codename depending on which Edition was
originall installed. Instead, we should ensure that it returns no
codename at all.
Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
---
diff --git a/fedora-release.spec b/fedora-release.spec
index d991c96..10564f7 100644
--- a/fedora-release.spec
+++ b/fedora-release.spec
@@ -317,6 +317,7 @@ NAME=Fedora
VERSION="%{dist_version} (%{release_name})"
ID=fedora
VERSION_ID=%{dist_version}
+VERSION_CODENAME=""
PLATFORM_ID="platform:f%{dist_version}"
PRETTY_NAME="Fedora %{dist_version} (%{release_name})"
ANSI_COLOR="0;34"
reply other threads:[~2026-08-10 9:34 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=178635448518.1.5866238161862963152.rpms-fedora-release-a5c97f9992cf@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