From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core82, updated. d49a04c939bcb5ebadba3138dd52c2852700806b
Date: Fri, 22 Aug 2014 12:06:13 +0200 [thread overview]
Message-ID: <20140822100613.8063E218C7@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 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, core82 has been updated
via d49a04c939bcb5ebadba3138dd52c2852700806b (commit)
from 48f989de1591ed83a614e7133649723a91d7e822 (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 d49a04c939bcb5ebadba3138dd52c2852700806b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Aug 22 12:05:39 2014 +0200
sane: depends on cups libs.
-----------------------------------------------------------------------
Summary of changes:
lfs/sane | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/sane b/lfs/sane
index 842b548..39b9603 100644
--- a/lfs/sane
+++ b/lfs/sane
@@ -33,9 +33,9 @@ DIR_APP = $(DIR_SRC)/sane-backends-$(VER)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = sane
-PAK_VER = 3
+PAK_VER = 4
-DEPS = "libtiff"
+DEPS = "cups libtiff"
###############################################################################
# Top-level Rules
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-08-22 10:06 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=20140822100613.8063E218C7@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