From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. f0fb701144c5ec2bb974b18fa1cae930d11b6141
Date: Sat, 25 Feb 2012 13:09:28 +0100 [thread overview]
Message-ID: <20120225121013.C9D2E2008B@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1622 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 f0fb701144c5ec2bb974b18fa1cae930d11b6141 (commit)
from e87a04764f162d83bec9fdfad6a31af429225625 (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 f0fb701144c5ec2bb974b18fa1cae930d11b6141
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Feb 23 00:51:42 2012 +0100
ghostscript: Add some dependencies that enhance functionality.
Link to libpng to read and write PNG images.
-----------------------------------------------------------------------
Summary of changes:
ghostscript/ghostscript.nm | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
Difference in files:
diff --git a/ghostscript/ghostscript.nm b/ghostscript/ghostscript.nm
index 08d7f53..14040f7 100644
--- a/ghostscript/ghostscript.nm
+++ b/ghostscript/ghostscript.nm
@@ -5,7 +5,7 @@
name = ghostscript
version = 9.05
-release = 1
+release = 2
groups = Applications/Printing
url = http://ghostscript.com
@@ -32,8 +32,11 @@ build
requires
cups-devel
dbus-devel
+ expat-devel
glib2-devel
+ libidn-devel
libjpeg-devel
+ libpng-devel
libtiff-devel
libtool
libxml2-devel
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-02-25 12:09 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=20120225121013.C9D2E2008B@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