public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: cvsdist <cvsdist@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/inn] epel10: auto-import changelog data from inn-2.3.3-5.src.rpm
Date: Wed, 26 Aug 2026 08:05:34 GMT [thread overview]
Message-ID: <178773153422.1.8224150536726879258.rpms-inn-a2a2f28af05e@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/inn
Branch : epel10
Commit : a2a2f28af05ef564d6f32180a90712b4b33367c9
Author : cvsdist <cvsdist@fedoraproject.org>
Date : 2004-09-09T06:17:15+00:00
Stats : +13/-4 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/inn/c/a2a2f28af05ef564d6f32180a90712b4b33367c9?branch=epel10
Log:
auto-import changelog data from inn-2.3.3-5.src.rpm
Tue Jul 23 2002 Florian La Roche <Florian.LaRoche@redhat.de>
- fix cron scripts to use correct paths #69189
- add compat symlinks for rnews/inews into /usr/bin
---
diff --git a/inn-cron-expire b/inn-cron-expire
index 7e72e74..4286ba4 100644
--- a/inn-cron-expire
+++ b/inn-cron-expire
@@ -1,3 +1,3 @@
#!/bin/sh
/sbin/chkconfig innd || exit 0
-su - news -c "unset LANG; unset LC_COLLATE; /usr/bin/news.daily delayrm"
+su - news -c "unset LANG; unset LC_COLLATE; /usr/lib/news/bin/news.daily delayrm"
diff --git a/inn-cron-nntpsend b/inn-cron-nntpsend
index ec82c99..23edde1 100755
--- a/inn-cron-nntpsend
+++ b/inn-cron-nntpsend
@@ -1,3 +1,3 @@
#!/bin/sh
/sbin/chkconfig innd || exit 0
-su - news -c "unset LANG; unset LC_COLLATE; /usr/bin/nntpsend"
+su - news -c "unset LANG; unset LC_COLLATE; /usr/lib/news/bin/nntpsend"
diff --git a/inn-cron-rnews b/inn-cron-rnews
index e0dc840..7282770 100644
--- a/inn-cron-rnews
+++ b/inn-cron-rnews
@@ -1,3 +1,3 @@
#!/bin/sh
/sbin/chkconfig innd || exit 0
-su - news -c 'unset LANG; unset LC_COLLATE; /usr/bin/rnews -U'
+su - news -c 'unset LANG; unset LC_COLLATE; /usr/lib/news/bin/rnews -U'
diff --git a/inn.spec b/inn.spec
index 548274b..daa880a 100644
--- a/inn.spec
+++ b/inn.spec
@@ -1,7 +1,7 @@
Summary: The InterNetNews (INN) system, an Usenet news server.
Name: inn
Version: 2.3.3
-Release: 4
+Release: 5
Copyright: GPL
Group: System Environment/Daemons
Source0: ftp://ftp.isc.org/isc/inn/inn-%{version}.tar.gz
@@ -129,6 +129,10 @@ rm -f $RPM_BUILD_ROOT/usr/lib/news/bin/filter/filter_innd.pl
#Fix perms in sample directory to avoid bogus dependencies
find samples -name "*.in" -exec chmod a-x {} \;
+mkdir -p $RPM_BUILD_ROOT/usr/bin
+ln -sf ../lib/news/bin/inews $RPM_BUILD_ROOT/usr/bin/inews
+ln -sf ../lib/news/bin/rnews $RPM_BUILD_ROOT/usr/bin/rnews
+
#Build filelist
echo "%defattr(-,news,news)" > files.list
find $RPM_BUILD_ROOT -type f -or -type l | \
@@ -235,10 +239,15 @@ exit 0
%files -n inews
%defattr(-,root,root)
%config(noreplace) /etc/news/inn.conf
+/usr/bin/inews
%attr(0755,root,root) /usr/lib/news/bin/inews
%{_mandir}/man1/inews*
%changelog
+* Tue Jul 23 2002 Florian La Roche <Florian.LaRoche@redhat.de>
+- fix cron scripts to use correct paths #69189
+- add compat symlinks for rnews/inews into /usr/bin
+
* Thu Jul 18 2002 Florian La Roche <Florian.LaRoche@redhat.de>
- make check if networking is up more robust in initscript
- move most apps into /usr/lib/news/bin for less namespace pollution
reply other threads:[~2026-08-26 8:05 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=178773153422.1.8224150536726879258.rpms-inn-a2a2f28af05e@fedoraproject.org \
--to=cvsdist@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