From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. cdbf2bccc8439731dce978aae9172ed90ef54991
Date: Thu, 19 Jun 2014 14:41:26 +0200 [thread overview]
Message-ID: <20140619124126.EA693218ED@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1548 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 2.x development tree".
The branch, next has been updated
via cdbf2bccc8439731dce978aae9172ed90ef54991 (commit)
from 567fadff6a099d8e2d59ee6ce1e1957cb5de8840 (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 cdbf2bccc8439731dce978aae9172ed90ef54991
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jun 19 14:40:56 2014 +0200
gpgme: Remove libgpg-error from dependency list
This has become a part of the core system, now.
-----------------------------------------------------------------------
Summary of changes:
lfs/gpgme | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/gpgme b/lfs/gpgme
index 12da4cb..cdaf5a6 100644
--- a/lfs/gpgme
+++ b/lfs/gpgme
@@ -32,9 +32,9 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = gpgme
-PAK_VER = 1
+PAK_VER = 2
-DEPS = "libgpg-error libassuan"
+DEPS = "libassuan"
###############################################################################
# Top-level Rules
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-06-19 12:41 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=20140619124126.EA693218ED@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