From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 4ec2079f201db9d057b7ec031ae16fc8776c6773
Date: Thu, 14 Sep 2023 12:01:59 +0000 [thread overview]
Message-ID: <4RmbXR50bFz2xlv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1563 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 4ec2079f201db9d057b7ec031ae16fc8776c6773 (commit)
from f98ee7a3e4f7267833cd3957f750cb68f8b8d782 (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 4ec2079f201db9d057b7ec031ae16fc8776c6773
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Sep 14 12:01:17 2023 +0000
glib2: Bump release to rebuild after Pakfire bug
The fix interpreter function has corrupted some scripts which no longer
can be executed any more and therefore this package needs to be rebuilt.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
glib2/glib2.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/glib2/glib2.nm b/glib2/glib2.nm
index d0e6e3bbd..417a90135 100644
--- a/glib2/glib2.nm
+++ b/glib2/glib2.nm
@@ -7,7 +7,7 @@ name = glib2
ver_major = 2.74
ver_minor = 2
version = %{ver_major}.%{ver_minor}
-release = 1
+release = 2
thisapp = glib-%{version}
groups = System/Libraries
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2023-09-14 12:01 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=4RmbXR50bFz2xlv@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