From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 958fb3937cffbb585bb325f68c7bde9d8a24ca21
Date: Sun, 11 Mar 2012 11:03:03 +0100 [thread overview]
Message-ID: <20120311100303.D48B3200D6@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1663 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 958fb3937cffbb585bb325f68c7bde9d8a24ca21 (commit)
from f5d8aeebaf336c979d256c2fff83d1c1784b1495 (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 958fb3937cffbb585bb325f68c7bde9d8a24ca21
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Mar 11 11:02:35 2012 +0100
perl-Digest-SHA1: Add missing build dependency perl-ExtUtils-ParseXS.
-----------------------------------------------------------------------
Summary of changes:
perl-Digest-SHA1/perl-Digest-SHA1.nm | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
Difference in files:
diff --git a/perl-Digest-SHA1/perl-Digest-SHA1.nm b/perl-Digest-SHA1/perl-Digest-SHA1.nm
index cd7a722..8c34a86 100644
--- a/perl-Digest-SHA1/perl-Digest-SHA1.nm
+++ b/perl-Digest-SHA1/perl-Digest-SHA1.nm
@@ -5,7 +5,7 @@
name = perl-Digest-SHA1
version = 2.13
-release = 2
+release = 3
thisapp = Digest-SHA1-%{version}
groups = Development/Libraries
@@ -32,6 +32,7 @@ source_dl = http://search.cpan.org/CPAN/authors/id/G/GA/GAAS/
build
requires
perl(ExtUtils::MakeMaker)
+ perl(ExtUtils::ParseXS)
end
build
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-03-11 10:03 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=20120311100303.D48B3200D6@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