public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jesse Keating <jkeating@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-release] f45: - Provide system-release, useful for spinoffs.
Date: Mon, 10 Aug 2026 09:33:24 GMT	[thread overview]
Message-ID: <178635440440.1.11550098600957949194.rpms-fedora-release-e3ebaa689690@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/fedora-release
            Branch : f45
            Commit : e3ebaa68969037559ec2665d3d0742a7786730c1
            Author : Jesse Keating <jkeating@fedoraproject.org>
            Date   : 2007-08-30T10:27:31+00:00
            Stats  : +13/-4 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/fedora-release/c/e3ebaa68969037559ec2665d3d0742a7786730c1?branch=f45

            Log:
            - Provide system-release, useful for spinoffs.
- Also link system-release to fedora-release for file level checks
- Bump for F8 Test2
- Fix license tag

---
diff --git a/.cvsignore b/.cvsignore
index 4586703..cc801b4 100644
--- a/.cvsignore
+++ b/.cvsignore
@@ -1 +1 @@
-fedora-release-7.90.tar.gz
+fedora-release-7.91.tar.gz

diff --git a/fedora-release.spec b/fedora-release.spec
index 4a1b655..df90c90 100644
--- a/fedora-release.spec
+++ b/fedora-release.spec
@@ -3,14 +3,15 @@
 
 Summary:	Fedora release files
 Name:		fedora-release
-Version:	7.90
+Version:	7.91
 Release:	1
-License:	GPL
+License:	GPLv2
 Group:		System Environment/Base
 URL:		http://fedoraproject.org
 Source:		%{name}-%{version}.tar.gz
 Obsoletes:	redhat-release
 Provides:	redhat-release
+Provides:	system-release = %{version}-%{release}
 Requires:	fedora-release-notes >= 7
 # We require release notes to make sure that they don't get dropped during
 # upgrades, and just because we always want the release notes available
@@ -36,6 +37,7 @@ echo "Kernel \r on an \m" >> $RPM_BUILD_ROOT/etc/issue
 cp -p $RPM_BUILD_ROOT/etc/issue $RPM_BUILD_ROOT/etc/issue.net
 echo >> $RPM_BUILD_ROOT/etc/issue
 ln -s fedora-release $RPM_BUILD_ROOT/etc/redhat-release
+ln -s fedora-release $RPM_BUILD_ROOT/etc/system-release
 
 install -d -m 755 $RPM_BUILD_ROOT/etc/pki/rpm-gpg
 for file in RPM-GPG-KEY* ; do
@@ -65,6 +67,7 @@ rm -rf $RPM_BUILD_ROOT
 %doc GPL 
 %config %attr(0644,root,root) /etc/fedora-release
 /etc/redhat-release
+/etc/system-release
 %dir /etc/yum.repos.d
 %config(noreplace) /etc/yum.repos.d/*
 %config(noreplace) %attr(0644,root,root) /etc/issue
@@ -74,6 +77,12 @@ rm -rf $RPM_BUILD_ROOT
 /etc/pki/rpm-gpg/*
 
 %changelog
+* Thu Aug 30 2007 Jesse Keating <jkeating@redhat.com> - 7.91-1
+- Provide system-release, useful for spinoffs.
+- Also link system-release to fedora-release for file level checks
+- Bump for F8 Test2
+- Fix license tag
+
 * Thu Jul 27 2007 Jesse Keating <jkeating@redhat.com> - 7.90-1
 - Bump for F8 Test1
 

diff --git a/sources b/sources
index 7c35be6..81568a3 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-c6f95d4263824eb1131c4f45033f9778  fedora-release-7.90.tar.gz
+e1369de67fa8d66da8764e01d7128cbd  fedora-release-7.91.tar.gz

                 reply	other threads:[~2026-08-10  9:33 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=178635440440.1.11550098600957949194.rpms-fedora-release-e3ebaa689690@fedoraproject.org \
    --to=jkeating@fedoraproject.org \
    --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