From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. fc1c8b957e8f9e5d5330867c328e07fe6cbb8640
Date: Wed, 19 Dec 2012 23:13:09 +0100 [thread overview]
Message-ID: <20121219221333.6A81D200CF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1652 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 fc1c8b957e8f9e5d5330867c328e07fe6cbb8640 (commit)
from a62c7eacc7ce619fdd7d3f7ef3a9dcda5a9fd589 (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 fc1c8b957e8f9e5d5330867c328e07fe6cbb8640
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Dec 19 20:42:11 2012 +0100
man-db: Update to 2.6.3.
Fixes the gnulib gets build problem.
-----------------------------------------------------------------------
Summary of changes:
man-db/man-db.nm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/man-db/man-db.nm b/man-db/man-db.nm
index b392038..f1dfba0 100644
--- a/man-db/man-db.nm
+++ b/man-db/man-db.nm
@@ -4,8 +4,8 @@
###############################################################################
name = man-db
-version = 2.6.1
-release = 3
+version = 2.6.3
+release = 1
groups = Documentation
url = http://savannah.nongnu.org/projects/man-db
@@ -20,6 +20,7 @@ description
end
source_dl = http://download.savannah.gnu.org/releases/man-db/
+sources = %{thisapp}.tar.xz
build
requires
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-12-19 22:13 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=20121219221333.6A81D200CF@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