public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Bill Nottingham <notting@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/setup] update_services: update
Date: Mon, 22 Jun 2026 15:54:40 GMT	[thread overview]
Message-ID: <178214368017.1.6058137715157827081.rpms-setup-1ee03ef0cf0a@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/setup
Branch : update_services
Commit : 1ee03ef0cf0ad72a9d17029b8f1be697ece41ac5
Author : Bill Nottingham <notting@fedoraproject.org>
Date   : 2004-09-28T16:21:11+00:00
Stats  : +11/-5 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/setup/c/1ee03ef0cf0ad72a9d17029b8f1be697ece41ac5?branch=update_services

Log:
update

---
diff --git a/.cvsignore b/.cvsignore
index 15d5899..29e9ae9 100644
--- a/.cvsignore
+++ b/.cvsignore
@@ -1 +1 @@
-setup-2.5.34.tar.bz2
+setup-2.5.35.tar.bz2

diff --git a/setup.spec b/setup.spec
index 320c013..b18e4a4 100644
--- a/setup.spec
+++ b/setup.spec
@@ -1,7 +1,7 @@
 Summary: A set of system configuration and setup files.
 Name: setup
-Version: 2.5.34
-Release: 2
+Version: 2.5.35
+Release: 1
 License: public domain
 Group: System Environment/Base
 Source: setup-%{version}.tar.bz2
@@ -28,6 +28,8 @@ rm -f %{buildroot}/etc/uidgid
 mkdir -p %{buildroot}/var/log
 touch %{buildroot}/etc/{shadow,gshadow}
 touch %{buildroot}/var/log/lastlog
+touch %{buildroot}/etc/environment
+chmod 0644 %{buildroot}/etc/environment
 chmod 0400 %{buildroot}/etc/{shadow,gshadow}
 chmod 0400 %{buildroot}/var/log/lastlog
 
@@ -50,6 +52,7 @@ rm -rf %{buildroot}
 %verify(not md5 size mtime) %config(noreplace) /etc/services
 %verify(not md5 size mtime) %config(noreplace) /etc/exports
 %config(noreplace) /etc/aliases
+%config(noreplace) /etc/environment
 %config(noreplace) /etc/filesystems
 %config(noreplace) /etc/host.conf
 %verify(not md5 size mtime) %config(noreplace) /etc/hosts.allow
@@ -68,7 +71,10 @@ rm -rf %{buildroot}
 %config(noreplace) %verify(not md5 size mtime) /var/log/lastlog
 
 %changelog
-* Mon Sep 28 2004 Rik van Riel <riel@redhat.com> 2.5.34-2
+* Tue Sep 28 2004 Bill Nottingham <notting@redhat.com> 2.5.35-1
+- add /etc/environment
+
+* Mon Sep 27 2004 Rik van Riel <riel@redhat.com> 2.5.34-2
 - mark /etc/services config(noreplace) (#133683)
 
 * Thu Sep 23 2004 Bill Nottingham <notting@redhat.com> 2.5.34-1

diff --git a/sources b/sources
index 009a663..2c12d86 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-f239bfbe7a4aa5896e38622d829e1b8f  setup-2.5.34.tar.bz2
+d754f1b793cd834ffcab5d12b1ca133d  setup-2.5.35.tar.bz2

             reply	other threads:[~2026-06-22 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 15:54 Bill Nottingham [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-22 15:54 [rpms/setup] update_services: update Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham
2026-06-22 15:54 Bill Nottingham

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=178214368017.1.6058137715157827081.rpms-setup-1ee03ef0cf0a@fedoraproject.org \
    --to=notting@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