From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. e6b6abcc0bd4e549b246f06b4db608ab57a1b070
Date: Mon, 18 Sep 2023 12:54:44 +0000 [thread overview]
Message-ID: <4Rq4WT2Cyxz2xPF@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".
The branch, master has been updated
via e6b6abcc0bd4e549b246f06b4db608ab57a1b070 (commit)
from c6f9b49ca3bbecb4718d01577ff3776f2910f0db (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit e6b6abcc0bd4e549b246f06b4db608ab57a1b070
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Sep 18 12:52:06 2023 +0000
ncurses: Rebuild for Pakfire man page compression bug
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
ncurses/ncurses.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/ncurses/ncurses.nm b/ncurses/ncurses.nm
index 9f533a9d3..db53476a3 100644
--- a/ncurses/ncurses.nm
+++ b/ncurses/ncurses.nm
@@ -5,7 +5,7 @@
name = ncurses
version = 6.4
-release = 1
+release = 2
thisapp = %{name}-%{version}
groups = System/Base
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2023-09-18 12: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=4Rq4WT2Cyxz2xPF@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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