From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 2bd9b33ab279017554e98e7aa43f0a34555ba18b
Date: Sun, 01 Jan 2012 13:01:02 +0100 [thread overview]
Message-ID: <20120101120123.7CF3120143@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1586 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 2bd9b33ab279017554e98e7aa43f0a34555ba18b (commit)
from 19df835c89b6c9bbc578814212cba029fe5eb5a6 (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 2bd9b33ab279017554e98e7aa43f0a34555ba18b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Jan 1 13:00:20 2012 +0100
elfutils: Fix broken runtime dependencies.
-----------------------------------------------------------------------
Summary of changes:
elfutils/elfutils.nm | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/elfutils/elfutils.nm b/elfutils/elfutils.nm
index df15cc4..c4d560e 100644
--- a/elfutils/elfutils.nm
+++ b/elfutils/elfutils.nm
@@ -5,7 +5,7 @@
name = elfutils
version = 0.152
-release = 4
+release = 5
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = Development/Libraries
@@ -61,7 +61,10 @@ packages
package %{name}-devel
template DEVEL
- requires = %{name}=%{thisver}, %{name}-libs=%{thisver}
+ requires
+ %{name} = %{thisver}
+ %{name}-libs = %{thisver}
+ end
end
package %{name}-libs
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-01-01 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=20120101120123.7CF3120143@argus.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