public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Nikola Pajkovsky <npajkovs@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/inn] epel10.3: forgot add inn-2.5.1-nologinshell.patch inn-2.5.1.pie.patch
Date: Wed, 26 Aug 2026 08:54:01 GMT [thread overview]
Message-ID: <178773444124.1.3916433653007405138.rpms-inn-74e5a8512c61@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/inn
Branch : epel10.3
Commit : 74e5a8512c61c7ae9396f543ab35492815e621c9
Author : Nikola Pajkovsky <npajkovs@fedoraproject.org>
Date : 2009-10-19T10:03:57+00:00
Stats : +116/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/inn/c/74e5a8512c61c7ae9396f543ab35492815e621c9?branch=epel10.3
Log:
forgot add inn-2.5.1-nologinshell.patch inn-2.5.1.pie.patch
---
diff --git a/inn-2.5.1-nologinshell.patch b/inn-2.5.1-nologinshell.patch
new file mode 100644
index 0000000..d79a0c6
--- /dev/null
+++ b/inn-2.5.1-nologinshell.patch
@@ -0,0 +1,92 @@
+diff -up inn-2.5.1/doc/man/rc.news.8.nologin inn-2.5.1/doc/man/rc.news.8
+--- inn-2.5.1/doc/man/rc.news.8.nologin 2009-10-12 20:24:04.000000000 +0200
++++ inn-2.5.1/doc/man/rc.news.8 2009-10-13 21:55:50.000000000 +0200
+@@ -175,20 +175,20 @@ is recommended to throttle the server fi
+ To start \s-1INN\s0 and leave certain error messages going to the terminal:
+ .PP
+ .Vb 1
+-\& su \- news \-c <pathbin in inn.conf>/rc.news
++\& su \- news \-c /etc/rc.news
+ .Ve
+ .PP
+ To run \s-1INN\s0 at startup time from appropriate system boot scripts:
+ .PP
+ .Vb 1
+-\& su \- news \-c <pathbin>/rc.news >/dev/console
++\& su \- news \-c /etc/rc.news >/dev/console
+ .Ve
+ .PP
+ To stop \s-1INN\s0 (throttling first):
+ .PP
+ .Vb 2
+ \& <pathbin>/ctlinnd throttle reason
+-\& su \- news \-c \*(Aq<pathbin>/rc.news stop\*(Aq
++\& su \- news \-c \*(Aq/etc/rc.news stop\*(Aq
+ .Ve
+ .SH "BUGS"
+ .IX Header "BUGS"
+diff -up inn-2.5.1/doc/pod/install.pod.nologin inn-2.5.1/doc/pod/install.pod
+--- inn-2.5.1/doc/pod/install.pod.nologin 2009-10-12 20:24:04.000000000 +0200
++++ inn-2.5.1/doc/pod/install.pod 2009-10-13 21:53:35.000000000 +0200
+@@ -1551,7 +1551,7 @@ INN is started via the shell script B<rc
+ news user and not as root. To start INN on system boot, you therefore
+ want to put something like:
+
+- su news -c <pathbin in inn.conf>/rc.news
++ su -m news -c /etc/rc.news
+
+ in the system boot scripts. If B<innd> is stopped or killed, you can restart
+ it by running B<rc.news> by hand as the news user.
+@@ -1559,7 +1559,7 @@ it by running B<rc.news> by hand as the
+ The B<rc.news> script may also be used to shut down INN, with the C<stop>
+ option:
+
+- su news -c '<pathbin in inn.conf>/rc.news stop'
++ su -m news -c '/etc/rc.news stop'
+
+ In the F<contrib> directory of this source tree is a sample init script
+ for people using System V-style init.d directories.
+diff -up inn-2.5.1/doc/pod/rc.news.pod.nologin inn-2.5.1/doc/pod/rc.news.pod
+--- inn-2.5.1/doc/pod/rc.news.pod.nologin 2009-10-12 20:24:04.000000000 +0200
++++ inn-2.5.1/doc/pod/rc.news.pod 2009-10-13 21:53:35.000000000 +0200
+@@ -63,16 +63,16 @@ is recommended to throttle the server fi
+
+ To start INN and leave certain error messages going to the terminal:
+
+- su - news -c <pathbin in inn.conf>/rc.news
++ su -m news -c /etc/rc.news
+
+ To run INN at startup time from appropriate system boot scripts:
+
+- su - news -c <pathbin>/rc.news >/dev/console
++ su -m news -c /etc/rc.news >/dev/console
+
+ To stop INN (throttling first):
+
+ <pathbin>/ctlinnd throttle reason
+- su - news -c '<pathbin>/rc.news stop'
++ su -m news -c '/etc/rc.news stop'
+
+ =head1 BUGS
+
+diff -up inn-2.5.1/INSTALL.nologin inn-2.5.1/INSTALL
+--- inn-2.5.1/INSTALL.nologin 2009-10-12 20:24:04.000000000 +0200
++++ inn-2.5.1/INSTALL 2009-10-13 21:53:35.000000000 +0200
+@@ -1511,7 +1511,7 @@ Starting and Stopping the System
+ news user and not as root. To start INN on system boot, you therefore
+ want to put something like:
+
+- su news -c <pathbin in inn.conf>/rc.news
++ su -m news -c /etc/rc.news
+
+ in the system boot scripts. If innd is stopped or killed, you can
+ restart it by running rc.news by hand as the news user.
+@@ -1519,7 +1519,7 @@ Starting and Stopping the System
+ The rc.news script may also be used to shut down INN, with the "stop"
+ option:
+
+- su news -c '<pathbin in inn.conf>/rc.news stop'
++ su -m news -c '/etc/rc.news stop'
+
+ In the contrib directory of this source tree is a sample init script for
+ people using System V-style init.d directories.
diff --git a/inn-2.5.1.pie.patch b/inn-2.5.1.pie.patch
new file mode 100644
index 0000000..06daa52
--- /dev/null
+++ b/inn-2.5.1.pie.patch
@@ -0,0 +1,24 @@
+diff -up inn-2.5.1/frontends/Makefile.pie inn-2.5.1/frontends/Makefile
+--- inn-2.5.1/frontends/Makefile.pie 2009-10-12 20:24:04.000000000 +0200
++++ inn-2.5.1/frontends/Makefile 2009-10-13 21:51:38.000000000 +0200
+@@ -85,7 +85,7 @@ ovdb_init: ovdb_init.o $(BOTH) ; $(
+ ovdb_monitor: ovdb_monitor.o $(BOTH) ; $(LINK) ovdb_monitor.o $(STORELIBS)
+ ovdb_server: ovdb_server.o $(BOTH) ; $(LINK) ovdb_server.o $(STORELIBS)
+ ovdb_stat: ovdb_stat.o $(BOTH) ; $(LINK) ovdb_stat.o $(STORELIBS)
+-rnews: rnews.o $(LIBINN) ; $(LINK) rnews.o $(STORELIBS)
++rnews: rnews.o $(LIBINN) ; $(LINK) rnews.o -pie $(STORELIBS)
+ sm: sm.o $(BOTH) ; $(LINK) sm.o $(STORELIBS)
+
+ ovdb_init.o: ovdb_init.c
+diff -up inn-2.5.1/innd/Makefile.pie inn-2.5.1/innd/Makefile
+--- inn-2.5.1/innd/Makefile.pie 2009-10-12 20:24:04.000000000 +0200
++++ inn-2.5.1/innd/Makefile 2009-10-13 21:53:11.000000000 +0200
+@@ -44,7 +44,7 @@ perl.o: perl.c ; $(CC) $(CFLAGS) $(PE
+ python.o: python.c ; $(CC) $(CFLAGS) $(PYTHON_CPPFLAGS) -c python.c
+
+ innd: $(OBJECTS) $(LIBSTORAGE) $(LIBHIST) $(LIBINN)
+- $(LIBLD) $(LDFLAGS) -o $@ $(OBJECTS) $(INNDLIBS)
++ $(LIBLD) -pie $(LDFLAGS) -o $@ $(OBJECTS) $(INNDLIBS)
+
+ tinyleaf: tinyleaf.o $(LIBINN)
+ $(LIBLD) $(LDFLAGS) -o $@ tinyleaf.o $(LIBINN) $(LIBS)
reply other threads:[~2026-08-26 8:54 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=178773444124.1.3916433653007405138.rpms-inn-74e5a8512c61@fedoraproject.org \
--to=npajkovs@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