From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 905b8cbfbdf341e433d39436527f3ad28632f7fa
Date: Wed, 13 Sep 2023 14:46:57 +0000 [thread overview]
Message-ID: <4Rm3FF3glqz2y2X@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1506 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 905b8cbfbdf341e433d39436527f3ad28632f7fa (commit)
from 28b594d2be129f86e74543319a7fb0e3daa1c908 (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 905b8cbfbdf341e433d39436527f3ad28632f7fa
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Sep 13 14:46:21 2023 +0000
libtool: Rebuild package because of a Pakfire bug
Pakfire incorrectly changed the interpreter of the libtoolize script
which breaks it entirely.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
libtool/libtool.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/libtool/libtool.nm b/libtool/libtool.nm
index e95e7ff30..1b6626a6b 100644
--- a/libtool/libtool.nm
+++ b/libtool/libtool.nm
@@ -5,7 +5,7 @@
name = libtool
version = 2.4.7
-release = 1
+release = 2
groups = System/Libraries
url = https://www.gnu.org/software/libtool/
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2023-09-13 14:46 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=4Rm3FF3glqz2y2X@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